From the PocketBase Cloud team.
Guides, tutorials, and deep dives on shipping full-stack apps.
FeaturedcomputePro Compute Now Runs in 12 Locations
Five new regions — Japan, India, and three US regions — join the seven existing Pro locations, so your dedicated compute can sit closer to your actual users.
nuxtHow to Deploy a Nuxt App
Deploy a Nuxt 3 app — server-rendered or statically generated — to PocketBase Cloud, with HTTPS and a database in the same project.
sveltekitHow to Deploy a SvelteKit App
Deploy a SvelteKit app — static or server-rendered — to PocketBase Cloud. Which adapter to pick, and the one command that ships each kind.
featuresEvery deploy leaves a trail: deployment history on every resource
Each PocketBase instance, frontend, and backend now keeps its deploy history on its detail page — what shipped, when, and whether it landed.
featuresOff the Free cluster in five steps
Upgraded to a paid plan but the instance is still on the Free cluster? Back up, restore at creation, repoint, delete — about five minutes.
pocketbaseYour PocketBase has knobs now: runtime flags and a syncable superuser
Dev mode, hooks pool, and query timeout are editable per instance from the portal or CLI, and the managed superuser can be rotated without the old password.
pocketbaseBring your PocketBase with you: restore a backup into a new instance
pbc pocketbase create --backup provisions an instance with your backup already restored — schema, records, files, and superusers. Same thing in the portal's create form.
FeaturedcliOne Step to Deploy from GitHub Actions
An official action and pbc ci init replace the 40-line hand-written workflow — and close a real credential leak along the way.
pricingThe Free plan now has an API rate limit (and why that's good news)
Free PocketBase instances can serve 500 API requests per hour. Here's what that means for your project, how the limit behaves, and how to lift it.
FeaturedfeaturesCustom Domains for PocketBase: Bring Your Own URL
Serve your PocketBase instance from a domain you own — with automatic HTTPS, one DNS check, and full CLI support. The feature I've been asked for more than any other.
clipbc locations: Know Where a Deploy Can Land
The new CLI command lists the regions the platform can actually deploy to for your plan — and --location now refuses a region before your deploy fails on it.
cliOne Deploy Command for Any Directory
pbc deploy reads the directory you're standing in, works out whether it's a PocketBase instance, a frontend, or a backend, and runs that deploy — same flags, same output, one less decision.