Compare / Supabase
The Supabase alternative that also runs your app
Supabase is a very good managed Postgres with a backend bolted on, and your application still runs somewhere else. Lizard runs the app and the database in the same project, on the same bill, with the connection string wired in by reference.
Why developers look for a Supabase alternative
The app is still someone else’s problem
Supabase hosts Postgres, Auth, Storage, Realtime, and Edge Functions. A Django API, a Go service, or a queue consumer needs a second platform and a second bill.
The compute add-on is the real price
Pro is $25 a month with a $10 compute credit — enough for exactly one Micro instance. The credit goes to the organization, not the project, so a second project, or any size above Micro (Small $15, Medium $60, Large $110), lands on top of the $25.
Free projects pause
A free Supabase project auto-pauses after a week of inactivity, which is fine for a prototype and surprising in a demo.
Edge Functions are not a server
They are Deno functions with execution limits. A long-lived worker is not one of the things they do.
Lizard vs Supabase
Every figure read off Supabase’s published pricing and our own. Last verified: 27 August 2026.
| Compared by | Lizard | Supabase |
|---|---|---|
| What it runs | Your app, your workers, and the database | The database, Auth, Storage, Realtime, and Edge Functions |
| Postgres | PostgreSQL 18, ready in seconds, billed on measured use | Postgres with row-level security, on a sized compute add-on |
| Compute pricing | $0.0250128 per vCPU-hour, $0.0125064 per GB-hour, measured | Compute add-ons: Micro $10, Small $15, Medium $60, Large $110 a month |
| Entry price | $19/month with $19 in monthly credits, after a 7-day trial with $5 in trial credits | Free tier that pauses after a week idle; Pro $25 with $10 of compute credit |
| Egress | $0.045 per GB from the first byte | 250 GB included on Pro, then $0.09 per GB |
| Long-lived workers | A service with no HTTP port | Not offered |
| Auth | Bring your own | First-party, and the strongest part of the product |
| Run a command in a running app | lizard ssh -s api -- <cmd>, one command at a time, no interactive session | Not applicable |
When Supabase is the better choice
You are building a client-heavy app and want auth, row-level security, realtime subscriptions, and storage without writing a backend. Supabase Auth is excellent, the row-level security model is the real product, and the dashboard is better than ours at database work. Many teams run Supabase for auth and Lizard for the services — that combination is fine.
Moving from Supabase
No Dockerfile required — lizardpack detects the stack and writes one on the build node. If your repo already has a Dockerfile, it is used as it stands.
Frequently asked questions
For the database and the app, yes — Lizard runs Managed Postgres in the same project as the service that reads it, wired in by reference. For auth and row-level security, Supabase does more out of the box; plenty of teams keep Supabase Auth and run their services on Lizard.
Pro is $25 a month including a $10 compute credit, which covers a Micro instance. Larger instances are add-ons: Small $15, Medium $60, Large $110, up to 16XL at $3,730. Egress is 250 GB included, then $0.09 per GB.
No. Free projects auto-pause after a week of inactivity and have to be restored. Lizard does not pause idle services. During the 7-day trial, running services pause if usage goes $1 past the $5 in trial credits. Pro costs $19/month with $19 in monthly credits.
Yes: pg_dump from the Supabase connection string, lizard add postgres, read the new connection string from the dashboard, then pg_restore into it. Check your extensions — Supabase enables several by default that a plain Postgres does not.
Build with AI. Ship with Lizard.
You don't need a platform team to go live. Your whole cloud, one CLI command away.
- Services
- —
- Add-ons
- —
- Deployments
- —
- Sandbox starts
- —