Compare
Databasezy, Supabase and Layerbase, side by side
What each one publishes about databases, compliance, platform services and cloud dev machines, read from their own pages on October 7, 2026. Where a vendor's pages do not say, the table says "Not listed".
Our column comes from the same catalogue as our pricing page. Badges mark what is still coming soon on our side. Spotted something out of date? Tell us at [email protected].
Comparison table
| Topic | Databasezy | Supabase | Layerbase |
|---|---|---|---|
| Databases | |||
| Engines | 18 in the catalogue, 18 available today | PostgreSQL | 18 engines |
| Billing model | Plan fee plus usage; compute billed by the hour at the size price | Plan fee plus usage; compute billed by the hour | Flat monthly plans, no usage meters |
| Scheduled backups | Solo: daily, 7-day retention; Team: daily, 14-day retention | Daily: Pro 7 days, Team 14 days | Solo daily, 7 days; Pro 30 days; Dedicated hourly |
| Point-in-time recovery | Add-on, $100 per instance / month / 7 days of retention | Add-on, $100 a month per 7 days of retention | Not listed |
| Security and compliance | |||
| HIPAA | Per database: secure placement on a HIPAA cell with dedicated nodes and per-org keys, on Team and Enterprise with a signed BAA | Paid add-on on Team and Enterprise with a BAA, configured per project | Not listed |
| Spend cap | On by default on Solo; available on every paid plan | Available on Pro | Flat prices; no metered usage |
| Team controls | Org and project roles, teams with budgets, approval requests, audit log | Organization roles; dashboard SSO on Team | Team seats on custom plans |
| Platform services | |||
| Auth for your app's users | Email and password, magic links, one-time codes, CAPTCHA, leaked-password checks; social sign-in, MFA and SAML coming soon | Yes, including social sign-in, MFA and SAML | Auth add-on built on Better Auth: email and password, Google and GitHub sign-in |
| REST and GraphQL | PostgREST and pg_graphql, plus SQL over HTTPS for every engine | PostgREST and pg_graphql | HTTP query API and compatible serverless drivers |
| Supabase client libraries | supabase-js works against your project endpoint | Native | Not listed |
| File storage | Buckets with policies, S3-compatible endpoint, image transforms Coming soon | Yes | Not listed |
| Edge functions | TypeScript functions on the Supabase edge runtime Coming soon | Yes | Not listed |
| Realtime | Broadcast, presence and Postgres changes Coming soon | Yes | Not listed |
| Cron and queues | pg_cron and pgmq, managed from the portal | pg_cron and pgmq | Not listed |
| Agent servers (cloud dev machines) | |||
| Offered | 3 sizes, from $12 a month ($0.0164 an hour) | Not listed | 3 sizes from $10 a month, billed monthly; in beta without an uptime SLA |
| When stopped | Compute billing stops; disk only, at $0.125 per GB-month | — | Stopping does not pause billing; cancel to stop charges |
| Isolation | A Kata VM per server, Docker inside | — | Ubuntu 24.04 servers with Docker |
| Access | SSH through a bastion with your registered keys (VS Code, Cursor, Zed), web terminal | — | SSH with your keys (VS Code, Cursor, Zed, Devin), web terminal |
| Snapshots | Daily snapshots, restore and export Coming soon | — | Not listed |
Where we go further
-
HIPAA-ready hosting per database
Put only the databases that hold PHI on a HIPAA cell, on nodes dedicated to your org with per-org keys and immutable backups, under a BAA on Team and Enterprise. Everything else stays on shared cells at normal prices.
-
18 engines, one control plane
18 available today, including PostgreSQL, MySQL, MariaDB and Valkey, each with the same backups, isolation, CLI, API and billing.
-
Usage billed by the hour
Compute by the hour at the size price, published usage prices and included allowances, with a spend cap that is on by default on Solo.
-
Agent servers that stop billing when stopped
A stopped server pays only for its disk. Each one is its own VM with Docker inside, reached over SSH through a bastion with your registered keys.
-
Org, team and budget controls
Roles, project-scoped access, team budgets and approval requests apply to databases, platform services and agent servers alike.
When another option may suit you better
We would rather you pick the right tool than the wrong one.
-
You need storage, functions or realtime in production today
Supabase ships them now. Ours are being built; the status on our platform page changes when they ship.
-
You need social sign-in, MFA or SAML for your users today
Supabase Auth has them. Ours are coming soon; email and password, magic links and one-time codes are live.
-
You want one flat monthly price with no meters
Layerbase's shared plans are flat. We bill usage by the hour, with included allowances and a spend cap.
Moving from Supabase: the step-by-step guide (documentation site)
Sources
Read on October 7, 2026. Supabase and Layerbase are trademarks of their owners.
Start today
Try it on your own data
A free database with Auth and the Data API on its endpoint, no card. Move a Supabase project over with the migration CLI.