Skip to main content

Fully Managed PocketBase
as a Service

Deploy PocketBase as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

PocketBase is an open-source Go backend with embedded SQLite, realtime subscriptions, authentication, and file storage — combining the convenience of Firebase or Supabase with the control and predictable cost of self-hosted infrastructure.

Free 7-day trial  99.9% Uptime SLA  No credit card  Cancel anytime

Free 7-day trial  99.9% Uptime SLA
No credit card  Cancel anytime

PocketBase

PocketBase

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
PocketBase Preview Image

ABOUT THE SOFTWARE

What is PocketBase

PocketBase is an open-source backend in a single ~12 MB binary. Written in Go, it bundles an embedded SQLite database, realtime subscriptions, authentication, file storage, and an admin dashboard — the complete shape of Firebase or Supabase, distributed as one file you can run anywhere.

The project is MIT-licensed and maintained by Gani Georgiev as an open-source project funded through GitHub Sponsors and Patreon. Roughly 58,000 GitHub stars and 3,400 forks reflect adoption that's heavy in indie SaaS, agency client work, mobile app backends, and internal tools.

The project's own documentation states PocketBase isn't recommended for production critical applications unless you're prepared to read the changelog and apply manual migration steps periodically — exactly the operational work managed hosting absorbs.

The architecture is deliberately small. PocketBase runs as a single binary plus a pb_data directory containing the SQLite database in WAL mode, uploaded files, and configuration. There is no separate database server, no Redis dependency, no message broker. Vertical scaling is the design choice; the maintainer benchmarks 10,000+ persistent realtime connections on a low-cost 2 vCPU VPS.

The trade-off is that PocketBase scales vertically only — the embedded SQLite is single-writer. For most indie SaaS, mobile backends, and agency-built client apps, that ceiling is well above what they'll ever hit. For high-write-concurrency or multi-region-active workloads, PocketBase isn't the right tool, and we'll tell you so before you sign up.

FEATURES

What PocketBase does

PocketBase is the backend in one file. Database, auth, realtime, file storage, admin UI, REST API, and JavaScript hooks — all bundled and all driven from a single binary plus a data directory. Eight capabilities cover the surface most teams use.

Embedded SQLite in WAL mode

A typed schema with relations, indexes, and rules. WAL mode gives reader concurrency; the database file is portable across architectures and OSes.

Authentication built in

Email/password, magic links, OTP, MFA for superusers. OAuth2 with Google, GitHub, Apple, Microsoft, Discord, GitLab, Bitbucket, and generic OIDC.

Admin dashboard at /_/

A real management UI — collection editor, record browser, log viewer, settings, API rules, OAuth provider config. Not a placeholder dev tool you replace later.

Official JS and Dart SDKs

Single-package SDKs for browser, Node, and Flutter clients. Type-safe, auto-refreshing tokens, realtime helpers. Community SDKs for Swift, Kotlin, Python, Go.

Realtime over Server-Sent Events

Clients open a long-lived GET /api/realtime stream and subscribe by collection. SSE plays nicer with proxies and CDNs than WebSockets, but is one-directional.

File storage with S3 adapters

Local disk by default, with first-class S3-compatible adapters for Cloudflare R2, Backblaze B2, AWS S3, Wasabi, and any other S3 API target.

JavaScript hooks via goja

Drop .pb.js files into pb_hooks/ to add custom routes, validate records, run scheduled jobs, or augment OAuth flows. No Node, no npm install step.

Go framework mode

PocketBase is also importable as a Go package. Custom binaries can register routes, models, and hooks in native Go — the path for deeper extensibility beyond the JS VM.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app you deploy includes the full managed service — security, backups, updates, and support from day one.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers on chat. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed PocketBase

Two compounding pressures push teams toward managed PocketBase in 2026. Firebase forced Cloud Storage onto the paid Blaze plan, ending the free hobby tier. Appwrite Cloud Pro raised its base price by two thirds. Meanwhile PocketBase itself ships breaking changes every few weeks — substantial operational work for anyone running it solo.

Running PocketBase in production isn't "drop the binary on a VPS and you're done." The single binary handles application logic; everything around it is operational work that doesn't show up in a Getting Started tutorial. Five things bite people who self-host:

The first is the SQLite WAL file. A naive rsync pb_data for backups drops the .db-wal file. The maintainer says it directly in GitHub Discussion #1265: without it, you can end up with missing writes or a corrupted database. The supported path is either PocketBase's own /api/backups/create endpoint (which queues writes during the zip) or continuous WAL replication with Litestream-style tooling. Either takes setup; neither is the default.

