Home / Software Alternatives

Bitwarden Send Alternatives: Secrets Without the Vault

Close-up of a golden padlock secured on a rope against a blurred water background.

Photo: Rahime Gül / Pexels

Grade the trust model, not the feature list

A secret-sharing tool makes three promises, and they are worth more than any feature grid. First, who can read the secret in transit: a zero-knowledge design encrypts in your browser and the server stores ciphertext, while a conventional design asks you to trust the operator's database. Second, who needs an account: Bitwarden Send requires the sender to hold a Bitwarden account, which is a strange toll for sending one password to a client. Third, when the link dies: after one view, after N views, after a set number of days, or never unless you remember to revoke it. Bitwarden Send's own rules frame the category: text Sends are free for account holders, file Sends require Premium at $1.65 a month billed annually ($19.80 a year), and Sends live inside your vault's ecosystem. Every alternative below wins on at least one of the three promises.

ToolAccount to sendWho can read it in transitLink dies
Bitwarden SendYes, Bitwarden accountBitwarden's end-to-end designBy date or view settings
Password PusherNoServer holds it for deliveryAfter set views or days
PrivateBinNoNobody: ciphertext only on the serverAfter reading or expiry
OneTimeSecretNo for basic linksServer holds it until the one viewAfter exactly one view
OnionShareNoNobody: direct from your machineWhen you stop sharing

Password Pusher: the working default

Password Pusher (pwpush) is the tool most teams actually need. You paste a password or attach a file, set an expiry in views or days, and get a URL to hand over; the recipient needs no account, no app, and no instructions beyond the link. The public service is free, and the software is open source under Apache-2.0, so an organization can self-host it and gain the features that make it an IT tool rather than a toy: audit logs of every push and retrieval, custom branding, and file pushes with real size limits. Its trust model is the conventional one: the server holds the secret until expiry, so a self-hosted install inside your own infrastructure is the version a careful team should run. For the daily flow of first-login passwords, vendor credentials, and Wi-Fi keys that otherwise end up in email threads, Password Pusher is the verdict, and the email thread is the competitor it actually replaces.

Interactive tool

Comparison Builder

Pick two or three products and see them side by side on the numbers that decide the purchase.

MeasureBitwardenPassword PusherPrivateBin
Starting paid price$1.65 per user/mo, billed annuallyFreeFree
Free optionFree plan: always free, unlimited passwords on unlimited devicesFree plan: the public service is free to use and the software is free and open source under Apache-2.0Free plan: the software is free and open source; public instances are free to use
PlansFree: free · Premium: $1.65/user/mo annual · Families: $3.99/user/mo annual · Teams: $4/user/mo annual · Enterprise: not publishedPassword Pusher (Self-Hosted): freePrivateBin (Self-Hosted): free
PlatformsWebWeb, LinuxWeb, Linux
Best forbudget users, privacy-focused teams, self-hostersIT staff sending first-login passwords, support teams sharing credentials with clients, replacing passwords pasted into email threadsone-off passwords and keys over chat or email, admins who self-host small utilities, anyone burned by secrets living in ticket history
StrengthsFree tier has no device or password limits; Open source and auditable; Self-hosting availableNo account needed to send or receive; View-count and time expiry on every link; Self-hosted installs add audit logs, branding, and file pushesThe server cannot read what you sent: encryption happens in the browser; Burn-after-reading and expiry are built in; No account for sender or receiver
Watch out forInterface is plainer than paid rivals; The built-in authenticator and file attachments sit on Premium, not FreeA link is a bearer secret: anyone holding it can open it; Free public instance limits file sizes and retention; Not a vault: nothing is stored for later retrievalText-first: not a file vault; Trust depends on the instance operator serving honest code; No delivery confirmation or audit trail

Lowest entry price: Password Pusher at Free per month flat. Real free plan: Bitwarden, Password Pusher, PrivateBin. Entry price is the floor, not the decision: check the plan line above for the tier that actually includes the feature you need.

All figures from vendor pricing pages, checked November 18, 2026. Some vendors price by contacts, tasks, or operations instead of seats; those notes are in the plan data and the linked pricing guides.

PrivateBin and OneTimeSecret: the zero-knowledge and the original

