Backend as a service in 2026: what it is and which one to pick
A backend as a service (BaaS) gives an app its database, sign-in, file storage and server functions as one hosted product, so you do not build and run those parts yourself. This page is about backend as a service, not banking as a service or backup as a service. It compares seven platforms on the three things that decide the choice: which database you get, what the free tier really allows, and how the bill grows.
Last checked November 17, 2026.
What a backend as a service includes
Most apps need the same server parts: a database, user accounts, file uploads, live updates and a place to run server code. A BaaS hosts all of them behind one project URL and one set of keys. Your app talks to it from the browser or the phone through a client library.
- Database: where the app data lives. Postgres, a document store or SQLite, depending on the platform.
- Auth: sign-up, sign-in, sessions and password reset.
- Storage: file uploads with access rules.
- Realtime: live updates pushed to connected clients.
- Functions: server code you deploy without running a server.
Seven BaaS platforms, side by side
| Platform | Database | Free tier | How paid plans are priced |
|---|---|---|---|
| Supabase | Postgres | 2 active projects, 500 MB database each, paused after 1 week of inactivity | Pro from $25 a month per organization, plus compute per project |
| Firebase | Firestore (documents) | Spark: 1 GiB stored, 50K reads and 20K writes a day, 50K monthly active users. No Cloud Functions. | Blaze: pay as you go, by reads, writes, storage and compute |
| Appwrite | TablesDB by default; dedicated PostgreSQL or MySQL from $10 a month per database | 1 organization and 2 projects. A project freezes when it reaches a limit. | Per organization, with resources allocated per project |
| Convex | Its own document database, queried in TypeScript instead of SQL | 1M function calls, 0.5 GB database storage and 1 GB file storage | Professional: $25 per developer a month, then usage |
| Nhost | Postgres behind Hasura GraphQL | 1 project, 1 GB database, paused after 1 week of inactivity | Pro from $25 a month per organization; point-in-time recovery from $100 extra |
| PocketBase | Embedded SQLite, one server | Free and open source. You host it yourself; there is no managed service. | The cost of your own server |
| Scribase | Postgres 17 | 1 project with no time limit, 0.5 GB database, 1 GB files. Scales to zero when idle and wakes on the next request. | Per project: Hobby $5 a month, Pro $25 a month. No per-user or per-developer price. |
Sources: Supabase: Pricing, Firebase: Pricing, Appwrite: Pricing, Appwrite docs: Free plan, Convex: Pricing, Nhost: Pricing, PocketBase: FAQ, Scribase: Pricing
How to choose
- You want SQL, joins and a database you can take anywhere: pick a Postgres platform (Supabase, Nhost, Scribase).
- You are building an offline-first mobile app inside the Google ecosystem: Firebase.
- You want the whole backend written as TypeScript functions with reactive queries, and you accept a database only that platform runs: Convex.
- You want one small binary on your own server and your app fits on a single machine: PocketBase.
- You want an open-source platform you can self-host with a hosted option too: Appwrite or Supabase.
- You want several small projects without a pause after a quiet week and without a per-seat price: Scribase.
Where Scribase fits
Scribase is a BaaS on Postgres 17. Each project has auth, storage, realtime and edge functions behind one URL, and it answers the same REST, auth and storage calls supabase-js makes, so there is no new client to learn. Transactional email is a Resend-compatible API in the same account, with its own key.
The difference from the others is the pricing unit and the idle behaviour: you pay per project, and a quiet project scales to zero and wakes on the next request instead of being paused until someone restores it by hand.
npx scribase initWhat Scribase does not do
A fair comparison names the gaps:
- One region today (Frankfurt). If your users or your compliance rules need another region, this is not the right host yet.
- Direct Postgres connections from the internet (ports 5432 and 6543, for psql or pg_restore) are not open yet. Migrations, the console SQL editor and the HTTP serverless driver work today.
- No compliance certifications yet (no SOC 2, no HIPAA BAA).
- The core is not open source. You can export everything, and a licensed self-hosted deployment exists, but you cannot clone the server from a public repository.
- No prebuilt sign-in components. You render the form and call the client.
Questions people ask
What is a backend as a service (BaaS)?
A backend as a service is a hosted product that gives an app its database, user sign-in, file storage, live updates and server functions behind one project URL, so the team does not build or operate those parts. In software, BaaS means backend as a service; it is unrelated to banking as a service and backup as a service.
Which backend as a service is best in 2026?
It depends on the database you want. For Postgres and SQL: Supabase, Nhost or Scribase. For an offline-first mobile app on Google infrastructure: Firebase. For a TypeScript-only backend with reactive queries: Convex. For a single self-hosted binary: PocketBase. For an open-source platform with self-hosting: Appwrite or Supabase.
Which BaaS has a free tier that does not pause?
As of 2026-11-17, Supabase and Nhost pause free projects after one week of inactivity. Scribase keeps one project free with no time limit; it scales to zero when idle and wakes on the next request. Firebase Spark and the Convex free plan do not pause but cap daily or monthly usage.
How much does a backend as a service cost?
Every platform here has a free tier. Paid plans start around $25 a month: Supabase Pro from $25 per organization, Nhost Pro from $25 per organization, Convex Professional $25 per developer. Scribase is priced per project: $5 a month on Hobby and $25 on Pro. Firebase Blaze is pay as you go.
Is Scribase a backend as a service?
Yes. Each Scribase project is Postgres 17 with auth, storage, realtime and edge functions, and it works with the supabase-js client. It runs in one region today and the core is not open source.