Password Pusher Alternative: Free Client-Side Encryption
Feature-rich server-side encryption vs zero-knowledge client-side encryption.
How Password Pusher works
Paste a password, set view and time limits, get a link. Password Pusher uses server-side AES-256-GCM encryption. The secret goes to the server as plain text over HTTPS, gets encrypted at rest, and is decrypted for the recipient. Their documentation is upfront about this: they don't provide client-side encryption.
What Password Pusher does well
It's the most feature-rich server-side option. Open source, self-hostable, configurable view limits from 1 to 100, expiry up to 90 days, audit logging, and an API for automation. If you need detailed audit trails or high view counts, PwPush has them. The project is actively maintained and well-documented.
The trade-offs
File sharing is a paid feature, starting at $19/month. Files use cloud storage encryption rather than the same database encryption applied to text. The encryption is server-side, so the server handles your secret in readable form. If you self-host, you control the server. If you use the hosted version, you're trusting their infrastructure.
Client-side encryption
With Secret.Broker, your browser encrypts the secret with XChaCha20-Poly1305 before anything goes to the server. The encryption key stays in the URL fragment. The server stores ciphertext it can't decrypt. File attachments up to 20 MB are compressed and encrypted with the same cipher. No paid tiers. The protocol page documents the full stack.
Feature comparison
- Password Pusher: server-side AES-256-GCM, open source, self-hostable, view limits 1-100, expiry up to 90 days, audit logging, API, file sharing from $19/month
- Secret.Broker: client-side XChaCha20-Poly1305, file attachments up to 20 MB (free), view limits 1-25, expiry 15 min to 30 days, paranoid mode, no account, no API
Also compare: vs Privnote and vs OneTimeSecret.
Common questions
Is Password Pusher secure?
Password Pusher uses server-side AES-256-GCM encryption. Their documentation states explicitly that they don't provide client-side encryption. Your secret is encrypted after it reaches the server. The code is open source and self-hostable, so you can verify the encryption logic and control the server.
Is Password Pusher free?
The core text sharing is free and open source. File sharing requires a paid tier starting at $19/month. Files use cloud storage encryption rather than the same database encryption applied to text. Self-hosting is free but requires your own infrastructure.
What's the difference between Password Pusher and Secret.Broker?
Password Pusher offers server-side AES-256-GCM encryption with extensive features: view limits up to 100, expiry up to 90 days, audit logging, and an API. File sharing is paid. Secret.Broker uses client-side XChaCha20-Poly1305 encryption where the server never sees the plaintext. File attachments up to 20 MB are free. No account needed. See the full alternatives comparison for more detail.