Open-source backend as a service
A backend as a service (BaaS) gives your app the parts every backend needs, so you don't write them from scratch: a database, an API on top of it, user sign-in, permissions, file storage and somewhere to run server code.
Apito is a BaaS with an open-source engine. You define your data models, and Apito gives you a GraphQL API and a REST API for them, along with auth, roles, storage and functions. You can run it on your own machine or use Apito Cloud.
What a BaaS usually includes
| Part | What it does | In Apito |
|---|---|---|
| Database | Stores your app's data | Cloud Free and Pro run SQLite. |
| API | Lets your app read and write data | GraphQL at api.apito.io/secured/graphql, REST at api.apito.io/secured/rest/<projectId> |
| Auth | Signs users in | Password, plus Google, Facebook, GitHub, X and LinkedIn |
| Permissions | Controls who can do what | Roles, with API keys tied to a role |
| File storage | Holds uploads | Built in |
| Server code | Runs logic you write | Cloud functions |
| Realtime | Pushes changes to clients | GraphQL subscriptions |
| Schema changes | Changes your data model over time | Staged changes, a pending list and history; a person publishes |
What Apito doesn't do yet
- No published client SDK. You call GraphQL or REST directly. There is no Flutter or JS package to install yet.
- No hosted Postgres on Cloud Free and Pro. Those plans run SQLite.
- No push notifications, analytics or crash reporting. Use a separate service for those.
- Sign-in is password plus five OAuth providers. No magic links, phone login or Apple sign-in today.
How it works
- Create a project, on Cloud or on your own machine.
- Define your models in the console or from your editor through Apito's MCP server.
- Publish the schema. Changes stay staged until you publish them.
- Call the API. Every model is available in GraphQL and REST.
- Add users and roles, and turn on the sign-in providers you need.
Open source or hosted
The Apito engine is open source under AGPL-3.0. You run it yourself and your data stays on your infrastructure. The exact install command is not printed here until it is confirmed. See the self-hosting guide.
Apito Cloud runs it for you. The Free plan gives you 2 projects on SQLite, and you don't need a card. Pro adds more room.
Who it's for
- Indie developers who want APIs and sign-in without writing a server.
- Agencies who build backends for clients.
- SaaS builders who want auth, roles and the API in one console.
How Apito compares
- Apito vs Supabase: Supabase is a Postgres platform with a large ecosystem.
- Apito vs Firebase: Firebase is Google's NoSQL platform with strong mobile SDKs.
- Hasura alternative and Strapi alternative.
FAQ
What is a backend as a service?
A hosted or self-hosted service that gives your app a database, an API, user sign-in, permissions and file storage, so you don't build and run those yourself.
Is Apito open source?
The engine is open source under AGPL-3.0. Apito Cloud is the hosted version.
Does Apito support GraphQL and REST?
Yes. Both are generated from your schema.
Does Apito have realtime?
Yes, through GraphQL subscriptions.
Is there a free plan?
Yes. 2 projects on SQLite, and no card needed.
How do I get help?
Email [email protected] or ask on Discord: https://discord.gg/Xb7p2ddC6E.
Which databases does Apito use?
Cloud Free and Pro use SQLite.