PocketBase

Creating a backup in a Docker setup fails because the temporary file cannot be renamed across devices into the backups directory.

Affects: Docker users

Restoring a production backup into a local instance on the same version fails with a generic error and nothing in the terminal logs.

Opening the admin UI is very slow, and while it loads a production app reading the same database through the JS SDK is blocked from returning results.

Affects: teams running production apps on the same instance

Viewing a collection of large photos in the dashboard triggers many concurrent thumbnail resizes that use far more memory than the image sizes and get the process OOM-killed.

Affects: teams storing high resolution photos

A user wanting a lightweight Firebase alternative finds PocketBase cannot store null values even though SQLite supports them, forcing magic constants or extra boolean columns.

Affects: developer storing optional numeric data

A developer says PocketBase would fit many projects if it supported Postgres, because corporate platform teams already handle Postgres replication, failover and backups.

Affects: developer in a corporate environment

A user of several PocketBase projects says it is great for solo developers but lacks a built-in bulk insert.

Affects: solo developer

A user behind Cloudflare cannot upload files above 100 MB through PocketBase and proposes chunked uploads reassembled on the server.

Affects: teams hosting behind Cloudflare

A company using PocketBase for internal services wants API keys with admin permissions so other systems do not need a stored admin password.

Affects: companies integrating internal services

A developer argues PocketBase has no rate limiting, so attackers can spam record creation, mass-create users or page through the whole database. The only option is per-route reverse proxy rules, which are hard to keep in sync.

Affects: developers of public-facing apps

A developer building a server-rendered SaaS template found PocketBase's built-in auth only works with SSR after writing their own cookie middleware. They question whether PocketBase is worth it given its client-library-to-DB model.

Affects: developer building a server-rendered SaaS template

Duplicating a record that has files requires downloading and re-uploading every file, which also changes filenames and forces reference updates. The user asks for a built-in duplicate endpoint.

Affects: developers using record attachments

The developer had to build their own CSV loader to get data into PocketBase because no import path exists.

Affects: developer building a webapp for a client

Deploying behind an nginx sub-path only partially works because the admin UI still requests assets from the root path, and the application URL setting does not help.

Affects: self-hosters behind a reverse proxy

For data like landing page text, users must create a whole collection per piece of data holding a single row. The user asks for a better abstraction.

Affects: developers storing site settings or marketing content