Supabase stack services
This page shows the capabilities provided by the services in the Supabase stack and the connections, configs, settings, cron schedules, actions, volumes, backups, imports, and other customizations attached to them for this specific stack.
| Stack service | Base service | Versions | Role |
|---|---|---|---|
| Supabase | 0.8.1 | Primary | |
| Supabase PostgreSQL | 17 | Required |
- Additional services can be added or removed.
- When one of the services in the stack updates, the stack can be upgraded to a new revision.
- Stack changes can then be rolled out to environments on your schedule.
Backups
Protect service data with repeatable backup workflows that stay attached to the stack.
Supabase
Storage objects (filesystem backend)
Supabase
Studio snippets
Supabase PostgreSQL
Supabase databases and roles
Imports and migration
Bring working data into another environment or onboard existing workloads faster with stack-defined import flows.
Supabase PostgreSQL
Supabase database import
Import from a backup archive, uploaded file, or public URL depending on the service workflow.
Settings
Tune service behavior per environment while keeping one reusable stack baseline.
Supabase
Application site URL
Supabase
Additional allowed redirect URLs
Supabase
Disable new signups
Default value: false.
Supabase
Exposed database schemas
Default value: public,storage,graphql_public.
Supabase
Email sender address
Supabase
Email sender name
Default value: Supabase.
Supabase
S3 bucket
Default value: stub.
Supabase
S3 endpoint URL
Volumes
Provision the persistent storage and shared volume relationships the stack expects.
Supabase
Storage objects
Size: 10 GB.
Supabase
Studio snippets
Size: 1 GB.
Supabase PostgreSQL
Database data and encryption keys
Size: 20 GB.
Service links
See how services are wired together so dependencies stay consistent across environments.
Supabase
Supabase PostgreSQL
Linked to Supabase PostgreSQL. Required.