PrivateBin is the trust-model purist's pick. It is a minimalist open source pastebin in which encryption happens in the browser with a key carried in the link itself, so the server stores only ciphertext it cannot read, and pastes burn after reading or expire on your schedule. It is text-first (attachments exist but are not the point), free to self-host on any PHP web space, and its public instances cost nothing. Its caveat is subtle: because the code is served by the instance you use, you are trusting that instance to serve honest JavaScript, which is why self-hosting or a known public instance matters. OneTimeSecret is the category's elder: running since 2012, open source, with the purest promise in the set, a secret viewable exactly once. Its simplicity is the feature, and its edge is also its sharpest edge: one view means one view, and a chat preview bot fetching the link can consume the secret before your human does. Use PrivateBin when the operator must not be able to read the secret, OneTimeSecret when the flow must be dead simple, and warn recipients to open links in a real browser either way.

OnionShare and the vault-shaped remainder

OnionShare deserves its line for the cases where even a temporary server copy is too much: it shares files directly from your computer over the Tor network, and the transfer ends when you close the app. It is the strongest privacy position here and the least convenient, which is the usual exchange rate. The remainder of the category is context. If your secrets flow mostly inside one organization that already runs Bitwarden for everyone, Send's account requirement stops being a toll and becomes an audit trail, and staying is defensible: the Premium price ($19.80 a year) buys file Sends inside a system your team already trusts. The standalone tools win when recipients are outside your vault (clients, vendors, family), when you send rarely, or when the sender should not need an account at all. Our Bitwarden free tier audit covers Send's place in the free-versus-Premium ledger for readers deciding the larger vault question at the same time.

The verdict

Password Pusher (free, self-hostable) is the default Bitwarden Send alternative for teams and IT flows. PrivateBin (free, zero-knowledge) is the verdict when the server must be unable to read the secret. OneTimeSecret (free) is the simplest one-view link for human-to-human sends. Bitwarden Send remains reasonable inside an all-Bitwarden organization. The checklist below is the operating discipline that makes any of them safer than the email thread they replace.

Interactive tool

Secret Sharing Safety Checklist

Check off each step as you finish it. Your progress stays on this page.

0 of 6 complete

0% done

Related guides

More from this corner of the chart: these companion guides compare the nearest alternatives and head to head matchups.

Frequently asked questions

Why would I leave Bitwarden Send if I already have Bitwarden?

Three reasons recur. Recipients: Send assumes your world is inside Bitwarden, while clients and vendors are not, and standalone tools ask nothing of the recipient. Files: file Sends require Premium at $19.80 a year, while Password Pusher and PrivateBin handle files on free and self-hosted tiers. Shape: Send is one feature of a vault you must maintain, while a self-hosted Password Pusher is a single-purpose page your whole company can use without accounts. If none of those bite, Send is fine and this article's verdict says so.

Are one-time secret links actually secure?

They are secure against the threat they target: a secret that would otherwise live forever in an email inbox, chat history, or ticket system, searchable by anyone who later compromises or subpoenas that archive. The link itself is a bearer secret, so the delivery channel matters: send the link by one channel and, for anything sensitive, a passphrase by another. Zero-knowledge tools like PrivateBin additionally protect against the service operator. What no link tool protects against is a recipient who saves the secret insecurely at the other end.

What is the difference between Password Pusher and PrivateBin?

The trust model and the feature center. Password Pusher is a delivery service: the server holds your secret (encrypted at rest on the hosted service) until the view or day limit you set expires, and in exchange you get file pushes, audit logs, and branding, especially self-hosted. PrivateBin is a zero-knowledge pastebin: encryption happens in your browser, the server stores ciphertext it cannot read, and you give up the delivery tooling. Teams pick Password Pusher; privacy-first individuals pick PrivateBin.

Can I self-host these tools easily?

Yes; this category is unusually self-host friendly. Password Pusher runs as a small container or a conventional Rails deployment, PrivateBin needs only PHP web hosting, and OneTimeSecret publishes its open source code for self-hosting. All three are $0 in license fees. The operational duties are the usual ones (HTTPS, updates, and for Password Pusher, database backups if you want the audit log to survive), and they are lighter than self-hosting a full password vault, as our self-hosted vault comparison makes clear by contrast.

How do I send a secret to someone with no account and no app?

Use Password Pusher's public service or a public PrivateBin instance: paste the secret, set the shortest expiry that works (one view, or one day), and send the link. Tell the recipient to open it in a browser and save the secret immediately, because the link will not work twice. For a file, Password Pusher is the smoother path. This is the entire workflow, and its two-minute length is exactly why these tools beat both email and a vault feature for one-off sends.

Photo credits: Rahime Gül (Pexels). Photos are served from this site; follow the credit to the library page for the original.