PocketBase
Single-file open-source backend — SQLite, auth, realtime, and admin UI packed into one Go binary.
Last commit 2026-06-01
PocketBase is the most radical simplification in the self-hosted backend category: the entire stack — SQLite database, REST API generator, authentication, realtime subscriptions, file storage, and a web admin dashboard — ships as a single Go binary under 25 MB. There is no Docker Compose file, no Postgres installation, no Node runtime, and no separate services to wire together. Download one executable, run it, and the admin interface is live on port 8090 within seconds.
The data model maps collections to SQLite tables. The auto-generated REST API exposes standard CRUD endpoints for every collection you create, and a rule engine in the admin dashboard lets you write access expressions without touching code — for example, locking record reads to the authenticated owner in a single line. Realtime subscriptions use server-sent events, so any client can watch a collection or a specific record and receive changes the moment they happen.
Extension points exist for custom server logic. Embedding PocketBase as a Go library and registering hooks is the primary path for compiled custom behavior. The bundled GOJA JavaScript engine supports lighter scripting for teams that prefer not to write Go. File storage backends support local disk or any S3-compatible service, keeping cloud storage options open.
The SQLite foundation caps concurrent write throughput — high-write applications should evaluate Postgres-backed alternatives instead. There is no managed cloud tier, so you own every aspect of hosting, backups, and upgrades. For personal projects, internal dashboards, prototype APIs, and small-audience applications, that trade-off is routinely worth accepting.
Key features of PocketBase
- Single Go binary under 25 MB — no Docker, Postgres, or external dependencies
- SQLite database with auto-generated REST API for every collection
- Built-in Auth supporting email/password, OAuth providers, and anonymous accounts
- Realtime subscriptions via server-sent events for any collection or individual record
- Web-based admin dashboard for data browsing, schema editing, and rule configuration
- Extensible via Go hooks (embed as a library) or JavaScript via the bundled GOJA engine
- File storage with local disk or S3-compatible remote backend
Pros
- Zero external dependencies — one binary is the entire production backend
- Tiny resource footprint runs comfortably on a $5/month VPS or a Raspberry Pi
- MIT license with no usage caps, no telemetry, and no managed-tier required
Cons
- SQLite write concurrency ceiling makes it unsuitable for high-write production workloads
- No managed cloud offering — you own hosting, backups, and all upgrade operations
- Single-node architecture rules out horizontal scaling
PocketBase pricing
Free / self-host · open-source · MIT
Solo developers, indie hackers, and small teams who need a complete self-hosted backend with zero infrastructure complexity.
PocketBase is an alternative to
Head-to-head comparisons
Frequently asked questions
Is PocketBase open source?
Yes. PocketBase is open source (MIT), so you can read the code, self-host it, and avoid vendor lock-in.
How much does PocketBase cost?
PocketBase starts at Free / self-host on a open-source model. Self-hosting can reduce that to infrastructure cost only.
Can I self-host PocketBase?
Yes — PocketBase supports self-hosting, giving you full data ownership.