Bitwarden stores your passwords. VoidNote shares them — once.
Bitwarden is one of the best password managers available. But sharing a password with someone who isn't on Bitwarden, or who shouldn't have permanent access, still means falling back to Slack or email. VoidNote fills that gap: a zero-knowledge encrypted link that works once and then permanently self-destructs — no shared account needed on either end.
The sharing gap Bitwarden doesn't close
Bitwarden's sharing features (Collections, Organisations) require both parties to have a Bitwarden account — and they create a persistent shared credential, not a one-time handoff. That's the right design for a team that needs ongoing shared access. It's the wrong tool for:
- · Handing a database password to a contractor who shouldn't have permanent access
- · Delivering an API key to a CI runner or AI agent that should use it once
- · Sharing credentials with a client who doesn't have (and shouldn't need) a Bitwarden account
- · Sending a secret to a colleague in a way that provably disappears from all logs
In all of these cases, most teams fall back to Slack or email — which stores the credential in plaintext indefinitely. VoidNote handles the handoff: encrypt, share once, destroy.
Bitwarden + VoidNote: complementary, not competing
Bitwarden
- ✓Your personal and team password vault
- ✓Autofill across browsers and devices
- ✓Long-term shared team credentials
- ✓Password generation and health reports
VoidNote
- ✓One-shot credential delivery — no shared account needed
- ✓Self-destructs after reading — no persistent copy
- ✓Works with contractors, clients, AI agents, pipelines
- ✓CLI + SDK for programmatic secret delivery
Technical comparison
| Feature | Bitwarden | VoidNote |
|---|---|---|
| Encryption | AES-256 client-side | AES-256-GCM client-side |
| Server holds key? | No | Never — key only in URL fragment |
| Persistent storage | Yes — vault stored indefinitely | No — auto-destructs after read |
| Sharing model | Persistent shared collection | Single-use encrypted link |
| Recipient needs account? | Yes (for shared collections) | No — just a browser |
| Open source | Yes | SDKs open source on GitHub |
| Self-hosting | Yes (Vaultwarden) | No |
| CLI & SDK | No | Yes — 6 languages |
| Self-destructing secrets | No | Yes |
| Anonymous use | No | Yes |
A real workflow: onboarding a contractor
1. Save database credentials in Bitwarden
2. Contractor doesn't have Bitwarden → paste into Slack DM
3. Credential now lives in Slack history, indefinitely
4. Contractor off-boards → you delete Slack message (too late)
Result: credentials in a former contractor's message history.
1. Save credentials in Bitwarden
2. Create a VoidNote with the contractor's specific access credentials
3. Paste the link into Slack DM
4. Contractor reads it — note self-destructs
Result: credential was in their Slack for seconds. Gone.
Fill the gap Bitwarden leaves open
Zero-knowledge one-shot delivery. No recipient account needed. Self-destructs after reading.