Deploy from GitHub
Every push goes live
Connect a repository to a PocketBase instance, a frontend or a backend. Push to your branch and it builds and deploys. Monorepos included.
NewDeploy on push · Continuous backup · Self-driving (beta)
Managed PocketBase hosting
Launch your whole app for one flat price.
Database, sign-in, file storage, frontend and server on one platform. Next month’s bill is the same, whatever your traffic does.
$10/mofor your first app
$25/mofor as many as you want
Free plan available — a card keeps bots out, and is never charged.
POCKETBASE
Your whole backend, without writing one.
One open-source program that is already your database, REST API, auth, file storage and job scheduler.
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',
});The platform
Everything your app needs to go live, in one place.
Your database, your site and your server run side by side, with deploys, domains, backups and monitoring already handled. The plan price does not move as you add to it.
What you get
- PocketBaseStore data, sign users in, upload files and push live updates without writing a backend.
- FrontendYour site live on HTTPS in under a minute, included on every plan.
- BackendRun your Node.js, Next.js, Deno or Bun server next to your data, on Pro.
- Deploy your wayShip from GitHub, one CLI command, or a template — whichever fits how you work.
- Domains + SSLYour app on your own domain, with the certificate issued and renewed for you.
- MonitoringSee what is slow or failing before your users tell you.
- Continuous backupUndo a bad migration or a deleted table — restore to any point in the last 7 days.
- Self-drivingBetaWhen production breaks, get the fix as a pull request to review.
One platform, one CLI, one bill.
Runs itself
Push to deploy. Undo any mistake. Get fixes as pull requests.
Shipping, backups and late-night debugging are the parts of running an app that usually need a person on call. Here the platform does them.
Continuous backup
Roll back to any point in the last 7 days
Turn it on and every change to your database is copied off-site as it happens, so there is no nightly gap to lose. Pick a moment and restore it.
Powered by LitestreamSelf-driving
When something breaks, a fix arrives for review
It spots crashes, error spikes and failing requests, explains the cause with evidence, and opens a pull request. You review and merge. It never merges or deploys 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, issued automatically.
No lock-in. Download a stock PocketBase directory any time and restore it anywhere.
Roll back any change. Turn on continuous backup on a paid plan and restore to any point in the last 7 days.
FRONTEND
Ship it, then point your domain at it.
Two commands, run from the directory your site lives in.
Deploy
One command from your project directory. The build config is inferred on the first run.
pbc frontend deploy
Your own domain
Add the domain, set the record the CLI names, and the certificate is issued for you.
pbc frontend domain add app.example.com --name web
Included, not configured
Every site is behind Cloudflare from the first deploy.
Fast for visitors everywhere
Served from Cloudflare’s global edge, with HTTP/3 and compression.
Stays up under attack
DDoS protection on every site.
Secure from the first deploy
HTTPS certificates issued and renewed for you.
Traffic spikes cost nothing
Bandwidth is not metered.
A live URL right away
Every deploy gets its own pocketbasecloud.com HTTPS address.
Deep links just work
Routes resolve to your app, for React Router and Vue Router alike.
BACKEND
Need npm packages or Next.js? Run your server here too.
Push the repo as it is. It runs in its own container and stays up between requests.
Runs on
Node.js
APIs, workers, and web services
Next.js
Full-stack and server-rendered apps
Deno
TypeScript-first backend services
Bun
Fast JavaScript and TypeScript apps
pbc backend deploy
Backends need Pro. Starter runs PocketBase and frontends.
Common questions.
What exactly does PocketBase Cloud host?
Everything a small or medium app is made of. Your data layer — a PocketBase instance, which is your database, its auto-generated REST API, authentication, file storage, realtime and scheduled jobs. Your frontend — any static or single-page build, served from its own HTTPS address behind Cloudflare. And, on Pro, your backend — a Node.js, Next.js, Deno or Bun project running in its own always-on container. One platform, one CLI, one invoice, instead of a database host, a frontend host and somewhere to put the server.
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.
Is there a free plan?
Yes. The Free plan runs 1 PocketBase instance with frontend hosting at no cost. We ask for a card at sign-up to keep bots out; it is never charged.
What happens to my bill if my app has a good month?
Nothing. There is no bandwidth meter, no per-request billing, no build minutes and no per-seat charge — the plan price is the price. That is the main reason to be here rather than on a stack of usage-billed services: on those, a post that does well is a bill you did not choose, and for a small or medium app the ceiling matters more than the floor.
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.
Do I have to use PocketBase to use the platform?
No. Plenty of people deploy only frontends here, and on Pro you can deploy a backend that talks to a database somewhere else entirely. PocketBase is what we recommend because it removes the most work — you get a database, an API over it, auth and file storage without writing any of them — but nothing forces you to build on it.
When do I need a backend deployment as well?
When the code outgrows a hook. PocketBase runs your JavaScript inside the instance, which is the right home for a few custom endpoints, validation before a save, or a nightly job — no dependencies, nothing extra to deploy. Reach for a backend when you need npm packages (Stripe, an AWS SDK, PDF generation, an LLM client), when a framework has to server-render (Next.js, Nuxt), when the logic is big enough to want modules and tests, or when work has to keep running between requests. Backend deployments are on the Pro plan.
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, and the same CLI that deploys your PocketBase instance also deploys your frontend and your backend. 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, your frontends and your backends alike. Everything 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 deployment, 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.
Launch today. Know next month’s bill.
No lock-in: your data is a stock PocketBase directory you can download as a zip and restore anywhere, any time. How that works.