An alternative to Supabase, Firebase and Appwrite. Your AI agent sets it up.
Ulabase is a managed backend for web, mobile and agent apps. A coding agent sets it up from files in git. Your users' agents work on it over MCP. Your data is JSON, and sign-up, payments and email are already built in. You start from a complete app.
Free plan. No credit card. EU region in Frankfurt.
What you get with Ulabase
Six things it gives you from the first day.
Build it with AI agents
The backend is a folder of setup files in git. Claude Code or Cursor writes them, reading the Ulabase documentation over MCP. The ulabase setup command shows a dry run, then applies them. You review and ship.
Build it for AI agents too
Every service is also an MCP server. Your users ask Claude or ChatGPT for what they would look up on a screen. One permission decides what the screens and the agent may do.
Your data as JSON documents
Your app saves its objects as they are. There are no tables to design and no migrations when a field changes. Aggregations, change streams and vector search work on the same documents.
The common parts are ready
Sign-up and login with Google, teams and invitations, Stripe payments, email, webhooks and AI are features you turn on. You write and deploy no functions for them.
Starters and the Ulabase Kit
Clone a complete app in React, Angular or Vue, or an ecommerce shop. Sign-up, teams and checkout already work. The Kit is the client code they are built on, and your own screens get it with one npm install.
Open source engine, EU region
Ulabase runs RESTHeart, open source since 2014, on a standard MongoDB. If you ever leave, you run the same API yourself on the same data. Ulabase is run by a European company, and your service can live in Frankfurt.
Ulabase, Supabase, Firebase, Appwrite and PocketBase compared
Nine facts, each read on the product's own site.
Ulabase
- Database
- MongoDB, documents
- API for your app
- REST, GraphQL, MCP
- Live updates
- Change streams, over WebSocket or Server-Sent Events
- Open source
- The engine, RESTHeart (AGPL-3.0)
- Run it yourself
- Yes, RESTHeart on your MongoDB
- Managed by its maker
- Yes, in Frankfurt or Virginia; Enterprise in any AWS region
- Free plan
- Yes: 500 MB, no credit card
- A free project nobody uses
- Deactivated after 40 days without requests
- First paid plan
- €9 a month
Supabase
- Database
- PostgreSQL, tables
- API for your app
- REST, GraphQL
- Live updates
- Realtime: database changes, broadcast, presence
- Open source
- Yes (Apache-2.0)
- Run it yourself
- Yes, with Docker
- Managed by its maker
- Yes
- Free plan
- Yes: 500 MB database, 2 projects
- A free project nobody uses
- Paused after 1 week of inactivity
- First paid plan
- From $25 a month
Firebase
- Database
- Cloud Firestore, documents
- API for your app
- Client SDKs, REST
- Live updates
- Snapshot listeners in the SDKs
- Open source
- No
- Run it yourself
- No
- Managed by its maker
- Yes, on Google Cloud
- Free plan
- Yes: 1 GiB in Firestore, no payment method
- A free project nobody uses
- No inactivity rule on its pricing page
- First paid plan
- Blaze, pay as you go
Appwrite
- Database
- Its own TablesDB and DocumentsDB
- API for your app
- REST, GraphQL
- Live updates
- Realtime, over WebSocket
- Open source
- Yes (BSD-3-Clause)
- Run it yourself
- Yes, with Docker
- Managed by its maker
- Yes
- Free plan
- Yes: 2 GB storage, 2 projects
- A free project nobody uses
- Paused after 7 days without development activity
- First paid plan
- From $25 a month
PocketBase
- Database
- SQLite, embedded
- API for your app
- REST
- Live updates
- Realtime, over Server-Sent Events
- Open source
- Yes (MIT)
- Run it yourself
- Yes, it is the only way
- Managed by its maker
- No, self-hosted only
- Free plan
- Free software
- A free project nobody uses
- It runs on your server
- First paid plan
- The cost of your server
The facts about the other products were read on their sites on 17 November 2026: Supabase pricing, Supabase GraphQL, Supabase Realtime, Supabase self-hosting, Firebase pricing, Firestore REST API, Firestore listeners, Appwrite pricing, Appwrite Realtime, Appwrite inactive projects, Appwrite self-hosting, PocketBase, PocketBase realtime, PocketBase FAQ. Prices and limits change: check them before you choose.
When one of the others is the better choice
Choosing the wrong backend costs months. Pick:
- Supabase if your data is relational and you want SQL, joins and the PostgreSQL ecosystem.
- Firebase if you build on Google Cloud and want its mobile SDKs, push notifications and analytics in one place.
- Appwrite if you want to write server functions in many languages next to your backend.
- PocketBase if a single file on one small server is all your app needs, and you are happy to run it.