The only BaaS where every piece is replaceable
Describe your backend needs to an AI agent. It assembles PostgreSQL, MinIO, SuperTokens, and more from open source services you own forever.
Open Source Cloud (OSC) is a managed platform for 200+ open source services with zero vendor lock-in. Ask the OSC architect AI to compose your backend stack from open source services.
Your mobile BaaS, composed
Tell the AI what your app needs. It provisions each open source service and hands you the connection strings.
| Need | Service on OSC |
|---|---|
| Auth | SuperTokens |
| Database | PostgreSQL |
| Realtime | Centrifugo |
| Push Notifications | ntfy |
| Object Storage | MinIO |
| Serverless Functions | Web Runner |
| Search | Meilisearch |
200+ Backend Services, All Open Source
Pick only what your app needs from a composable catalog. No bundled proprietary services, no hidden dependencies — each service is an independent open source project.
Database
PostgreSQL, CouchDB
Authentication
SuperTokens, OpenAuth, Keycloak
File Storage
MinIO (S3-compatible)
Realtime
Centrifugo, Valkey (pub/sub)
Search
Meilisearch
Caching
Valkey
Monitoring
Uptime Kuma
Composable vs Bundled vs Single-Stack
Compare the three approaches to open source backend infrastructure.
| Feature | Proprietary BaaS | Open-source single-stack | OSC |
|---|---|---|---|
| Services | Bundled, proprietary | One project | 200+ independent open-source services |
| Lock-in | High (proprietary APIs) | Medium (single project dependency) | Zero (standard APIs, self-host anytime) |
| MCP support | No | No | Yes |
| Portability | Vendor migration required | Re-deploy one project | Change a connection string |
Frequently Asked Questions
What is an open source BaaS?
An open source Backend-as-a-Service (BaaS) provides the same managed infrastructure as commercial BaaS platforms — databases, authentication, file storage, search — but every component is an open source project. You get managed convenience without proprietary lock-in. OSC deploys 200+ open source services on demand, meaning you compose only the pieces your app actually needs.
How does MCP composition work?
MCP (Model Context Protocol) lets AI assistants like Claude interact directly with OSC. Connect your AI agent to mcp.osaas.io, then describe your backend needs in plain language. The AI provisions each service — PostgreSQL, MinIO, SuperTokens — and returns connection strings. No dashboards, no YAML, no DevOps knowledge needed.
How do I avoid backend lock-in?
Use open source software with standard APIs. When every component you rely on — database, auth, storage — speaks a standard protocol (PostgreSQL wire, S3, OIDC), you can move it anywhere. OSC enforces this by only hosting unmodified open source projects. There is no proprietary OSC API your app calls. If you want to self-host, you grab the same Docker image and run it anywhere.
Can I replace a proprietary BaaS with OSC?
Yes. Each BaaS category has a well-established open source equivalent on OSC: SuperTokens for authentication, PostgreSQL for your database, MinIO for object storage, Meilisearch for search, and Centrifugo for realtime messaging. OSC manages all of them — the switch is an operational question, not a capability question.
Ready to Compose Your Backend?
Connect your AI agent to OSC via MCP and describe the stack your app needs. It provisions every piece in minutes.
Compose your BaaS with AIReplacing Firebase specifically? See our Firebase alternative guide →