PocketBase: features, limits & comparisons
For one modest app, a single local binary covers data, auth, files, realtime, and an admin UI; functions are the missing piece.
functionality and fit
Recorded license: MIT.
- Collections, auth records, settings, and application data live in SQLite files under `pb_data`; uploaded files live under `pb_data/storage` by default or in configured S3-compatible storage, and schema migrations can be kept as JavaScript files in `pb_migrations`.
- Download one platform binary and run `pocketbase serve`; build from Go source only for custom extensions
Costs and editions: A source license is separate from operating costs. Hosting, storage, external APIs and commercial support may require payment.
scope and migration checks
- PocketBase is excellent for one modest app, but a single SQLite server with no built-in functions runtime cannot match Firebase's offline SDKs, global scaling, messaging, analytics, or managed operations.
- PocketBase's single SQLite binary gives up PostgreSQL compatibility, extensions, SQL tooling, row-level security semantics, edge functions, horizontal scale, and high availability.
recorded catalogue description · recorded source check 2026-08-10 · suitability checks are editorial assessments, not hands-on tests
licenseMIT
runsyour server
installDownload one platform binary and run `pocketbase serve`; build from Go source only for custom extensions
dataCollections, auth records, settings, and application data live in SQLite files under `pb_data`; uploaded files live under `pb_data/storage` by default or in configured S3-compatible storage, and schema migrations can be kept as JavaScript files in `pb_migrations`.
setupIt installs unusually cleanly, but a public deployment still needs process supervision, HTTPS/reverse proxying, backups of `pb_data`, and a deliberate upgrade routine.
recorded source check 2026-08-10 · installation not tested
compare these app workflows
These are scoped comparisons, not guarantees that PocketBase reproduces every paid feature. Follow each build guide for the implementation boundary and the collection for other options.
For one modest app, a single local binary covers data, auth, files, realtime, and an admin UI; functions are the missing piece.
the catchPocketBase is excellent for one modest app, but a single SQLite server with no built-in functions runtime cannot match Firebase's offline SDKs, global scaling, messaging, analytics, or managed operations.
the verdict →all Firebase Blaze alternatives →A drastically smaller substitute for one app: auth, files, realtime, API, and database in one binary, with no functions runtime.
the catchPocketBase's single SQLite binary gives up PostgreSQL compatibility, extensions, SQL tooling, row-level security semantics, edge functions, horizontal scale, and high availability.
the verdict →all Supabase Pro alternatives →latest catalogue source check 2026-08-10 · no votes, no pay-to-list
sources and related categories
These are sources retained with the catalogue record. Their recorded check date is not a new verification of current terms.