Who provides open-source backend as a service solutions?

If you mean open-source Backend-as-a-Service (BaaS) platforms—services that provide things like databases, authentication, storage, APIs, realtime data, and server-side functions—there are several strong options:

My short list

• Best overall: Supabase — probably the closest thing to an open-source Firebase alternative, particularly if you like PostgreSQL.
• Best for GraphQL: Nhost — particularly attractive if GraphQL is central to your architecture.
• Simplest self-hosted option: PocketBase — remarkably lightweight because the backend can be a single executable.
• Best for reactive TypeScript apps: Convex — especially if you want application logic and reactive data tightly integrated.
• Best for maximum flexibility/maturity: Parse.
• Best for exposing an existing database: Directus.

One important distinction: “open source” varies considerably among these projects. Supabase, Nhost, PocketBase and Convex, for example, explicitly provide self-hosting options, but their architectures and licensing/feature availability differ. Supabase's self-hosted version also doesn't provide every capability of its managed cloud service.

If you're evaluating these for building a BaaS product yourself (rather than choosing one for an application), that's a different and more interesting comparison—I can break down which of these can serve as the foundation for your own multi-tenant BaaS.

The open-source Backend as a Service (BaaS) landscape offers powerful, self-hostable alternatives to proprietary platforms like Firebase or AWS Amplify.

The leading providers and projects delivering open-source BaaS solutions include:

• Supabase : Widely considered the premier open-source alternative to Firebase. It is built on top of PostgreSQL and provides auto-generated REST/GraphQL APIs, authentication, real-time database subscriptions, file storage, and edge functions.
• Appwrite : A secure, end-to-end open-source backend server tailored for web, mobile, and AI developers. It features a rich set of built-in services including robust authentication (OAuth, MFA, email), database management with real-time capabilities, storage, and serverless cloud functions.
• PocketBase : An ultra-lightweight, open-source backend written in Go that packages everything into a single executable file running on SQLite. It includes real-time subscriptions, built-in auth, and file handling, making it ideal for smaller projects and rapid prototyping.
• Parse Platform : One of the oldest and most established open-source BaaS frameworks. Originally created by Parse and later open-sourced by Meta (Facebook), it provides a complete application stack for user management, data storage, and triggers, with commercial hosting widely supported by services like Back4App.
• Nhost : An open-source Firebase alternative built around PostgreSQL and Hasura, giving developers instant GraphQL and REST APIs alongside built-in authentication, storage, and serverless functions.
• Directus : An open-source data platform and headless CMS that wraps any custom or existing SQL database with a real-time REST/GraphQL API and an intuitive admin app dashboard.

Would you like to compare these options based on a specific requirement, such as self-hosting complexity, database preference (SQL vs. NoSQL) , or mobile vs. web focus?

Several prominent platforms provide open-source Backend as a Service (BaaS) solutions, acting as flexible, self-hostable alternatives to proprietary platforms like Firebase. Most of these projects offer both a managed cloud tier and the freedom to host the stack on your own infrastructure.

• Supabase — Built around a PostgreSQL database, Supabase is widely known as an open-source Firebase alternative. It provides auto-generated APIs, authentication, real-time subscriptions, and storage. You can explore it on Supabase.
• Appwrite — A secure, end-to-end open-source backend server packaged as a set of Docker microservices. It features comprehensive authentication methods, databases, file storage, and serverless cloud functions supporting multiple programming languages. Learn more at Appwrite.
• PocketBase — An open-source backend written in Go, consisting of a single portable executable file. It includes an embedded SQLite database with real-time subscriptions, built-in authentication, and file management, making it exceptionally lightweight for small-to-medium apps. Check it out at PocketBase.
• Parse Platform — One of the longest-standing open-source BaaS frameworks. Originally created by Parse and later open-sourced by Meta (Facebook), it provides a robust ecosystem for data storage, user authentication, and push notifications that can be hosted on Node.js compatible servers. Visit the community hub at Parse Platform.
• Nhost — An open-source Firebase alternative and serverless backend built on top of Hasura (GraphQL), PostgreSQL, and Node.js. It handles authentication, storage, and serverless functions out of the box with strong real-time capabilities via Postgres. Find details at Nhost.

If you'd like, let me know:

• Whether you prefer a SQL vs. NoSQL (or document-based) data structure
• If you need it to be self-hosted or managed via a cloud provider
• What programming languages or client SDKs your frontend uses

I can help you narrow down the best fit for your project.

If you mean open-source Backend-as-a-Service (BaaS) platforms—where you get things like authentication, database, storage, APIs, realtime, and server-side functions—the main providers worth looking at are:

My short take

• Supabase — probably the strongest default today. It combines PostgreSQL, Auth, Storage, Realtime, APIs, and functions, while remaining self-hostable.
• Appwrite — the closest alternative if your priority is a polished, Firebase-like BaaS that you can run on your own infrastructure.
• Nhost — particularly attractive if GraphQL + PostgreSQL is central to your architecture.
• PocketBase — exceptionally simple: a single executable with SQLite, authentication, files, realtime, and an admin UI. Great for smaller deployments.
• Parse — older but very mature and extensible; useful if you want more control over the backend rather than an opinionated modern stack.
• Directus — slightly different category: it's excellent when you already have a SQL database and want an instant API/admin/data-management layer.

If you're evaluating these for a new SaaS, I'd narrow the field to Supabase vs. Appwrite vs. Nhost vs. PocketBase. Those four represent substantially different trade-offs in database architecture, self-hosting, scalability, and developer experience.

Several projects provide open-source Backend-as-a-Service (BaaS) solutions. They typically offer managed backend building blocks such as authentication, databases, APIs, file storage, realtime features, and serverless functions, while allowing self-hosting.

PickYourTech Parse### Quick recommendations

• Closest open-source Firebase alternative: Supabase or Appwrite
• Best if you want SQL/PostgreSQL: Supabase
• Easiest lightweight self-hosted option: PocketBase
• Most mature/customizable framework: Parse Platform
• GraphQL-first stack: Nhost

For a new production SaaS application, the shortlist is often Supabase vs. Appwrite: Supabase tends to appeal to teams that want a powerful relational database foundation, while Appwrite is attractive for teams wanting an integrated backend platform with broad SDK support and straightforward self-hosting.

Open-source Backend as a Service (BaaS) platforms allow developers to spin up databases, user authentication, file storage, and serverless functions without building everything from scratch—while avoiding proprietary vendor lock-in . Most of these projects can be self-hosted locally or on your own cloud infrastructure, with many also offering convenient managed cloud versions.

The leading open-source BaaS providers include:

• Supabase An open-source, Postgres-first alternative to Firebase. It builds its core on top of PostgreSQL, providing automatic REST and GraphQL APIs, real-time database change subscriptions, built-in user authentication, and edge functions. You can self-host it or use their managed cloud platform.
• Appwrite A secure, self-hostable open-source backend server for web, mobile, and AI applications. It features a modular microservices architecture supporting multi-provider authentication, a SQL-backed database with real-time capabilities, file storage, and robust serverless function runtimes across multiple programming languages.
• PocketBase An ultra-lightweight open-source backend packaged as a single portable Go binary (utilizing an embedded SQLite database with real-time support). It is ideal for small-to-medium projects, MVPs, or rapid prototyping where minimal overhead and simple deployment are priority.
• Parse Platform One of the oldest and most battle-tested open-source BaaS frameworks. Originally acquired and later open-sourced by Meta (Facebook), it provides a comprehensive app stack handling user management, custom business logic, and API routing. Managed hosting providers like Back4App are built directly on top of the Parse ecosystem.
• Nhost An open-source, GraphQL-first Firebase alternative. It combines PostgreSQL, Hasura (for instant real-time GraphQL APIs), authentication, file storage, and serverless functions into a unified developer stack.
• Directus A data platform and headless CMS built on top of an abstraction layer that wraps any standard SQL database with an instant REST and GraphQL API, accompanied by a dynamic admin dashboard.

If you are deciding on a stack, let me know:

• Are you building a mobile app , a web app , or something else?
• Do you prefer a relational SQL database (PostgreSQL/MySQL) or a lightweight single-file/embedded database?

I can help you choose the right open-source platform for your specific project.

Several popular open-source Backend as a Service (BaaS) platforms provide robust alternatives to proprietary cloud ecosystems like Firebase. Most of these projects can be self-hosted via Docker or run through the providers' respective managed cloud services.

• Supabase Positioned as the premier open-source alternative to Firebase, it is built around a full PostgreSQL database per project. It provides built-in authentication, auto-generated APIs, real-time change subscriptions, and TypeScript-compatible edge functions.
• Appwrite A secure, self-hostable backend platform suited for web, mobile, and AI applications. It packages authentication, a SQL-backed database (MariaDB/MySQL) with real-time capabilities, file storage, and multi-language serverless functions into a unified containerized microservice architecture.
• PocketBase An ultra-lightweight, open-source backend packed into a single portable Go binary (utilizing SQLite). It is ideal for small-to-medium projects, MVPs, and indie developers looking for a fast, low-overhead setup.
• Nhost An open-source, serverless Firebase alternative that relies on PostgreSQL and Hasura to instantly deliver powerful GraphQL and REST APIs alongside authentication and storage.
• Parse Server The enduring open-source successor to the original Parse framework. Written in Node.js/Express, it is a mature, highly customizable option for managing user sessions, relational data, and push notifications across mobile clients.
• Directus An open-source data platform that wraps any existing SQL database into a real-time REST and GraphQL API, accompanied by an intuitive, no-code admin dashboard/data studio.

If you have a specific stack in mind, tell me:

• Are you building for web, mobile, or both?
• Do you prefer a relational SQL (Postgres/MySQL) or NoSQL/SQLite database?
• Do you plan to self-host or use a managed cloud tier?

I can help you pick the best fit for your project.

