HostCritiq
Search ⌘K
Menu

Application hosting

Hosting PocketBase

A compact backend for applications that need a database, authentication, file uploads and realtime subscriptions. PocketBase packages these features into one executable, with SQLite as its embedded database.

See matching plans Size a server
Min vCPU
Depends on workload
Min memory
Depends on workload
Min storage
Depends on workload

Must have

Hard prerequisites

  • An executable matching the operating system and CPU architecture.
  • Persistent writable storage for the pb_data directory.

Recommended

Documented guidance

No further general recommendations are published for this version.

Capacity depends on your workload

The documentation does not establish universal CPU, RAM or disk minimums. Size the host around records, uploads and concurrent connections. The project cautions against production-critical use before 1.0 unless you can manage breaking changes.

We only compare what providers publish. A RAM figure alone can't confirm compatibility or production capacity.

Deploy with

Supported paths

  • Standalone executable behind a reverse proxy
  • Custom container with a persistent data volume
  • Embedded in a Go application

The host must provide

Runtime

SQLite
Embedded by PocketBase; no separate database service required

Storage

Persistent data

Persist pb_data, including the database and local uploads. Keep migrations in version control. Back up application data and uploaded files; external object-store files need their own backup strategy.

Step by step

Plan a PocketBase deployment

  1. Choose the binary

    Use the release matching your host architecture and read upgrade notes before changing versions.

    Official instructions

  2. Prepare persistent storage

    Keep pb_data outside disposable container layers and test restoring a backup.

    Official instructions

  3. Configure public access

    Place the service behind HTTPS, configure trusted proxy headers and enable authentication rate limits.

    Official instructions

Security

Before you go public

  • Restrict superuser access and consider MFA.
  • Use production SMTP and protect settings and backup credentials.

Cost

Beyond the server price

  • Budget for persistent storage, backups and email delivery as well as the host.

Matching plans

Plans with published evidence

Vultr

Vultr Optimized Cloud Compute (CPU Optimized) · 16 vCPU / 32 GB

16vCPU
32 GBRAM
300 GBStorage
8 TBTransfer
  • Dedicated vCPU (AMD EPYC)
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • An executable matching the operating system and CPU architecture.This prerequisite has no comparable published plan field.
  • Persistent writable storage for the pb_data directory.This prerequisite has no comparable published plan field.
Vultr

Vultr Optimized Cloud Compute (CPU Optimized) · 2 vCPU / 4 GB

2vCPU
4 GBRAM
50 GBStorage
5 TBTransfer
  • Dedicated vCPU (AMD EPYC)
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • An executable matching the operating system and CPU architecture.This prerequisite has no comparable published plan field.
  • Persistent writable storage for the pb_data directory.This prerequisite has no comparable published plan field.
Vultr

Vultr Optimized Cloud Compute (CPU Optimized) · 4 vCPU / 8 GB

4vCPU
8 GBRAM
75 GBStorage
6 TBTransfer
  • Dedicated vCPU (AMD EPYC)
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • An executable matching the operating system and CPU architecture.This prerequisite has no comparable published plan field.
  • Persistent writable storage for the pb_data directory.This prerequisite has no comparable published plan field.
Vultr

Vultr Optimized Cloud Compute (CPU Optimized) · 8 vCPU / 16 GB

8vCPU
16 GBRAM
150 GBStorage
7 TBTransfer
  • Dedicated vCPU (AMD EPYC)
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • An executable matching the operating system and CPU architecture.This prerequisite has no comparable published plan field.
  • Persistent writable storage for the pb_data directory.This prerequisite has no comparable published plan field.
Vultr

Vultr Optimized Cloud Compute (General Purpose) · 1 vCPU / 4 GB

1vCPU
4 GBRAM
30 GBStorage
4 TBTransfer
  • Dedicated vCPU (AMD EPYC)
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • An executable matching the operating system and CPU architecture.This prerequisite has no comparable published plan field.
  • Persistent writable storage for the pb_data directory.This prerequisite has no comparable published plan field.
Vultr

Vultr Optimized Cloud Compute (General Purpose) · 16 vCPU / 64 GB

16vCPU
64 GBRAM
320 GBStorage
8 TBTransfer
  • Dedicated vCPU (AMD EPYC)
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • An executable matching the operating system and CPU architecture.This prerequisite has no comparable published plan field.
  • Persistent writable storage for the pb_data directory.This prerequisite has no comparable published plan field.
Vultr

Vultr Optimized Cloud Compute (General Purpose) · 2 vCPU / 8 GB

2vCPU
8 GBRAM
50 GBStorage
5 TBTransfer
  • Dedicated vCPU (AMD EPYC)
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • An executable matching the operating system and CPU architecture.This prerequisite has no comparable published plan field.
  • Persistent writable storage for the pb_data directory.This prerequisite has no comparable published plan field.
Vultr

Vultr Optimized Cloud Compute (General Purpose) · 4 vCPU / 16 GB

4vCPU
16 GBRAM
80 GBStorage
6 TBTransfer
  • Dedicated vCPU (AMD EPYC)
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • An executable matching the operating system and CPU architecture.This prerequisite has no comparable published plan field.
  • Persistent writable storage for the pb_data directory.This prerequisite has no comparable published plan field.
Vultr

Vultr Optimized Cloud Compute (General Purpose) · 8 vCPU / 32 GB

8vCPU
32 GBRAM
160 GBStorage
7 TBTransfer
  • Dedicated vCPU (AMD EPYC)
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

  • An executable matching the operating system and CPU architecture.This prerequisite has no comparable published plan field.
  • Persistent writable storage for the pb_data directory.This prerequisite has no comparable published plan field.

Want the full monthly bill? Use the hosting cost calculator. It keeps unknown charges visible.