Supabase Hosting on AWS

Run the open-source Supabase stack on your own AWS account — Postgres, Auth, Storage, Realtime, and Edge Functions — provisioned by Terraform. A self-hosted alternative to Supabase Cloud, with no auto-pause on idle projects, no per-project caps, and full data ownership.

Two ways to host Supabase

Supabase Cloud — managed by Supabase. Fast to start, but free-tier projects auto-pause after a week of inactivity, and the bundled plans push you up tiers as you grow.
Self-hosted on AWS — same Supabase, your infrastructure. No auto-pause, no per-project caps, billed directly by AWS. Staticbot ships the Terraform that provisions it.

This page is about the second option. If you already have a Supabase backend and just need to deploy the frontend, see frontend hosting for Supabase apps.

What you get

Full open-source Supabase

Postgres, GoTrue (Auth), Storage, Realtime, PostgREST, and Edge Functions — the same services Supabase Cloud runs, deployed from the upstream open-source images.

Your AWS account

Resources live in your own AWS organization, billed directly by AWS. No Staticbot middleman on the runtime bill.

No auto-pause

Your database stays up whether or not the app sees traffic this week. AWS doesn't pause your EC2 / RDS / Lambda for being idle.

Terraform you own

The infrastructure is Terraform code we ship to you. Walk away from Staticbot any time and the stack still runs on AWS exactly as deployed.

When self-hosted Supabase makes sense

Your Supabase Cloud project keeps getting auto-paused. Free-tier projects pause after 7 days of inactivity. On AWS, your DB stays warm as long as you want to keep paying for it.
You need predictable pricing. Supabase Cloud's Pro tier ($25/mo) is fine until you cross a metered limit; the next jumps come in fixed bands. AWS bills you for what you provisioned.
You need data sovereignty. Customer in the EU? Health/financial data with residency rules? Staticbot deploys Supabase into the AWS region you pick — including EU regions.
You're escaping a bundled provider. Lovable Cloud, Bolt, Base44 — they all run Supabase under the hood and mark it up. Self-host the same stack and pay the underlying rate.

When it doesn't

You want zero ops

Supabase Cloud handles upgrades, backups, point-in-time recovery, and security patches for you. Self-hosting means you own that operational surface. Staticbot ships sensible defaults, but you're driving.

You're at hobby scale

Supabase Cloud's free tier is generous for prototypes and side projects. If auto-pause every 7 days doesn't actually break your usage, the free tier is hard to beat. Self-hosting starts to make sense once you have real users.