Role
Required
Supabase PostgreSQL in the Supabase stack
This page explains what Supabase PostgreSQL means in the Supabase stack: how it is included, which base service it uses, and how it connects to the rest of the stack.
Supabase PostgreSQL is included by default and treated as a required part of the Supabase stack.
Base service
Supabase PostgreSQL
Type
db
Delivery
Prebuilt service image
Stack fit
How Supabase PostgreSQL fits into this stack
Supabase PostgreSQL is included by default and treated as a required part of the Supabase stack.
This stack service is based on Supabase PostgreSQL and keeps the service-specific setup for Supabase in one place.
Version policy
This stack service is limited to 17.
Inclusion
Enabled by default: Yes
Required: Yes
Primary: No
Connections
No explicit service links are defined for this stack service.
Storage
data: 20 GB
Stack-specific technical details
Review the operational capabilities exposed by Supabase PostgreSQL inside this stack, including backups, imports, configs, settings, cron, actions, storage, and service links where they exist.
Backups
Protect service data with repeatable backup workflows that stay attached to the stack.
Supabase databases and roles
Imports and migration
Bring working data into another environment or onboard existing workloads faster with stack-defined import flows.
Supabase database import
Import from a backup archive, uploaded file, or public URL depending on the service workflow.
Volumes
Provision the persistent storage and shared volume relationships the stack expects.
Database data and encryption keys
Size: 20 GB.