Plan your stack in a free Hobby workspace. Self-hosted Supabase runs as several paid services with persistent storage, sized for the components you enable.
Each instance has a fixed monthly price, prorated by the second. Budget for every enabled service and its storage.
Capability | Render | |||
|---|---|---|---|---|
How Supabase runs | One Render service per Supabase container | Fully managed by Supabase | Self-hosted containers with volumes | Self-hosted Machines with volumes |
Free tier | The full stack needs paid services and disks | 2 active projects, paused after 1 week idle | $5 trial for 30 days, then $1/month credit | No free tier. Personal bills under $5 waived |
Pricing model | Multiple paid services plus storage | Pro from $25/month, one project included | Usage-based compute and volumes | Usage-based compute and volumes |
Database | Supabase Postgres image on a disk | Managed Postgres, 500 MB on Free | Supabase Postgres image on a volume | Supabase Postgres image on a volume |
Persistent storage | SSD disks on paid services | Managed by Supabase | Volumes (no replicas) | Volumes, one per Machine, not replicated |
Stack as code | One render.yaml, auto-synced on push | Managed by Supabase | Project file, applied with CLI or CI | fly.toml per app. No database definitions |
Upgrades and patches | You update the Supabase images | Supabase | You update the images | You update the images |
Competitor details as of November 2026.
Map each Supabase component to a Render service. Define the stack in one render.yaml Blueprint and validate it in staging.
Map the upstream Supabase stack into individual services. Decide which APIs, realtime features, storage, and functions your application uses.
Use private services for internal components in the same workspace and region. Publish only the endpoints your application needs.
Supabase expects specific database roles, extensions, and initialization. Validate the database architecture instead of treating any Postgres instance as a drop-in replacement.
Use a supported S3-compatible backend for Storage, or validate a custom layout. Database persistence is separate.
Keep signing keys, database credentials, and service URLs consistent across the stack. Store secrets outside source control.
Test coordinated component updates and restore procedures. Render service infrastructure does not replace Supabase application operations.
Select the Supabase components you need and map each to a Render service. Translate configuration files, dependencies, and network routes into the deployment design.
Set up the required database roles and extensions, file persistence, and shared secrets. Configure public URLs, mail, and authentication providers.
Deploy a staging architecture and test auth, APIs, realtime, uploads, and recovery. Complete those checks before routing production traffic.