Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
Self-host Password Pusher
updated Nov 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Nov 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
A web app for sharing a password, text note, file, URL or QR code through a one-time link that expires after a set number of views or days. The recipient opens the link, and the content is deleted once the view or day limit is reached, so it does not sit in chat or email history. Push payloads and file metadata are encrypted at rest in the database with a master key you set, but uploaded file contents are not, and the app runs on one container with SQLite, with an optional audit log and an API for scripts.
Pick Password Pusher when you want to share a password, text note, file, URL or QR code through a link that expires after a set number of views or days, from a single container with no separate database. The recipient opens the link, the content is shown and later removed. The README lists encrypted storage, an optional passphrase, an audit log, MFA, a JSON API, an official CLI and 31 languages. It is Ruby on Rails under Apache-2.0. Our snippet is upstream's `docker-compose.yml` with the image pinned to `pglombardo/pwpush:2.17.1` (released 2026-11-02, amd64 only on Docker Hub), `PWPUSH_MASTER_KEY` and `SECRET_KEY_BASE` generated into `.env`, and the high port 5100 published over plain HTTP instead of the 443 and `TLS_DOMAIN` setup that upstream recommends. Upstream gives no RAM figure, so our 512 MB floor is an estimate. In the catalog, Onetime Secret and Yopass are the other one-time-link services, the first built around a single secret and a Valkey store and the second encrypting in the browser, and Vault, OpenBao, Infisical and Phase hold application credentials; Password Pusher is the one that handles URL and QR pushes, keeps an audit trail for signed-in users and runs on SQLite alone.
What you need
Any VPS with at least 512 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
Password Pusher's README and Compose file flag these before you rely on it:
non-negotiableUpstream's quick start is HTTPS: set TLS_DOMAIN to a domain pointing at the host and the container gets a Let's Encrypt certificate on port 443. Our snippet leaves that out so it can run on an IP address, which means links and pushed secrets travel over plain HTTP. Put a TLS proxy in front or use TLS_DOMAIN before sharing real secrets.
non-negotiablePWPUSH_MASTER_KEY is the encryption key for the database. The Compose file says that if it is omitted a default key is used, and offers PWPUSH_MASTER_KEY_PREVIOUS for rotation. Our snippet generates one into .env; back it up, because content encrypted under a lost key cannot be read.
non-negotiableAccounts and logins need mail: the Compose file marks SMTP settings as required for account emails and logins, and none are set in our snippet. Its list of settings shows PWP__ALLOW_ANONYMOUS as true: anyone who can reach port 5100 can create text, URL and QR pushes, and sign-up is open by default (PWP__DISABLE_SIGNUPS), so keep the port private. Creating a file push requires a signed-in account. Our run only checks /up, so we did not push a secret or create an account.
non-negotiableThe README separates the open-source repository from Pro: hosted Pro features are "periodically migrated" to the open-source edition, and a paid Self-Hosted Pro with licensing exists for features not yet in it. What you get from this image is the Apache-2.0 edition only.
non-negotiablePushes and uploads live in SQLite under /opt/PasswordPusher/storage, the pwpush-storage volume. The Compose file warns not to mount a volume over /opt/PasswordPusher/db because that hides the migrations and breaks upgrades. The image is pinned with platform: linux/amd64, and Docker Hub lists only amd64 for this tag.
non-negotiableThe Compose file shows default expiry of 7 days and 5 views for password pushes, with limits up to 90 days and 100 views, all adjustable by PWP__PW__* settings. A push made with the defaults stays retrievable for several views, so lower them if you want a strict single view.
Password Pusher used 327 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 512 MB.
Is the Password Pusher install snippet verified?
The Password Pusher install snippet is marked verified on Ubuntu 26.04 (Nov 2026).