Deploy from GitHub
Every push goes live
Connect a repo to your instance. Push and it builds and deploys. Monorepos included.
NewDeploy on push · Continuous backup · Self-driving (beta)
Managed PocketBase hosting
PocketBase in production, without the server work.
Your own PocketBase instance in seconds, with deploys, backups, domains and monitoring handled.
- Live in secondsPick a region, name it, done
- Deploy on pushFrom GitHub, CLI or a template
- Continuous backupAny point in 7 days, Starter & Pro
- Domains + SSLCertificates renewed for you
POCKETBASE
Your whole backend, without writing one.
Database, REST API, auth, files and jobs in one open-source program.
client.js
// 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',
});Runs itself
Push to deploy. Undo any mistake. Get fixes as pull requests.
Shipping, backups and debugging, handled by the platform.
Continuous backup
Roll back to any point in the last 7 days
Every database change is copied off-site as it happens. Pick a moment and restore.
Powered by LitestreamSelf-driving
When something breaks, a fix arrives for review
It spots crashes and errors, explains the cause and opens a pull request. It never merges by itself.
Runs on our model key, or bring your own
Merge the fix, and the push deploys it.
30sto go live
99.99%uptime
800+developers
300+instances
12locations
Running in production todayLive status page
SSL and DDoS protection on every instance.
No lock-in. Download a standard PocketBase backup any time.
Roll back any change. Restore your database to any point in 7 days, on paid plans.
Common questions.
What exactly does PocketBase Cloud host?
PocketBase instances, managed for you. Each one is your database, its auto-generated REST API, authentication, file storage, realtime and scheduled jobs, running on its own HTTPS address. We handle the server, SSL, updates, backups and monitoring; you deploy from the portal, the CLI or a GitHub push.
What is PocketBase, in one paragraph?
It is a single open-source program that is already most of a backend. You define your tables in a visual editor and it immediately gives you a REST API over them with access rules, plus email and social sign-in, file uploads with thumbnails, realtime subscriptions, and a place to run your own JavaScript for custom endpoints and scheduled jobs. It is built and maintained by a separate, unrelated open source project; we are an independent platform that runs it for you, with no server setup.
Can I get my data out?
Any time, and you do not need to ask us. In your instance's PocketBase admin, Settings → Backups gives you a zip of the whole pb_data directory: schema, records and uploaded files. Restore it onto any PocketBase and your app is back. It is the standard PocketBase backup, not an export format of ours. If you would rather stay in the terminal, "pbc admin settings backup download" fetches the same file.
How does this compare to self-hosting?
Self-hosting means configuring servers, applying updates, setting up SSL, arranging backups and watching uptime yourself. Here that is handled. Moving an existing instance is a backup restore: create a backup under Settings → Backups in your current admin, then upload and restore it in your PocketBase Cloud instance. Collections, records, users and uploaded files arrive as they were, with nothing to convert.
What if I break my database?
On Starter and Pro, turn on continuous backup and restore from it. Once enabled, each change to the database is copied off-site as it happens, and you can put the instance back to any point in the last 7 days from its Continuous Backup page in the portal. It covers the database, not uploaded files. For those, keep taking the standard PocketBase backup from Settings → Backups. On Free there is no continuous backup, only the standard one.
Can I use a custom domain?
Yes, on the Starter and Pro plans, for your PocketBase instance. Every instance also gets a unique pocketbasecloud.com subdomain by default, so there is a working HTTPS address before any domain is involved. Point a CNAME at your instance, or an A record to the server IP the portal shows if your DNS is on Cloudflare, and the certificate is issued and renewed for you. If you keep Cloudflare’s proxy on, we verify the domain with a TXT record.
Who runs PocketBase Cloud?
A small team rather than a large company — the About page names the founder, explains how the business makes money, and is honest about what that trade-off costs you: direct answers on Discord, but no 24/7 on-call rota. We would rather you know that before signing up than find out during an incident.
Are you affiliated with PocketBase or run by its authors?
No. PocketBase Cloud is an independent, unofficial hosting service with no relationship to the PocketBase open source project. We are not affiliated with, associated with, authorised by, endorsed by or sponsored by PocketBase or its authors, and we do not speak for them. "PocketBase" and related marks belong to their respective owners; we use the name only to describe the open source software we host for you, which is distributed under the MIT licence. The official project is at pocketbase.io. Questions about this hosting platform come to us — please do not send them to the PocketBase maintainers, and bugs in PocketBase itself are theirs to fix, not ours.
Your PocketBase, live in seconds.
No lock-in: download your data any time. How that works.