The backend is PocketBase. The server work is ours.
The official docs just work
Not a fork. Every PocketBase guide and SDK works as written.
Your data, a click away
Download your whole database and uploaded files as one zip, whenever you want.
Your data stays where you put it
Its own container and database, in the region you chose.
Leave any time
Restore that zip on any PocketBase and point your app at it. Nothing to convert.
Your whole backend, without writing one.
Database, REST API, auth, files and jobs in one open-source program.
// 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 tables in a visual editor. No SQL.
Every table gets a REST API with filters, sorting and access rules.
Sign-up and email verification built in. Add Google or GitHub with two keys.
Upload files onto a record. Image thumbnails included.
Subscribe once and get changes live. No polling.
Add endpoints in JavaScript, or run code around a save.
Run digests and cleanups on a schedule.
// 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',
});Manage 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 pocketbase lsevery instance and its statuspbc pocketbase hooks pushship a JS hook from the repopbc env setset an encrypted variablepbc logsfollow the instance log
Instance commands act on whichever instance "pbc admin use" selected, so the same script works against a colleague's instance or your own.
Read the docsKnow your bill before the month starts.
Most platforms add metered usage on top of a base fee. PocketBase Cloud charges one flat price for the whole project.
| Topic | PocketBase Cloud | Usage-billed platforms |
|---|---|---|
| How you pay | One flat monthly price | A base fee plus metered compute, bandwidth or requests |
| When traffic spikes | Your bill stays the same | Your bill rises with usage |
| Database, auth, files, website and API | In one project | Often separate products, each billed on its own |
| Leaving | Download a standard PocketBase backup any time | Depends on the platform |