Docs Platform Architecture

Architecture

PocketBase Cloud is built around a simple idea: every app needs a database, backend logic, and a frontend. We call these the three pillars.

The three pillars

PocketBase (Database + API)

Each PocketBase instance gives you:

  • SQLite database — fast, embedded, zero-config
  • REST API — auto-generated CRUD endpoints for every collection
  • Realtime subscriptions — live updates via SSE
  • Authentication — email/password, OAuth2, and more
  • File storage — upload and serve files
  • Admin panel — visual database management at /_/

PocketBase is the data layer of your app. Define your schema in the admin panel and your API is ready instantly.

Backend (Custom Logic)

For logic that goes beyond PocketBase’s built-in features:

  • Deno runtime
  • Custom API endpoints
  • Third-party integrations (Stripe, SendGrid, etc.)
  • TypeScript-first
  • Webhook handlers

Your backend runs as a managed process with its own URL and environment variables.

Frontend (Static Sites)

Deploy the user-facing part of your app:

  • Any framework that builds to static HTML/CSS/JS
  • Automatic HTTPS
  • Custom domain support
  • Instant redeployments

How it fits together

A typical full-stack app on PocketBase Cloud:

[Frontend]
    ├── HTTP ───────────────> [PocketBase]
    ├── HTTP ───────────────> [Backend]
    │
[Backend]
    ├── HTTP ───────────────> [PocketBase]
    │
[PocketBase]
    ├── Webhook / Event ────> [Backend]
  • The frontend calls PocketBase directly using the PocketBase SDK for data, auth, and realtime. Also can call backend for custom logic.
  • The backend handles complex business logic, webhooks, and third-party integrations
  • PocketBase serves as the central data layer that both frontend and backend connect to

Security

  • All traffic is encrypted with HTTPS
  • Environment variables are encrypted at rest
  • Each deployment runs in isolation
  • PocketBase admin credentials are unique per instance