System Requirements

Minimum and suggested system requirements for self-hosting Password Pusher Pro (Starter, Advanced, and Enterprise).

This article applies to: Pro Self-Hosted (Starter, Advanced, and Enterprise)

Password Pusher Pro Self-Hosted — System Requirements

This document outlines the minimum and suggested system requirements for self-hosting Password Pusher Pro.

Starter & Advanced share the same requirements (single container with bundled SQLite3).
Enterprise has higher requirements because it runs the application plus PostgreSQL (two containers on the same host or split across hosts).


Starter & Advanced

Single container: application with bundled SQLite3.

  Minimum Suggested
CPU 1 vCPU (2.0 GHz or higher) 2 vCPUs (2.0 GHz or higher)
Memory 2 GB RAM 2 GB RAM
Storage 10 GB 20 GB (SSD recommended)
Network Internet for image pulls Stable, low-latency connection
OS Docker 24.0+ and Docker Compose 2.20+ Same

Storage breakdown: Application ~2 GB; remainder for file uploads and logs. When using local storage, estimate based on the total size of files from active pushes and requests at any given time. When a push or request expires or is closed, its attached files are deleted immediately. Storage needs therefore depend on how many active pushes and requests you have at once.


Enterprise

Two containers: application + PostgreSQL. Requirements below are for the combined system when both run on one host.

  Minimum Suggested
CPU 2 vCPUs (2.0 GHz or higher) 4 vCPUs (2.0 GHz or higher)
Memory 4 GB RAM 4 GB RAM
Storage 20 GB (SSD recommended) 50 GB (SSD strongly recommended)
Network Internet for image pulls Stable, low-latency connection
OS Docker 24.0+ and Docker Compose 2.20+ Same

Storage breakdown: Application ~2 GB; PostgreSQL data 10–30 GB depending on usage; remainder for file uploads, logs, and backups. When using local storage for file uploads, estimate based on the total size of files from active pushes and requests at any given time. When a push or request expires or is closed, its attached files are deleted immediately. Storage needs therefore depend on how many active pushes and requests you have at once.


Additional considerations

  • Background workers: The application runs background job workers that perform various tasks (e.g. cleanup, notifications, scheduled jobs). The CPU and memory requirements above include capacity for these workers.
  • Scaling: Memory and storage scale with usage, number of Pushes/Requests, and retention. For production with significant traffic, consider resources above the suggested values.
  • File uploads (local storage): Plan storage for the total size of files attached to active pushes and requests at any given time. Once a push or request expires or is closed, attached files are deleted immediately.
  • Enterprise: The application and PostgreSQL can run on one host (as in the default compose) or you can run PostgreSQL on a dedicated host and point the app at it.

Environments:

  • VPS: All editions run well on providers such as DigitalOcean, AWS, Azure, etc.
  • Cloud: Any platform that supports Docker and Docker Compose.
  • On-premise: Supported with appropriate network and security setup.

Docker requirements

All editions require:

  • Docker: 24.0 or higher
  • Docker Compose: 2.20 or higher

Check versions:

docker --version
docker compose version

Support

For questions about system requirements or deployment, see the rest of the docs at docs.pwpush.com or contact support.