Backend-as-a-Service

Self-hosted Backend-as-a-Service platforms have transformed how teams build applications by providing Firebase and Supabase-like functionality on private infrastructure. Supabase itself is open source and self-hostable, alongside alternatives like Appwrite, PocketBase, and Nhost that bundle authentication, databases, file storage, and serverless functions into a single deployable unit. PocketBase stands out for shipping as a single Go binary with an embedded SQLite database -- teams can run a full backend on hardware as small as a Raspberry Pi. The BaaS category is particularly relevant for startups and indie developers who want to move fast without surrendering control. Vendor lock-in in the BaaS space is especially painful because switching providers means migrating authentication systems, database schemas, and file storage -- a process that can take months. Self-hosting from the start eliminates this risk entirely. The 2026 landscape shows strong momentum: Appwrite crossed 40,000 GitHub stars, and PocketBase has become a go-to choice for hackathons and MVPs that may scale to production. Docker Compose deployments with integrated PostgreSQL or SQLite make these platforms accessible to solo developers. When evaluating self-hosted BaaS options, compare real-time subscription support, built-in authorization rules, client SDK quality, and how the platform handles database migrations. The trade-off is operational responsibility, but for teams with basic DevOps capability, the freedom to extend and customize backend services without vendor constraints outweighs the maintenance cost.