Self-hosting PocketBase the easy way
Yulei ChenPocketBase is an open-source backend in a single file. It gives you a realtime database, user authentication, file storage, and a built-in admin dashboard - all powered by SQLite. It's perfect for SaaS projects, mobile apps, or any prototype that needs a backend fast.
Sliplane is a managed container platform that makes self-hosting painless. With one-click deployment, you can get PocketBase up and running in minutes - no server setup, no reverse proxy config, no infrastructure to maintain.
Prerequisites
Before deploying, ensure you have a Sliplane account (free trial available).
Quick start
Sliplane provides one-click deployment with presets.
Deploy PocketBase >- Click the deploy button above
- Select a project
- Select a server (If you just signed up you get a 48-hour free trial server)
- Click Deploy!
About the preset
The one-click deploy above uses Sliplane's PocketBase preset. Here's what it includes:
- The community-maintained PocketBase Docker image (
ghcr.io/coollabsio/pocketbase) - Specific version tag (
0.36.9) for stability - Persistent storage for
/app/pb_data(your database, uploaded files, and settings) - Persistent storage for
/app/pb_hooks(custom JavaScript hooks) - Listens on port 8080 by default
Next steps
Once PocketBase is running on Sliplane, open the domain Sliplane provided (e.g. pocketbase-xxxx.sliplane.app).
Creating your admin account
PocketBase has no default credentials. On the first visit, go to /_/ (e.g. pocketbase-xxxx.sliplane.app/_/) to open the admin setup wizard. You'll create your admin email and password there.
Admin dashboard
The admin dashboard at /_/ is where you manage everything: collections (your database tables), API rules, auth providers, file storage settings, and more. It's a full GUI - no SQL needed to get started.
Data storage
PocketBase stores everything in SQLite under /app/pb_data. This includes your database, uploaded files, and internal settings. The preset mounts this path to a persistent volume, so your data survives container restarts and redeployments.
Custom hooks
If you need server-side logic, PocketBase supports JavaScript hooks. Place your .pb.js files in /app/pb_hooks and they'll be loaded automatically on startup. The preset mounts this path to a separate persistent volume.
Logging
PocketBase logs to STDOUT by default, which works well with Sliplane's built-in log viewer. For general Docker log tips, check out our post on how to use Docker logs.
Troubleshooting
If the admin UI doesn't load, make sure you're visiting the /_/ path (with the trailing slash). If the service won't start, check the logs in the Sliplane dashboard for error messages. Common issues include volume permission errors, which are usually resolved by redeploying.
Cost comparison
You can also self-host PocketBase with other cloud providers. Here is a pricing comparison for the most common ones:
| Provider | vCPU | RAM | Disk | Monthly Cost | Note |
|---|---|---|---|---|---|
| Sliplane | 2 | 2 GB | 40 GB | €9 (~$10.65) | Flat rate, 1 TB bandwidth, SSL included |
| Fly.io | 2 | 2 GB | 40 GB | ~$18 | Disk and bandwidth billed separately |
| Render | 1 | 2 GB | 40 GB | ~$35 | 100 GB bandwidth, Disk billed separately |
| Railway | 2 | 2 GB | 40 GB | ~$67 + $20 plan | Pro plan floor, usage-based, bandwidth billed separately |
Click here to see how these numbers were calculated.
(Assuming an always-on instance running 730 hrs/month)
- Sliplane: flat €9/month for the Base server. Unlimited services on the same server, 1 TB egress and SSL included.
- Fly.io:
shared-cpu-2x2 GB = $11.83/mo + 40 GB volume × $0.15/GB = $6 -> ~$17.83/mo. Egress billed separately ($0.02/GB in EU). - Render: closest match is Standard ($25, 1 vCPU / 2 GB) plus 40 GB disk × $0.25/GB = $10 -> ~$35/mo. Stepping up to Pro (2 vCPU / 4 GB) costs $85/mo + disk.
- Railway (Pro plan): CPU 2 × $0.00000772/s × 2,628,000 s = $40.57; RAM 2 × $0.00000386/s × 2,628,000 s = $20.29; volume 40 × $0.00000006/s × 2,628,000 s = $6.31 -> ~$67/mo compute, plus the $20/mo Pro plan floor and $0.05/GB egress.
Bandwidth costs can add up fast on usage-based providers. Use our bandwidth cost comparison tool to see what your egress would cost on each platform.
FAQ
What can I build with PocketBase?
PocketBase is great for any project that needs a backend quickly: SaaS apps, mobile apps, internal tools, or prototypes. It gives you a REST and realtime API, user auth (email/password, OAuth2), file uploads, and an admin UI out of the box. Many developers use it as a Directus or Firebase alternative.
How do I configure OAuth2 or email auth?
Go to the admin dashboard at /_/, navigate to Settings, and configure your auth providers there. PocketBase supports Google, GitHub, Facebook, and many other OAuth2 providers. You can also enable email/password auth and customize verification emails directly from the UI.
How do I update PocketBase?
Change the image tag in your Sliplane service settings to the new version and redeploy. Your data in /app/pb_data is stored on a persistent volume, so it's safe across redeployments. Always check the PocketBase changelog before upgrading to review any breaking changes.
Are there alternatives to PocketBase?
Yes. Popular options include Directus (a headless CMS with a powerful data studio), Strapi (another headless CMS focused on content APIs), NocoDB (an Airtable-like spreadsheet UI on top of databases), and Supabase (a Firebase alternative built on Postgres).
Can PocketBase handle production traffic?
Yes. PocketBase is surprisingly performant thanks to SQLite. For most small-to-medium apps, a single instance on a €9/month Sliplane server handles thousands of concurrent connections without issues. If you outgrow a single file, you can always migrate your data to an external database later.
