Password Pusher is available to use at pwpush.com or can be self-hosted with one of the sources listed below.

Note: There is also a large number of 3rd party tools from mobile apps to CLI utilities to interface with Password Pusher (wherever it is hosted) through the bundled JSON API.

Installation Sources

Password Pusher is available from the following sources:

Password Pusher is also offered by various hosting providers such as PikaPods & Heroku. It can also be run in Google Cloud, Microsoft Azure or Amazon AWS.

See the full Installation documentation for details

Run Your Own Instance Now

The recommended way to run Password Pusher is using the provided docker-compose.yml file, which includes persistent database storage, health checks, and is production-ready out of the box.

Steps:

  1. Setup a DNS record to point to your server (e.g. pwpush.example.com)
  2. Clone this repository or download docker-compose.yml
  3. Uncomment and set TLS_DOMAIN: 'pwpush.example.com' in docker-compose.yml
  4. Run:
docker compose up -d

Browse to https://pwpush.example.com - your TLS certificate will be automatically provisioned via Let’s Encrypt.

What’s included:

  • Persistent SQLite database (stored in Docker volumes)
  • Automatic TLS certificate provisioning
  • Health checks
  • Production-ready configuration

Using Docker Run (Alternative)

For a quick test or ephemeral instance:

docker run -d \
  -p "80:80" \
  -p "443:443" \
  -e TLS_DOMAIN=pwpush.example.com \
  pglombardo/pwpush:stable

Note: This method doesn’t include persistent storage. For production use, prefer Docker Compose.

Continue on for the full installation instructions…

Updated: