| Product | PocketBase |
| Website | pocketbase.io |
| Category | Backend / BaaS |
| License | MIT (open source) |
| Pricing | Free (self-hosted) |
What Is PocketBase?
PocketBase is a backend in a single executable file. Download one binary (~20MB), run it, and you have a database (SQLite-based), REST API, real-time subscriptions, authentication, file storage, and an admin UI. No Docker, no dependencies, no configuration files.
PocketBase targets the use case where Firebase or Supabase is more than you need, but writing a backend from scratch is more work than the project justifies. Side projects, prototypes, small SaaS apps, and internal tools all fit this niche.
Key Features
Single File
One binary. Run it, and the backend is live. The database (SQLite), file storage, and admin UI are all embedded. Your entire backend is one file and one data directory. Backup means copying those two things. Deployment means copying the binary to a server and running it.
Admin UI
A web-based admin panel where you define collections (tables), fields, relations, and API rules. Non-developers can manage data through the admin UI, and developers define the schema visually or through the Go/JS SDK.
Authentication
Email/password and OAuth2 authentication built in. User management, email verification, password reset — the auth flows that every app needs but nobody wants to build. Supports OAuth2 providers (Google, GitHub, Facebook, etc.) with minimal configuration.
Real-Time Subscriptions
Subscribe to changes on a collection and receive updates via Server-Sent Events. When a record is created, updated, or deleted, connected clients receive the change instantly. For live dashboards, chat features, and collaborative apps.
Extend with Go or JS
PocketBase is a Go framework. You can use it as a library and extend it with custom routes, hooks, and middleware. Alternatively, use the JavaScript SDK from any frontend framework.
Who Is This For?
- Indie developers building side projects
- Prototypers who need a backend in minutes
- Small SaaS apps that don’t need distributed databases
- Anyone who wants Firebase simplicity without vendor lock-in
Pros
- Single binary, zero dependencies
- Built-in auth, file storage, admin UI
- Real-time subscriptions
- MIT open source
- Incredibly easy to deploy
- Extensible with Go
Cons
- SQLite only (no PostgreSQL/MySQL)
- Not designed for horizontal scaling
- Single-server architecture
- Young project (rapid API changes)
- Limited to what SQLite can handle
Verdict
PocketBase is the most frictionless way to get a backend running. Single binary, zero config, built-in auth and real-time — there is nothing faster for prototypes, side projects, and small applications. The SQLite foundation means your data is a single file, backup is a copy, and deployment is uploading one binary.
The limitation is scale. PocketBase runs on a single server with SQLite, so it won’t handle the traffic of a large SaaS. For applications that will grow past what one server can handle, start with Supabase or build on PostgreSQL. For everything else — and “everything else” is most projects — PocketBase is faster to set up and easier to maintain than any alternative.