Your PocketBase, without the server underneath it.
The same single binary you would run yourself, on a machine somebody else keeps up.
It is ordinary PocketBase
Not a fork. The PocketBase docs describe your instance exactly.
Backups you can take yourself
A zip of the whole pb_data directory, on demand, from the admin.
One machine, one region
Its own container and SQLite file, in a region you chose.
No lock-in to undo
Point the SDK elsewhere and go. No format to convert.
Your whole backend, without writing one.
One open-source program that is already your database, REST API, auth, file storage and job scheduler.
// JavaScript SDK
import PocketBase from 'pocketbase';
const pb = new PocketBase('https://my-pocketbase.pocketbasecloud.com');
// list and search 'posts' with filters and sorting
const list = await pb.collection('posts').getList(1, 50, {
filter: 'published = true && created > @todayStart',
sort: '-created,title',
expand: 'author',
});Ready to use out of the box
Collections, auth and file storage are there the moment the instance boots. Nothing to wire together first.
Design your tables in a visual editor. No SQL, no migration files.
Every table gets a REST API the moment you create it - filters, sorting, access rules. You write none of it.
Sign-up, passwords and email verification are already built. Add Google or GitHub sign-in with two keys.
Upload files straight onto a record. Thumbnails are made on request, not on upload.
Subscribe once and get changes as they happen. No polling loop, no second service.
Add your own endpoints in JavaScript, or run code before and after a record is saved.
Cron jobs on the same instance. No worker service, no external scheduler.
// JavaScript SDK
import PocketBase from 'pocketbase';
const pb = new PocketBase('https://my-pocketbase.pocketbasecloud.com');
// list and search 'posts' with filters and sorting
const list = await pb.collection('posts').getList(1, 50, {
filter: 'published = true && created > @todayStart',
sort: '-created,title',
expand: 'author',
});Administer it without opening the dashboard
The portal and the CLI reach the same instance. Create it, point the CLI at it, and the collections, records, hooks and backups are all one command away.
The same tool, every day after
pbc cloud pb lsevery instance and its statuspbc cloud pb hooks pushship a JS hook from the repopbc cloud env setset an encrypted variablepbc cloud logsfollow the instance log
Instance commands act on whichever instance "pbc use" selected, so the same script works against a colleague's instance or your own.
Read the docsPut your next project on PocketBase Cloud.
No lock-in: your data is a stock PocketBase directory you can download as a zip and restore anywhere, any time. How that works.