Quick-Start
Choose how to use Password Pusher: hosted Pro, self-hosted Pro, OSS self-hosted, or the public OSS demo.
Password Pusher helps you share secrets with expiring, one-time links instead of email or chat. You can run it as a hosted service, buy a license to self-host the Pro edition, or deploy the open-source edition yourself. Pick the path that matches who operates the servers and which features you need.
Integrations: Many third-party apps, CLIs, and scripts talk to Password Pusher through API v2—no matter where it is hosted.
Four ways to get started
1. Password Pusher Pro (hosted, US or EU)
Best when: You want a managed service without running your own servers—from free basic use (including requests) up to Premium or Pro with file uploads, branding, teams, and more.
It is free to use for core features (text, URLs, QR codes, requests with text-only responses, and the like). Extensive branding, custom domains, and file uploads (including file attachments on request responses) are not included on the free tier and require a paid plan.
Subscribe at your preferred data residency region: us.pwpush.com (US) or eu.pwpush.com (EU). Regions are separate deployments; pick EU if you need GDPR-aligned hosting. See Regions for how this choice works.
Pricing and plan tiers: pwpush.com/pricing.
2. Self-Hosted Pro (purchase)
Best when: You need Pro capabilities (SSO, advanced storage, air-gapped options, full data control) on your network or cloud.
You purchase a license and run the official Pro containers on infrastructure you control. This is not the same as the open-source Docker image—it is a licensed product with Pro-only features and support options.
Start here: Pro Self-Hosted Overview — plans, requirements, and links to Getting started checklist and Self-Hosted Pricing.
3. Open-source edition (self-hosted)
Best when: You want a free, self-managed instance and are fine with the OSS feature set (secure pushes, API, admin tools, rebranding—without hosted-only or Pro-only capabilities).
Deploy with Docker or other methods using the public project:
- OSS Self-Hosted Overview — why and when to self-host OSS
- Installation — Docker Compose and other deployment options
- Source: Password Pusher on GitHub (Apache 2.0)
4. Open-source edition (try online)
Best when: You want to try the same OSS codebase in a browser before installing anything.
Use the community-hosted instance: oss.pwpush.com. Treat it like any shared demo: do not place highly sensitive production data there; run your own instance for full control and policy compliance.
How these options differ (at a glance)
| Operated by | Typical use | |
|---|---|---|
| Hosted Pro / Premium | Apnotic (you choose US or EU) | Subscriptions at pwpush.com, no servers to manage |
| Self-Hosted Pro | Your organization (licensed) | Compliance, private cloud, air-gap, SSO at scale |
| OSS self-hosted | You (free, open source) | Full control, OSS license and feature set |
| oss.pwpush.com | Community demo of OSS | Quick trials; not a substitute for private hosting |
For a fuller edition comparison (OSS vs Premium vs Pro vs Self-Hosted Pro), see Editions and the feature matrix on pwpush.com.