BUT CAN'T SUPABASE DO THAT?
Alfredo vs Supabase
“Doesn't Supabase already wire auth, database and storage for me?”
Supabase gives one project a backend; Alfredo wires and watches all of your projects, and the two can coexist.
YOU KEEP
Supabase in any project that uses it. Alfredo wires a different bundle (Convex, Better-Auth) and does not migrate yours.
Alfredo and Supabase, across the seven things
The honest version, side by side. Green is automatic, amber is manual work you own, a grey ring is not possible.
| CAPABILITY | Alfredo | Supabase |
|---|---|---|
| Runs on your servers | Any VPS you can SSH into. Alfredo runs on your servers; it does not host your projects. | Partly — Docker self-hosting exists, but self-hosted behaves as one project (no orgs; managed backups/PITR, branching and multi-project Studio are platform-only, July 2026). |
| Deploys your projects | Built in. Pick the integrations a project needs and deploy — there is no separate PaaS underneath. | Its own backend only — your app still needs a host. |
| Wires each project at birth | The core claim. Auth, email, database, analytics and payments are configured at creation, secrets are moved for you, and integrations already running are reused. | Its own bundle — Postgres, auth, storage — real and scoped to that one backend. |
| One dashboard across projects | One HQ across every project you deploy. | No — Studio is one backend's console. |
| Sees your business, not just CPU | Payments and email delivery sit next to traffic, errors and uptime — business signals, not just CPU. | No. |
| Works without assembly | Zero setup — the cross-project view is assembled for you, not built. | Managed, yes; self-hosted is a Docker stack you run per project. |
| Flat cost for many projects | Flat: you pay for your own box, not per host, per project or per module. | Free $0, Pro from $25/mo, Team from $599/mo (2026-07-18). |
ALFREDO ADDS
Deploys the whole project on your servers, wires beyond the backend (email, analytics, payments, uptime), and gives one view across all projects. Alfredo is a prototype; Supabase is a mature backend.
SUPABASE'S REAL WINS
Maturity, docs, community, a genuinely useful free tier, backend depth.
STAY ON SUPABASE IF
Stay put if you need a deep managed Postgres backend right now. Nothing Alfredo provisions matches that depth. Alfredo is an early, unproven prototype; Supabase is the mature, proven thing.