PocketBase Cloud

Best Self Hosted Alternatives to PocketBase Cloud

A curated collection of the 4 best self hosted alternatives to PocketBase Cloud.

Managed cloud hosting for PocketBase that provides a hosted backend-as-a-service: realtime database, authentication, file storage, admin UI and API endpoints to build and deploy apps without self-hosting.

Alternatives List

#1
PocketBase

PocketBase

Open-source Go backend providing embedded SQLite, realtime (SSE) subscriptions, auth (JWT/OAuth2), file storage, admin UI and REST-style APIs for web and mobile apps.

PocketBase screenshot

PocketBase is a compact open-source backend written in Go that provides an embedded SQLite database, realtime subscriptions, user authentication, file storage and a built-in admin dashboard. It can be used as a standalone single-file executable or as an embeddable Go library for custom apps. (github.com)

Key Features

  • Embedded SQLite database with schema builder, validations and realtime change subscriptions (Server-Sent Events). (github.com)
  • Authentication and authorization: email/password, token-based (JWT) auth, OAuth2 provider integrations and auth token refresh/management. (pocketbase.io)
  • File storage with local or S3-compatible backends, file uploads attached to records and automatic thumbnail generation. (pocketbase.io)
  • Built-in Admin dashboard UI for managing collections, records, files and users; extendable via Go hooks and an embedded JavaScript VM. (github.com)
  • REST-style JSON APIs plus official SDKs (JavaScript, Dart) for quick client integration and realtime subscribe/unsubscribe helpers. (github.com)
  • Small footprint single binary distribution with cross-platform prebuilt executables and example starter projects. (pocketbase.io)

Use Cases

  • Prototyping and internal tools where a minimal backend (DB + auth + file storage + admin UI) is needed quickly.
  • Client-driven web or mobile apps (SPAs, PWAs, React/Flutter apps) that need realtime updates and a simple REST API.
  • Lightweight CMS-like applications, admin dashboards and hobby/side projects requiring a portable backend.

Limitations and Considerations

  • Single-server architecture with an embedded SQLite store; no built-in sharding or multi-node clustering, so horizontal scaling is limited. (github.com)
  • Realtime uses SSE (unidirectional) rather than WebSockets; reverse proxy configuration must support long-lived HTTP streams. (pocketbase.io)
  • Project is under active development and the maintainers note potential breaking changes before a stable v1.0; review changelogs and migration notes for production upgrades. (github.com)
  • Offline-first sync is not provided out-of-the-box; client-side handling is required for offline scenarios. (github.com)

PocketBase offers a pragmatic, compact backend for many web and mobile workflows where simplicity, portability and realtime updates matter. It is especially suited for prototypes, internal apps and small production services that accept the single-server SQLite tradeoffs.

55.3kstars
3kforks
View Details
#2
Kinto

Kinto

Kinto is a lightweight JSON document store with an HTTP API, built-in permissions, sharing, and client synchronization, designed for offline-first and distributed apps.

Kinto screenshot

Kinto is a minimalist JSON storage service that exposes a RESTful HTTP API for storing and retrieving JSON records. It is designed to support sharing and synchronization workflows, making it a good fit for offline-first and distributed applications.

Key Features

  • RESTful API for JSON records organized into buckets and collections
  • Built-in permissions model with support for groups and permission inheritance
  • Synchronization support designed for clients that need to reconcile changes
  • Pluggable storage backends, including in-memory for development and PostgreSQL for production
  • Designed to be embedded as a generic storage layer for applications

Use Cases

  • Backend storage for offline-first apps that need sync and conflict-aware updates
  • Shared JSON data store for teams or services with fine-grained access control
  • Lightweight application backend for storing configuration, preferences, or metadata

Limitations and Considerations

  • Primarily focused on JSON document storage and sync; not intended as a full relational database replacement
  • Production deployments typically rely on PostgreSQL, so operational requirements depend on that stack

Kinto provides a focused, API-first approach to JSON storage with strong primitives for permissions and synchronization. It is well-suited when you need a small, reliable service to store, share, and sync JSON documents across clients and environments.

4.4kstars
420forks
View Details
#3
TrailBase

TrailBase

TrailBase is a fast, single-executable Firebase alternative with type-safe REST and realtime APIs, built-in auth, admin UI, WebAssembly extensibility, and SQLite storage.

TrailBase screenshot

TrailBase is an open-source application server designed as a lightweight Firebase-style backend you can run as a single executable. It provides database-backed REST and realtime APIs, built-in authentication, an optional admin UI, and a WebAssembly runtime for extending server-side logic.

Key Features

  • Single-binary deployment for consistent environments (dev, testing, edge, production)
  • Type-safe RESTful CRUD APIs exposing tables and views
  • Realtime subscriptions for push-based data change sync
  • Built-in authentication with JWT access tokens and refresh tokens
  • Optional built-in admin dashboard for configuration and data exploration
  • Authorization via ACLs and SQL-based access rules
  • Built-in WebAssembly runtime for extending functionality with guest languages

Use Cases

  • Backend-as-a-service for mobile, web, and desktop applications
  • Realtime data sync for collaborative or event-driven apps
  • Lightweight deployments where SQLite and a single executable simplify operations

Limitations and Considerations

  • SQLite-based architecture may not fit workloads requiring a separate scalable SQL cluster
  • Extending behavior via WebAssembly requires building and managing WASM components

TrailBase is a good fit when you want a fast, low-ops backend that still provides core BaaS capabilities like auth, realtime updates, and API generation. Its single-binary approach and standards-oriented design help reduce operational complexity and vendor lock-in.

4.4kstars
123forks
View Details
#4
bknd

bknd

bknd is a lightweight Firebase/Supabase alternative that provides a modular backend with REST API, admin UI, auth, media, and workflows, deployable across many JS runtimes.

bknd screenshot

bknd is a lightweight backend platform that provides core primitives most applications need, including data management, authentication, media handling, and workflows. It is designed to run in many JavaScript runtimes and can be deployed standalone or embedded into popular web frameworks via adapters.

Key Features

  • Modular, opt-in building blocks for data, auth, media, and workflow automation
  • Integrated admin UI for managing schema, data, and backend configuration
  • Instant REST API with OpenAPI support and a type-safe TypeScript SDK
  • Adapter-first architecture for multiple runtimes and infrastructure providers
  • Supports SQL backends including SQLite variants and PostgreSQL
  • Storage adapters for S3/S3-compatible providers and filesystem-based storage

Use Cases

  • Build MVPs and prototypes with a ready-to-use backend and admin panel
  • Create API-first apps that need a portable, framework-agnostic backend
  • Run SaaS backends with user management and multi-tenant data isolation patterns

Limitations and Considerations

  • Requires Node.js 22.13+ for certain Node-based deployments
  • Actively developed project; backward compatibility may change before 1.0

bknd is a practical choice when you want a compact backend that can be deployed across environments without committing to a single vendor. Its adapter-based approach makes it suitable for teams that want control over databases, storage, and runtime choices while keeping development simple.

3.5kstars
127forks
View Details

Why choose an open source alternative?

  • •Data ownership: Keep your data on your own servers
  • •No vendor lock-in: Freedom to switch or modify at any time
  • •Cost savings: Reduce or eliminate subscription fees
  • •Transparency: Audit the code and know exactly what's running