Run all your side projects for $25 a month.
Launch as many experiments as you like on one server of your own. The eleventh app costs the same as the first: nothing extra.
The indie math
- 1 project
- $10/mo
- 10 projects
- $25 flat
- Shutting one down
- $0 lost
- Custom logic runs
- Never billed
Pro is one 2 vCPU server you fill as you like, not a quota. Sites and databases are light; servers you deploy use it up first.
How a weekend ships
From your laptop to a live URL in a weekend
01
Develop locally
pbc local initRun the same PocketBase on your laptop as in production, so nothing breaks on the way up.
02
Add logic in hooks
pb_hooks/*.pb.jsEndpoints, data triggers and scheduled jobs next to your data. They ship with the app and are never billed per run.
03
Deploy the bundle
pbc deployDatabase, site and server from one CLI. Redeploys remember the target, and GitHub Actions can ship it for you.
Why indies stay
Small enough to understand fully
One app, one log to read, one folder to back up, and access rules written as one-line filters.
Most apps never need a separate server
Hooks cover most MVPs. When yours outgrows them, Pro runs Node, Next, Deno, Bun or Python right beside it.
Your landing page is included
5 sites on Free and Starter, unlimited on Pro. No second host for the landing page.
Drop the misses for free
Delete a failed experiment in a click. The winners are already live, with nothing to migrate.
Honest fit check
Good fit
- Apps that read more than they write: SaaS dashboards, tools, content apps, mobile backends
- Solo devs who want the same setup locally and live, and one CLI for everything
- Portfolios where flat pricing beats per-project multiplication
Not the fit
- Apps with heavy simultaneous writes, or that need Postgres add-ons like PostGIS or pgvector — consider Supabase
- Apps that must run in many regions at once or scale to zero — consider Cloudflare or Vercel
Your PocketBase, live in seconds.
No lock-in: download your data any time. How that works.