Open-source BaaS, permissive licence
Appwrite (BSD-3-Clause).
Why people look for a Supabase alternative
Most people leave Supabase for one of four reasons:
- Data location. They need a specific region or their own server.
- Price model. Usage limits or compute costs do not fit their app.
- Less product. They want only the database, and bring their own auth and API.
- Different model. They want NoSQL (Firebase), a single binary (PocketBase) or GraphQL (Nhost).
If none of these apply, stay on Supabase.
Quick comparison
Facts from each vendor page or repository, checked October 2026. Not stated means the vendor page checked did not say.
| Tool | Type | Database | License | Self-host | Free tier | EU region |
|---|---|---|---|---|---|---|
| Firebase | BaaS | Firestore (NoSQL documents) | Proprietary (Google service) | No production self-hosting (Emulator Suite is for development only) | Spark plan: 1 GiB stored, 50K reads, 20K writes and 20K deletes per day; Auth free to 50K MAU | Yes. eur3 (Belgium, Netherlands, witness in Finland), europe-west3 (Frankfurt) and others |
| Appwrite | BaaS | Own database API (not Postgres) | BSD-3-Clause | Yes, with Docker | Free plan: 2 projects, 1 database, 3 storage buckets, 5 functions | Yes. Frankfurt (FRA). Amsterdam listed as coming soon |
| PocketBase | BaaS (single binary) | SQLite (embedded) | MIT | Yes, only (you run the binary) | Free software. You pay for the server you run it on | Your choice of server, so any region you rent |
| Nhost | BaaS | Postgres, with Hasura GraphQL | MIT | Yes, Docker Compose (example in the repo) | Starter: $0 forever, 1 project, 1 GB database, 1 GB storage, 5 GB egress | Not stated |
| Convex | Backend platform (framework) | Convex’s own database | FSL-1.1-Apache-2.0 (source-available, Apache-2.0 after two years) | Yes, with Docker | Free: $0, 0.5 GB database storage, 1 GB bandwidth, 1M function calls, 1 to 6 developers | Not stated |
| Neon | DB only | Postgres | Apache-2.0 | Code is open source, but no supported self-hosted product | Free: $0, 1 GB per project (20 GB total), 100 CU-hours per project, scales to zero after 5 minutes | Yes. aws-eu-central-1 (Frankfurt) and aws-eu-west-2 (London) |
| Self-hosted Supabase | BaaS (self-hosted) | Postgres | Apache-2.0 | Yes, Docker Compose (recommended path) | Free software. Minimum server: 4 GB RAM, 2 CPU cores, 40 GB SSD | Your choice of server, so any region you rent |
| Hostim | DB only (plus your own backend) | Postgres, MySQL, Redis | Hosted service, not open source | No | Postgres from €0 for 256 MB. €10 for 10 GB | Yes. Germany (Falkenstein) |
1. Firebase: Google’s backend with Firestore, the NoSQL database
BaaS • Proprietary (Google service) • Database: Firestore (NoSQL documents)
Firebase is Google’s hosted backend: a NoSQL database (Firestore), auth, file storage and hosting. It fits mobile and web apps that want a managed backend and already use Google Cloud. Supabase is the usual pick against it, because Supabase uses Postgres and SQL.
Pick it when:
- Your app is mobile-first and uses the Firebase SDKs.
- Your data fits document collections, not SQL tables.
- You want Google’s push, analytics and crash tools in the same project.
Trade-off: Firestore is not SQL. Joins and complex reporting are harder, and the bill can grow with every read and write. The database location is fixed when you create it. Pick a European location on day one if you need EU data residency.
Source: firebase.google.com/pricing
2. Appwrite: an open-source BaaS you can self-host
BaaS • BSD-3-Clause • Database: Own database API (not Postgres)
Appwrite is an open-source backend with auth, databases, storage, functions and realtime. You can use its cloud or run it on your own server with Docker. It fits teams that want a Firebase-style API with an open-source licence and a self-hosting option.
Pick it when:
- You want a BaaS under a permissive licence (BSD-3-Clause).
- You may move the backend to your own server later.
Trade-off: Its database is its own API, not Postgres. If you want plain SQL and Postgres tools, Supabase fits better. Appwrite Cloud's Free plan caps you at 2 projects and 1 database. Storage and bandwidth limits are not stated. In the EU only Frankfurt is live.
Source: github.com/appwrite/appwrite
3. PocketBase: one Go binary with SQLite, self-host only
BaaS (single binary) • MIT • Database: SQLite (embedded)
PocketBase is an open-source backend in one file: a Go binary with an embedded SQLite database, realtime subscriptions and an admin UI. It fits small apps and prototypes where you want to copy one file to one server and be done.
Pick it when:
- You want the whole backend in one binary and one SQLite file.
- Your app has one server and modest traffic.
Trade-off: It is a single-node tool. You own backups, updates and failover. SQLite is not Postgres, so you lose Postgres extensions and the tooling that comes with them. There is no official managed service.
Source: github.com/pocketbase/pocketbase
4. Nhost: Postgres with an instant GraphQL API
BaaS • MIT • Database: Postgres, with Hasura GraphQL
Nhost is a Postgres backend with auth, storage and a GraphQL API built on Hasura. It is the closest Supabase model in the list, because both sit on Postgres and both give you an API from your schema. It fits teams that want GraphQL first.
Pick it when:
- You want GraphQL on Postgres with Hasura.
- You want auth and storage in one managed service.
Trade-off: Its free tier is small: one project and 1 GB of database. Nhost does not state its hosting regions on the pages we checked, so check EU regions before you choose it for EU data.
Source: nhost.io/pricing
5. Convex: a reactive backend written in TypeScript
Backend platform (framework) • FSL-1.1-Apache-2.0 (source-available, Apache-2.0 after two years) • Database: Convex’s own database
Convex is a backend where your queries, mutations and scheduled jobs are TypeScript functions, and the client updates live. It fits frontend teams that want realtime data with little backend code.
Pick it when:
- Your team writes TypeScript on both ends and wants live queries.
- You are happy to write your backend logic in Convex functions.
Trade-off: The licence is not an open-source licence in the OSI sense: it is FSL, which turns into Apache-2.0 two years after each release. Your logic is tied to Convex functions, so moving away is real work. The pages we checked do not name an EU region.
6. Neon: serverless Postgres only
DB only • Apache-2.0 • Database: Postgres
Neon is serverless Postgres: the database, with branching and scale-to-zero, and nothing else. It fits teams that want Postgres and bring their own auth, storage and API. It is a database, not a backend.
Pick it when:
- You want Postgres with branches per Git branch.
- You build your own auth, storage and API code.
Trade-off: Neon has no auth, storage or realtime. The free plan pauses compute after five minutes idle, and that cannot be turned off. Neon is part of Databricks.
Source: neon.com/pricing
7. Self-hosted Supabase: the same product on your own server
BaaS (self-hosted) • Apache-2.0 • Database: Postgres
Self-hosted Supabase is the Supabase stack, run with Docker Compose on a server you control. It fits teams that need the Supabase feature set and must keep the data on their own hardware. It is the same product, so you do not switch APIs.
Pick it when:
- You want Supabase features with your own server and your own data location.
- You can run Linux, Docker and backups yourself.
Trade-off: You run the ops. The guide says mixing individual image tags is not guaranteed to work, and that analytics are off by default. Production also needs HTTPS, SMTP and secrets handling. Read our Supabase self-hosting guide before you start.
Supabase vs Firebase
Postgres and SQL vs Google’s NoSQL documents.
| Supabase | Firebase | |
|---|---|---|
| Database | Postgres (SQL) | Firestore (NoSQL documents) |
| Self-hosting | Yes, Docker Compose | No production self-hosting (emulator is dev only) |
| Free tier | $0: 500 MB database per project, 2 active projects, 1 GB file storage, 50K MAU; paused after 1 week idle | 1 GiB stored, 50K reads and 20K writes per day |
| EU location | Yes. Ireland, Paris, Frankfurt, Stockholm (Cloud) | Yes, eur3 or europe-west3 (Frankfurt), fixed at creation |
Pick Supabase if you want SQL, joins and an open-source stack. Pick Firebase if your app is mobile-first and already uses the Firebase SDKs.
Appwrite vs Supabase
Both are open-source backends with auth, storage and functions, and both can be self-hosted with Docker. The difference is the database. Supabase is Postgres. Appwrite has its own database API. Pick Supabase for SQL and Postgres tools. Pick Appwrite if you want a permissive BSD-3-Clause licence and a Firebase-style API.
PocketBase vs Supabase
PocketBase is one MIT-licensed Go binary with an embedded SQLite database. Supabase is a full Postgres stack in many containers. PocketBase is smaller and simpler to run. Supabase scales further, has Postgres, and has a managed option. If you run one server with a small app, PocketBase is enough. If you need Postgres or more load, use Supabase.
Neon vs Supabase
A serverless Postgres database vs a full backend.
| Neon | Supabase | |
|---|---|---|
| What it is | Serverless Postgres only | Postgres plus auth, storage, realtime and auto API |
| Free plan | $0, 1 GB per project, 100 CU-hours, scales to zero after 5 minutes | $0, 500 MB database per project, 2 active projects, 1 GB file storage; paused after 1 week idle |
| Paid pricing | Pay as you go: $0.106 per CU-hour, $0.35 per GB-month, no monthly minimum (Launch) | See supabase.com/pricing |
| EU region | Frankfurt and London (AWS; London is outside the EU) | Ireland, Paris, Frankfurt, Stockholm (London and Zurich are outside the EU) |
Pick Neon when you only need a Postgres database, you write your own auth and API, and you want branches for each Git branch. Pick Supabase when you want the database and the backend services in one product. Supabase saves work when you need auth and storage.
8. Hostim: the database next to your own backend
This is us. Read it with that in mind.
Hostim is not a BaaS. It has no auth, storage, realtime or auto-generated API. Hostim gives you managed Postgres with a hot standby and failover on every plan, daily backups kept 7 days, and your own app containers in one project. Everything runs in Germany.
Pick it when:
- You have a backend, or you want to write one, and need Postgres in the EU.
- You outgrew the BaaS model and want the database next to your own API.
- You want a flat price: €0 for 256 MB, €10 for 10 GB, see the pricing page.
Trade-off: If you need auth, storage or an API generated from your schema, Hostim does not provide them. Use Supabase, Appwrite or Firebase for that.
Which Supabase alternative should you pick?
One small binary
PocketBase (MIT, SQLite, self-host only).
GraphQL on Postgres
Nhost.
Realtime TypeScript backend
Convex (FSL, source-available).
Postgres only, bring your own backend
Neon.
Same product, your own server
Self-hosted Supabase.
Mobile apps on Google
Firebase.
Your backend, managed Postgres in Germany
Hostim.
Moving a Supabase database to Postgres elsewhere? See our Neon alternative page, and free Postgres hosting in Europe.
Not stated on the vendor pages we checked: Appwrite Cloud free storage and bandwidth limits, Nhost EU regions, Convex EU regions. Checked October 2026.
Sources
- firebase.google.com/pricing
- firebase.google.com/docs/firestore/locations
- github.com/appwrite/appwrite (BSD-3-Clause)
- appwrite.io/pricing
- github.com/pocketbase/pocketbase (MIT)
- nhost.io/pricing
- github.com/get-convex/convex-backend (FSL-1.1-Apache-2.0)
- neon.com/pricing
- neon.com/docs/introduction/regions
- github.com/supabase/supabase (Apache-2.0)
- supabase.com/docs/guides/self-hosting/docker
- supabase.com/pricing
- supabase.com/docs/guides/platform/regions
- firebase.google.com/docs/emulator-suite (development only)
- appwrite.io/docs/advanced/billing/free
- appwrite.io/docs/products/network/regions
- github.com/nhost/nhost (MIT)
- convex.dev/pricing
- github.com/neondatabase/neon (Apache-2.0)
Comparisons
See how Hostim compares.
Side by side against the platform you are moving from, or a round-up covering several at once.
Explore other alternatives
Heroku Alternative (EU)Render Alternative (EU)Railway Alternative (EU)Vercel Alternative (EU)Sevalla AlternativeNeon Alternative (EU Postgres)Fly.io AlternativeCoolify AlternativeCapRover AlternativePortainer AlternativeDokku AlternativeNorthflank AlternativeDigitalOcean App Platform Alternative
Compare several platforms at once
Frequently asked questions
What is the best open-source Supabase alternative?
Appwrite if you want a BaaS with auth, storage and functions under BSD-3-Clause. PocketBase if you want one small binary with SQLite. Self-hosted Supabase if you want the same product on your own server. Nhost is MIT-licensed and can be self-hosted with Docker Compose.
Supabase vs Firebase: which is better?
Firebase if your app is mobile-first, uses the Firebase SDKs and fits document data. Supabase if you want Postgres, SQL joins and an open-source stack. Firestore charges per read and write, so check your usage before you pick it. Firestore EU locations are fixed when the database is created.
Neon vs Supabase: which one?
Neon if you only need serverless Postgres and will write your own auth, storage and API. Supabase if you want the database plus auth, storage, realtime and an auto API. Neon’s free plan pauses compute after five minutes and it has Frankfurt and London regions. The Supabase free plan pauses a project after one week of inactivity, and Supabase Cloud has four EU regions. Supabase is the bigger product.
Can I self-host Supabase?
Yes. The self-hosting guide uses Docker Compose and requires at least 4 GB RAM, 2 CPU cores and 40 GB SSD. You run the upgrades, backups and security yourself. Read our self-hosting guide before you start.
What is the cheapest Supabase alternative?
Self-hosted PocketBase or Supabase cost only the server you rent. Among managed services, Neon’s free plan gives 1 GB per project with compute that pauses when idle. The Supabase free plan gives 500 MB per project and 2 active projects. Hostim gives Postgres from €0 for 256 MB, and €10 for 10 GB, with replicated failover on every plan. Check each price page, because free limits change.
Is there an EU-hosted Supabase alternative?
Yes, if you want a managed EU region. Supabase Cloud has Ireland, Paris, Frankfurt and Stockholm. Neon has Frankfurt (London is outside the EU). Appwrite Cloud has Frankfurt. Firebase has European Firestore locations. Hostim runs in Germany, but it is a database and container host, not a BaaS. Self-hosted Supabase or PocketBase on a European server also keeps data in the EU.
Start now
Put something live today.
Open the dashboard and deploy a Docker image, a Git repo or a template. The 5-day trial project needs no card.