Skip to content

PocketBase Cloud vs Self-Hosting on a VPS

PocketBase is one of the easiest backends to self-host: a single binary you can run on the smallest VPS. So the honest question isn’t can you run it on your own server — you can — it’s whether the work around it is worth your time. This page walks through what a production VPS setup involves, what it costs, and when managed PocketBase hosting is the better deal.

Prices below are as of September 2026 — check DigitalOcean, Hetzner, and PocketBase Cloud pricing for current numbers.

Summary

PocketBase on a VPS PocketBase Cloud
Server cost From ~$4–6/mo for an entry-level VPS $0 Free / $10 Starter / $25 Pro, flat
Setup Download binary, systemd service, domain, firewall pbc deploy or a click in the portal
HTTPS Built in (Let’s Encrypt) — or your own reverse proxy Automatic, including custom domains
OS patches & security Yours Handled
Backups Built-in snapshots — scheduling, off-site copy and restore tests are yours Continuous point-in-time backup (Starter & Pro)
Monitoring & logs Set up yourself Live logs and per-instance metrics built in
PocketBase upgrades ./pocketbase update, whenever you remember Pinned version, upgrade per instance when you choose
Several apps One process, port, and domain each — you wire it up Unlimited instances on Pro, one bill
Frontend & backend Separate setup Included — frontends on every plan, Node/Deno/Bun backends on Pro
Root access Yes No

Is PocketBase free?

Yes. PocketBase is open-source software under the MIT license — no license fee, no usage limits in the software itself. Running it costs whatever the machine costs. On a VPS, that’s the server bill plus your time. On PocketBase Cloud, the Free plan hosts one instance with 50 MB of storage and 500 API requests per hour for $0 — enough for a prototype or a small side project.

What self-hosting PocketBase on a VPS involves

Credit where it’s due — PocketBase makes the basics genuinely easy:

  1. Install: download the release for your server’s architecture and unzip it. No runtime, no dependencies.
  2. Run it as a service: a small systemd unit that runs pocketbase serve and restarts on failure.
  3. HTTPS: pocketbase serve yourdomain.com obtains a Let’s Encrypt certificate on its own, or you put Caddy or nginx in front.
  4. First superuser: open the installer link printed on first start, or run pocketbase superuser upsert.
  5. Backups: the dashboard’s Settings → Backups can take scheduled snapshots and upload them to S3-compatible storage.

An afternoon, if you’ve done Linux before. The work that doesn’t fit in the afternoon is everything after it:

  • Operating system upkeep — security updates, SSH hardening, a firewall, and noticing when the disk fills up.
  • Backups you’ve actually restored. A nightly snapshot loses up to a day of data; testing a restore is the step most setups skip.
  • Monitoring and alerts. Something has to tell you the process died at 3 AM, before your users do.
  • PocketBase upgrades. PocketBase is pre-1.0 and releases often, with occasional breaking changes — so upgrades mean reading the changelog and testing first, not just running ./pocketbase update.
  • More than one app. Each app is another process, port, domain, and backup schedule to keep straight.
  • The rest of the stack. Your frontend and any Node or Deno backend need their own hosting, builds, and certificates.

None of it is hard. It’s just never finished.

What managed PocketBase hosting does instead

On PocketBase Cloud, you create an instance from the portal or with pbc deploy, and the server work is done:

  • HTTPS and custom domains with certificates issued and renewed for you
  • Continuous backup on Starter and Pro: every database change streams off-site, restorable to any point in the last 7 days (uploaded files are backed up separately)
  • Live logs and usage and performance metrics for every instance
  • Version pinning: each instance runs the PocketBase release you choose, and upgrades happen when you decide
  • Hooks and migrations deploy from the CLI — see Deploying PocketBase
  • A lost superuser password is a reset, not a recovery project — see Upserting a Superuser Credential
  • Frontends and backends on the same bill — static sites on every plan, Node.js, Deno, Bun, Next.js, and Python backends on Pro

Cost: a VPS vs managed PocketBase

For one small app, a VPS is cheaper on paper: a few dollars a month against $10 for Starter. The difference is an hour or two of your time a year — if nothing goes wrong.

For several apps, the math changes. Pro is $25/month flat for your own dedicated compute (2 vCPU) with unlimited PocketBase instances, frontends, and backends. A single VPS can host several apps too, but each one adds its own service, domain, backups, and monitoring to maintain. For freelancers and agencies running client projects, that upkeep is usually the real cost.

When to choose which

Self-host on a VPS when:

  • You need root access, custom Go extensions, or a non-standard setup
  • Data must stay on hardware or a provider you already control
  • You enjoy running servers, or you already run them for other workloads
  • Budget is the deciding factor and your time is free

Choose PocketBase Cloud when:

  • You’d rather build the app than maintain the server under it
  • You run several PocketBase apps and want one flat bill
  • You want point-in-time backups and monitoring without assembling them
  • You also need to host the frontend or a backend next to PocketBase

The honest bottom line

  • One hobby app, and you like Linux: a VPS is cheap and PocketBase makes it easy — go for it.
  • Anything you’d be upset to lose, or more than a couple of apps: managed hosting costs less than the time you’d spend keeping a server healthy.

Next steps