jerrycan vs Supabase
Managed platform vs owned backend
Supabase and jerrycan solve the same problem — a backend for your product — with opposite ownership models. Supabase operates a managed platform you subscribe to; jerrycan generates a Rust codebase you run yourself. Here's the full read.
The short answer
Choose Supabase if
- You want a managed service and are comfortable on their cloud and pricing.
- You rely on their ecosystem: client SDKs, edge functions, dashboard workflows.
- You have no appetite for operating software, even a single binary.
Choose jerrycan if
- You want the code and data as your own IP, portable to any host.
- Predictable flat hosting costs matter more than managed convenience.
- You build with an AI agent and want it to own the whole stack end to end.
What is Supabase?
Supabase is a hosted backend platform built around Postgres. Sign up and you get a managed database with instant APIs, plus auth, file storage, realtime subscriptions and edge functions — all operated by Supabase, configured through their dashboard, and consumed through their client SDKs. It open-sources its components and markets itself as the open-source Firebase alternative.
Where Supabase shines
For getting a hosted Postgres with batteries in minutes, Supabase is genuinely excellent. The dashboard is polished, the SDKs are mature, the documentation is strong, and the free tier is generous enough to build a real prototype. Because the core is Postgres rather than a proprietary datastore, your data model stays standard — a meaningful advantage over closed platforms. An experienced operations team runs it all so you never think about servers.
Where Supabase falls short
The problems start when a prototype becomes a business. Usage-based pricing means your bill grows with your success and spikes with your best months — you are permanently renting infrastructure you'll never own. Your application logic ends up expressed as platform configuration: row-level-security policies, dashboard settings and edge functions that only fully make sense inside Supabase. Self-hosting exists but means operating their entire multi-service platform yourself — roughly ten coordinated services — which is a heavier operational burden than most teams expect. And the deeper you integrate their SDKs, the more your product's architecture belongs to their roadmap, their pricing changes, and their deprecation schedule rather than to you.
What is jerrycan?
jerrycan is a self-hostable Rust backend framework for REST APIs, designed for a different builder: an AI agent. You describe the product; your agent assembles auth, data, files and payments from jerrycan’s built-ins as real code in your repository, then deploys it to a server you choose. The output is a compiled binary you own outright — no platform between you and your users, no meter on your growth.
Where jerrycan beats Supabase
- Ownership: jerrycan output is plain Rust code and a standard database in your repo — your IP, portable to any host. Supabase gives you access, not an asset.
- Hosted convenience without lock-in: your agent can deploy jerrycan with instantly hosted Postgres (e.g. on Render) — managed database, still your code and your data.
- Cost shape: a flat server bill that ignores your growth, versus usage-based pricing that compounds with it.
- Operational weight when self-hosting: one compiled binary versus a ten-service platform.
- AI workflow: your agent builds, reviews and deploys the whole product from chat — no dashboard wiring, no SDK glue.
- No platform dependency: nothing between you and your users to reprice, rate-limit or sunset.
| Supabase | jerrycan | |
|---|---|---|
| What you get | A hosted backend platform — Postgres, auth, storage behind their APIs. | A real Rust backend your AI builds for your REST APIs — code you own. |
| Where it runs | Their cloud by default; self-hosting means running their whole platform. | Anywhere you choose — your server, your cloud, or instantly hosted Postgres via Render. |
| Pricing at scale | Usage-based — the bill grows with your success. | Free and open source — you pay only for your own hosting. |
| Lock-in | Platform APIs and hosted services tie your app to them. | Plain Rust code and your own data — portable by design. |
| AI workflow | You wire the SDKs and dashboard together yourself. | Built and deployed from your agent chat — one conversation. |
Own the backend behind your SaaS
Point your AI at jerrycan — it builds a real Rust backend for your REST APIs that's yours to keep.