PocketBase is attractive because it packages a lightweight backend, authentication, realtime features, file storage, and an embedded SQLite database into a compact deployment. That means it can run on much smaller VPS hardware than a multi-service backend stack.
The main operational concerns are durable storage, backup consistency, file growth, and keeping the single server easy to restore.
Key takeaways
- 1 GB is enough for many small PocketBase projects.
- 2 GB gives comfortable room for a reverse proxy, monitoring, and related services.
- SQLite and uploaded files make disk backups critical.
- A small VPS is often simpler than introducing a large container platform.
- Scale architecture only when real concurrency and storage demand require it.
How much VPS does PocketBase need?
Small applications can run comfortably on 1 GB because the deployment is compact. Two gigabytes gives useful operational headroom and room for monitoring, a reverse proxy, or a small side service.
CPU requirements are usually modest until traffic or application logic becomes significant.
SQLite and storage design
PocketBase uses SQLite, so the database lives on local storage rather than a separate database service. That simplicity makes disk durability and backups especially important.
Uploaded files can grow much faster than the database itself, so monitor storage capacity.
Deployment choices
A direct binary under systemd can be simpler than Docker for one small PocketBase application. Docker is still useful when it matches the team's deployment workflow.
Place a reverse proxy in front for HTTPS, hostnames, and access controls.
Backups and scaling
Back up the database and file storage together in a consistent way. Keep off-server copies so VPS loss does not become data loss.
If concurrency or storage outgrows a single-server architecture, evaluate whether PocketBase remains the right backend before simply scaling the VPS indefinitely.
Frequently asked questions
Is 1 GB enough for PocketBase?
Yes for many small applications.
Does PocketBase need PostgreSQL?
No. PocketBase uses SQLite as its embedded database.
Should PocketBase run in Docker?
It can, but a direct binary deployment is also simple and efficient.
What should I back up?
Back up both the PocketBase database and uploaded files, plus configuration needed to restore the application.