Teams · DevOps · Engineering
Your team shares secrets every day.
Most of them end up in Slack.
VoidNote gives every person on your team a secure, zero-knowledge way to deliver credentials — to colleagues, contractors, CI runners, and AI agents — without leaving a trace in chat history.
Where your team's secrets actually live
Slack DMs
Credentials sent in messages live in workspace history indefinitely. Former employees, admin exports, and workspace breaches all expose them.
Email threads
Credentials forwarded to a contractor sit in both sent and received inboxes, on every synced device, for years.
Shared .env files
A .env in Dropbox or a shared drive stays accessible until someone manually revokes access — which rarely happens after off-boarding.
Git history
A key committed once — even in a private repo — is permanently in history. GitHub scanning bots find and abuse exposed keys within minutes.
Every security audit finds the same thing: credentials scattered across communication tools, with no expiry and no audit trail of who saw what. The problem isn't discipline — it's that there hasn't been a fast, frictionless alternative.
How teams use VoidNote today
- 1
Developer onboarding
Instead of pasting a list of API keys into Slack, create a single VoidNote with all the new joiner's credentials. They read it once — it self-destructs. No credentials in the onboarding thread.
- 2
Contractor credential handoff
Grant a contractor exactly the access they need for the engagement, via a single-use link. When the note self-destructs after they read it, there's nothing to revoke and no copy persisting in their inbox.
- 3
CI/CD pipeline bootstrapping
Deliver the initial secrets a new pipeline needs via a VoidNote link. The runner reads it once, loads the credentials into environment variables, and the link is dead.
- 4
AI agent provisioning
Drop a VoidNote link into a Claude Code CLAUDE.md or system prompt. The agent reads the credentials once, they're in memory, and the note self-destructs. Keys never in a file or conversation log.
- 5
Incident response
During an incident, rotating credentials and securely distributing replacements to the people who need them — without broadcasting to a whole Slack channel — is a frequent bottleneck. VoidNote handles it in seconds.
Current team options
Void Unlimited
$20/mo
- ✓Unlimited notes — no credit counting for heavy use
- ✓500 GB encrypted Vault / month
- ✓API key — automate delivery from pipelines and scripts
- ✓Priority support
Best for engineering teams: one subscription, one API key, unlimited team-wide usage.
Subscribe to UnlimitedCredit packs
Pay as you go
- ✓100 credits / $5 — up to 1,000 at better rates
- ✓Credits never expire
- ✓Pay by card or crypto
- ✓Good for occasional team use
Buy a large credit pack and distribute it across the team. Credits don't expire, so there's no rush.
Buy creditsTeam accounts with shared billing
We're building first-class team support: a single subscription that covers every member, a shared credit pool, and a team admin dashboard. Here's what's planned:
Shared credit pool
One balance, shared across the whole team. Top up once from a company card.
Member management
Invite team members, assign roles, and remove access when someone off-boards.
Usage by member
See who created what (metadata only — never note content) for cost attribution.
Centralised API key
One API key for all team scripts and pipelines, with per-member attribution.
Team Vault quota
Shared vault storage across the team, pooled under a single subscription.
Priority onboarding
Dedicated setup call and priority support for team accounts.
Get early access
Team billing is in development. If you need it now — or want to help shape how it works — reach out. Teams that contact us before launch get priority access and a discounted rate.
Contact us about team billingWhy teams can trust VoidNote
Irish-registered company
Quantum Encoding Europe Limited, registered in Ireland (CRO No. 807205). Subject to GDPR — not a US company that can be served a National Security Letter.
Zero-knowledge by architecture
The decryption key lives only in the URL fragment — never sent to our servers, never in a request log. We cannot read any note, even under compulsion.
No tracking or analytics
No Google Analytics, no session recording, no ad pixels. The only cookie is a functional session cookie required for login.
Verify it yourself
Open DevTools, create a note, watch the network tab. No plaintext, no key. Open-source SDKs on GitHub. The encryption model is fully auditable.
Ready to stop leaking secrets in Slack?
Start with a free account. Upgrade when your team needs more. Team billing coming soon.