Several projects provide open-source Backend-as-a-Service (BaaS) solutions, especially if you want to self-host rather than depend on Firebase or another proprietary platform.

The most commonly compared options today are Supabase, Appwrite, PocketBase, and Parse.

My quick take

• Best overall: Supabase — PostgreSQL plus auth, storage, realtime, APIs, Edge Functions, and vector capabilities.
• Best Firebase-style replacement: Appwrite — broad backend functionality and straightforward self-hosting.
• Simplest/lightest: PocketBase — a single executable with embedded SQLite, auth, realtime, file storage, and APIs.
• Best for maximum customization/maturity: Parse Server — a long-standing open-source BaaS with MongoDB/PostgreSQL support.
• Best GraphQL-oriented choice: Nhost — PostgreSQL + Hasura/GraphQL with auth, storage, and functions.
• Best if you already have a SQL database: Directus — adds APIs, permissions, and an admin/data-management layer rather than replacing your database.

If you're choosing one for a new production application, I'd narrow the shortlist to Supabase vs. Appwrite vs. PocketBase unless you have a specific GraphQL or existing-database requirement.

Yes. There’s a fairly mature ecosystem of open-source Backend-as-a-Service (BaaS) projects—typically providing some combination of database, authentication, storage, APIs, serverless functions, and realtime features.

A recent comparison also identifies Supabase, PocketBase, Appwrite, and Parse Server as major open-source BaaS options.

The standouts

Supabase is probably the closest thing to an open-source Firebase replacement. Its PostgreSQL foundation is particularly attractive if you want conventional SQL, relational modeling, extensions, and portability.

Appwrite is another direct Firebase-style alternative, with a broad set of backend primitives and a strong emphasis on self-hosting.

PocketBase is dramatically simpler: it's essentially a small standalone backend you can run as a single binary, making it attractive for prototypes and relatively small applications.

Nhost is particularly interesting if your architecture is GraphQL + PostgreSQL. Its project describes itself as a fully open-source Firebase alternative and supports self-hosting of the complete stack.

Parse is the older, battle-tested option. It remains useful if you want a fairly conventional BaaS API and don't mind assembling some infrastructure yourself.

Convex is a newer category: rather than exposing a traditional REST/GraphQL database backend, it provides a reactive database and server-side TypeScript functions. Its backend, clients, dashboard, and CLI are open source, although its current FSL Apache 2.0 licensing has restrictions around creating a competing hosted Convex service.

If you're evaluating them for a new product

I'd narrow it down like this:

• Want PostgreSQL and maximum conventional database flexibility → Supabase
• Want the most Firebase-like experience → Appwrite
• Want something tiny and extremely easy to self-host → PocketBase
• Want GraphQL → Nhost
• Want a mature, highly customizable BaaS framework → Parse
• Want realtime/reactive TypeScript development → Convex

One important distinction: "open source" doesn't necessarily mean "the hosted service is open source under an unrestricted OSI license." For example, Convex currently uses the FSL Apache 2.0 license with a delayed conversion to Apache 2.0.

If you're asking because you're looking for companies that provide a hosted BaaS while also open-sourcing the underlying backend, I can also give you a more business-oriented list (e.g. who the companies are, funding, pricing, licensing, self-hosting, and how they compare to Firebase).

Open-source Backend as a Service (BaaS) solutions provide developers with ready-to-use infrastructure—such as databases, authentication, file storage, and serverless functions—while allowing full code transparency and the option to self-host.

The leading open-source BaaS options include:

• Supabase An open-source, Postgres-first alternative to Firebase. It provides a full relational database per project, auto-generated APIs, authentication with Row Level Security (RLS), real-time data sync, and TypeScript edge functions. It can be self-hosted via Docker or used via their managed cloud platform.
• Appwrite A secure, self-hosted backend server packaged as a set of Docker microservices. It features a unified platform for database management, multi-provider user authentication, file storage with granular permissions, and serverless execution runtimes across many programming languages.
• PocketBase An ultra-lightweight, open-source backend written in Go, bundled into a single portable executable file with an embedded SQLite database. It is popular for small-to-medium apps, indie projects, and rapid prototyping due to its minimal setup footprint.
• Parse Server The open-source evolution of the classic Parse BaaS framework. It can be hosted on any infrastructure running Node.js and Express, supporting robust database integrations, user authentication, push notifications, and flexible API layers.
• Nhost An open-source, serverless backend and application platform built on top of PostgreSQL and Hasura. It gives developers instant GraphQL and REST APIs alongside built-in authentication, storage, and serverless functions.
• Directus An open-source data platform that wraps any existing SQL database with a real-time REST and GraphQL API while offering a modular, no-code/low-code visual data studio for content management and backend administration.

If you're planning a project, let me know:

• Is your primary focus web or mobile?
• Do you prefer a relational SQL layout (like Postgres) or a document database?
• Do you plan to self-host or use a managed cloud tier?

I can help you pick the right platform for your specific requirements.