Flat-price full-stack hosting.

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.

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.

Yes, frontends are a first-class part of the platform, not an add-on. Run "pbc frontend deploy" in your project directory and the build is uploaded and served over HTTPS on its own address, behind Cloudflare’s edge. Free and Starter include 5 frontends; Pro is unlimited. You can point your own domain at any of them on Starter and Pro, and the certificate is issued and renewed for you.

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.

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.

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.

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.

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, so there is no second toolchain for the rest of the app. If you already self-host, the migration is a backup restore — see the question further down.

On the Pro plan ($25/month flat), you get your own dedicated compute (2 vCPU) in a region you choose. Each instance runs in isolation with its own database, credentials, and URL. Because you're paying for the compute — not per instance — you can run effectively unlimited PocketBase instances, backends, and frontends on it. Additional dedicated computes are coming soon for teams that want extra isolation or scale.

Yes. The Free plan runs 1 PocketBase instance with frontend hosting at no cost. A Stripe subscription is required to collect payment information and prevent abuse — you won’t be charged.

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.

On Starter and Pro, restore it. Continuous backup is on by default for every paid instance: 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.

It only acts on a repository you connected and only after you turn it on. When the platform records a real problem, such as a crash loop, an error spike or failing requests, the agent reads the evidence, works on a copy of your repository in an isolated sandbox, and opens a pull request with the fix and its reasoning. It never merges, never deploys and never touches your running instance. You review the PR like any other. It is in beta and free on every plan, within daily and monthly run limits. Runs use our model key by default; to pay your own provider instead, add your own model key under Account → Self-driving. Keys are stored encrypted, sent only to the run sandbox and never shown back.

Yes. Connect a repository to a PocketBase instance, a frontend or a backend, choose the branch and, for a monorepo, the directory, and every push to that branch deploys. You can switch auto-deploy off and deploy a commit by hand instead. The CLI and GitHub Actions keep working alongside it.

Yes, the same way in reverse. Create a backup in your existing instance's admin under Settings → Backups, then upload and restore it in your PocketBase Cloud instance's admin. Collections, records, users and uploaded files arrive as they were; there is nothing to convert and no field mapping to redo.

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 and the certificate is issued and renewed for you; if your DNS is on Cloudflare you can leave the proxy on and we verify the domain with a TXT record instead.

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.

On one machine in one region you chose, in a rootless container under its own system user, with its own SQLite file. Pro picks from 12 regions at checkout; Starter can pick a shared-pool location. The complete list of third parties involved — OVHcloud, Contabo, Hetzner, Cloudflare, Stripe, Resend and Google Analytics (marketing site only) — is on the security page, along with what has and has not been certified. There is no SOC 2 report; if your procurement needs one, better to know now.

Yes, from the portal, without emailing anyone. Deleting your account cancels your Stripe subscription in the same step, so billing stops when the account does. Delete your instances first — the portal shows you exactly what is left and links to each one — and take a backup before you do, since deletion is not reversible.