The second is the binary swap. PocketBase ships releases approximately every five days, and the v0.x cadence carries real breaking changes — v0.23 reworked the admin setup model around a new _superusers collection; v0.36 changed the collection API; v0.38 added a system migration that resaves every collection. Reading the changelog, testing in staging, and rolling forward at a controlled time is a recurring tax. We run that staging cycle for every customer instance and hold the upgrade if a release would require code changes in your hooks.

The third is email. PocketBase's default SMTP uses the local sendmail binary, which the official docs flag as a deliverability dead end in production. Password resets and magic links don't arrive. We require a real SMTP provider on every paid instance and wire it on day one.

The fourth is the file-descriptor and memory ceiling. The PocketBase docs warn that a busy realtime workload hits "too many open files" without raised system limits. We tune ulimit, GOMEMLIMIT, and the underlying kernel parameters before you ever notice.

The fifth is the export. The whole point of self-hostable software is portability. We give you the full pb_data directory as a downloadable zip at any time, no cancellation form required. If you ever want to move to a VPS, your data comes with the binary.

REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run PocketBase on DANIAN

These are representative team types we set up most often. Each starts with the same flat €9 plan.

10-PERSON DIGITAL AGENCY

Per-client backend after Firebase's storage paywall hit

Eleven client backends, deployed one per €9 instance in Germany and Canada. Each client gets a subdomain and OAuth against their own Google Workspace. The agency wired a single Make.com automation to provision a new PocketBase from their internal admin tool. No more shared Firebase project, no more attributing usage spikes back to specific clients.

2-FOUNDER INDIE SAAS

Migrated from Supabase to cut the $25/month compute floor

A scheduling tool with 2,400 paying users. Moved off Supabase Pro after the Postgres compute charges crossed $80/month. PocketBase runs in Singapore with WAL replication to Japan. JavaScript hooks port their Supabase Edge Functions; Stripe webhooks land via a custom /api/stripe route. €9 flat from one to fifty thousand users.

SOLO MOBILE DEVELOPER

Flutter app backend for a meditation timer

4,000 monthly active users, Apple Sign In and Google OAuth, audio file delivery through the S3 adapter pointed at Cloudflare R2. Deployed in Brazil for Brazilian primary market with €9 instance plus R2 egress (zero). Push notifications via OneSignal, triggered from a PocketBase JS hook on record-create. The whole backend cost is under €15 a month including storage.

COMPARISON

Four ways to run PocketBase

Most teams arrive at PocketBase from one of three places — Firebase, Supabase, or Appwrite. The cost question isn't "PocketBase vs Firebase" abstractly; it's what each of the four realistic paths costs at the scale you're running. The math runs the argument; we don't need to.

 PATH1 APP5 APPS 10 APPSWHAT YOU DO
Firebase Blaze
$25–60$125–300$250–600Pay-as-you-go after free tier. Cloud Storage requires Blaze since Feb 2026. Reads, writes, egress, and storage each billed separately.
Self-host 
on a $24/mo production-class VPS
~€100–280~€140–340~€200–440VPS + object-storage backup + monitoring + 1–2 hours/month of patching, WAL replication, SMTP setup, certificate renewal, on-call.
Higher-end home server
~€210–667~€220–680~€240–700Synology DS923+ or HP ProLiant ML30 amortised over 36 months, plus electricity, business internet with static IP, off-site backup target, and ops time.
DANIAN Managed PocketBase€9€45€90You point a domain at the instance we deploy. We handle backups, upgrades, SMTP, SSL, monitoring, scaling, and chat support. Customer ops time: 0 hours.

Cost rows reflect 2026 published pricing for Firebase Blaze (Spark plan no longer covers Cloud Storage as of February 3, 2026), 2 vCPU / 4 GB production-class VPS reference setup, and higher-end home-server hardware amortised over 36 months. Ops time priced at €60–120/hour.

BY INDUSTRY

PocketBase for specific industries

PocketBase's shape — embedded SQLite, single binary, JS hooks — fits some industries cleanly and others not at all. Four are worth calling out explicitly because the decision pattern is genuinely different.

The dominant use case. The official Dart SDK and JavaScript SDK cover Flutter, React Native, native iOS via REST, Android via REST, and progressive web apps from one backend. SSE-based realtime works through standard mobile networking stacks where WebSockets are sometimes blocked.

Operational standard here is Apple's App Transport Security and certificate pinning. We provision long-lived Let's Encrypt certificates with explicit cipher-suite selection so iOS clients can pin the leaf certificate without renewal surprises. Push notifications via a JS hook on record.create calling OneSignal or APNs directly. A typical Flutter app with 5,000 monthly active users and OAuth runs comfortably on the base €9 instance with no upgrade needed.
The second-largest cohort. PocketBase replaces Firebase + Cloud Functions or Supabase Pro for one-founder businesses and 2–3-person teams running a paying SaaS, where the per-user economics of managed BaaS have crossed into "this is more than my server bill should be."

The operational concern is the standard data-protection stack: encryption at rest, backup integrity, and a defensible export path. We encrypt the PocketBase data volume at rest, encrypt off-site WAL backups in transit and at rest, and keep the full pb_data directory downloadable from the dashboard. A typical indie SaaS will run Stripe webhook handling through a JavaScript hook at /api/stripe-webhook and gate subscription tier in API rules. Users on the base instance: comfortable through 10,000+ paying customers.
Common pattern: an agency builds a custom internal tool, client portal, or content management system for a client and needs a backend they can hand off cleanly. PocketBase fits because the entire backend is one binary and one pb_data directory — the agency can deliver the client a downloadable zip if the relationship ever ends.

The operational standard is contractual: client data portability and a defined exit path. We configure each client instance under its own custom domain, with its own OAuth provider against the client's identity provider, and the pb_data export is one click in the dashboard. An agency running 12 client instances pays €108/month total — versus per-seat SaaS bills in the low thousands at the same client count.
The quiet fourth use case. Companies build internal CRUD applications — inventory, ticketing, content publishing, ops dashboards — on PocketBase instead of standing up Postgres, building an admin UI, writing auth, and wiring file uploads. The bundled admin dashboard at /_/ covers the bulk of the back-office workflow without any frontend.

Standard concern is access control and audit logging. We restrict the admin URL by IP allowlist on request, configure OAuth against your identity provider for SSO, and set backup retention to match your audit window — typically 90 days for compliance-adjacent workloads. A typical internal tool with 30 staff users and 50,000 records runs at zero perceptible load on the base instance.

FAQ

Frequently asked questions

Everything teams ask before signing up — answered straight, without sales speak.

Three groups: technical setup, migration, and how DANIAN works as a service.

01

Technical and configuration

PocketBase scales vertically only — the embedded SQLite is single-writer. The maintainer's published benchmark is 10,000+ persistent realtime connections on a low-cost 2 vCPU / 4 GB VPS. We've seen a 15,000-user client app cited in the project's own GitHub discussions running comfortably on a 2 GB / 2 vCPU production-class VPS. If you need horizontal scaling or high write concurrency, PocketBase isn't the right tool and we'll say so.
Not for writes. SQLite is single-writer and PocketBase's realtime event dispatch isn't designed to deduplicate across replicas. A read-only replica pattern via Litesync or similar is possible but app-level routing of reads versus writes is your responsibility. For most PocketBase workloads, vertical scaling on a single larger instance is cheaper and operationally simpler than chasing horizontal scale.
The PocketBase default uses the OS sendmail command, which the official docs explicitly call out as fine for development but a deliverability failure in production. We require a real SMTP provider on every paid instance and configure it on day one — Postmark, Mailgun, AWS SES, Brevo, or your own. Password resets, magic links, and OAuth verification emails actually arrive.
Email/password, magic links, OTP, MFA for superusers, plus OAuth2 with Google, GitHub, GitLab, Bitbucket, Discord, Apple, Microsoft, Facebook, Twitter, Spotify, Strava, Kakao, Gitea, Forgejo, and generic OpenID Connect. We register the OAuth app on your behalf if you want, or you bring the client IDs and we wire them into the admin UI. SSO via OIDC works for internal-tool patterns.

02

Migration and onboarding

We can activate your app on your own custom domain/subdomain. Examples: mydomain.com, anyword.mydomain.com.
Or, on our randomized free subdomain. Example: 963.apps.danian.cloud
If you wish to use a custom domain/subdomain, select that option when ordering your app (or notify us later). We will send you the required DNS records and if needed, our tech team will modify them for you.
21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.

03

Billing, support, and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on Email/LiveChat. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 Live chat and email support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed PocketBase for 7 days

No card. Cancel from the dashboard.