Shared authenticator · credential vault
Your team needs six digits. It does not need the seed those digits come from. Vaultio keeps every shared 2FA seed on the server and hands out codes one at a time: revocably, and on the record.
Audit
Nobody receives a seed, so nobody keeps one. Offboarding is a revoked grant, not a weekend of rotating accounts at every provider and re-enrolling everyone who still works there.
How it works
Scan the provider QR with a camera, upload a screenshot of it, paste the otpauth:// link, or type the secret. Backup codes are captured in the same step, because that screen is the only time a provider shows them.
Access is a grant held against someone, with an optional expiry, not a copy of anything. Revoking takes effect on their next request, and deactivating an account withdraws every grant it holds at once.
A tile stays blank until it is tapped. One tap returns the code for the current period; it disappears when that period ends. One request, one code, one audit row.
Capabilities
The seed is decrypted, turned into six digits, and dropped. It never reaches a response, a log line, or an error message.
Someone who lost their authenticator asks; every administrator is notified; an approval releases exactly one stored code through a single-use link that expires in minutes.
Everyone also gets personal authenticators and password entries, sealed under a key derived from their password. An administrator cannot open it because they hold no key.
Send a stored password or an ad-hoc secret to somebody with no account. The link works once, then the contents are erased. Link previewers cannot burn it.
Pricing · per person, per month · cancel whenever
Shared accounts multiply. Charging by the authenticator would push you to keep some of them out of Vaultio, which defeats the point.
The whole product, up to three people, for thirty days. Long enough to enrol a real shared account and revoke it.
$0for 30 days, up to 3 people, no card
Pick a plan when it ends. Nothing is re-enrolled and no history is lost.
Most teams land here
For a team that shares real accounts and needs revocation to mean something.
$4per person, per month
$48 per person, billed annually. Save 20%.
Adds governance
For an organisation that has to prove who held which access, and when.
$7per person, per month
$84 per person, billed annually. Save 22%.
Need more seats, invoicing or custom terms? Talk to us
Trial terms
The trial is the full product, because the thing you need to test is whether revocation really works, and you cannot test that against a feature that has been switched off.
Do nothing and the workspace turns read-only for thirty more days: codes stop, nothing is deleted, and your enrolled accounts, grants and audit history are waiting whenever you come back.
Plan detail
| Feature | Trial | Team | Business |
|---|---|---|---|
| Shared accounts | |||
| People | Up to 3 | Unlimited | Unlimited |
| Duration | 30 days | Monthly or annual | Monthly or annual |
| Shared authenticators | Unlimited | Unlimited | Unlimited |
| Grant expiry dates | Yes | Yes | Yes |
| Enrol by camera, upload, link or text | Yes | Yes | Yes |
| Custody | |||
| Backup-code custody | Yes | Yes | Yes |
| Request and approval workflow | Yes | Yes | Yes |
| One-time share links | Unlimited | Unlimited | Unlimited |
| Governance | |||
| Audit history | 30 days | 1 year | 3 years |
| Audit export | CSV | CSV | CSV, JSON |
| Enforce two-factor sign-in | — | — | Org and per account |
| SAML / OIDC single sign-on | — | — | Yes |
| SCIM provisioning | — | — | Yes |
| Operations | |||
| Uptime commitment | — | — | 99.9% |
| Support | Email, 2 days | Email, 2 days | Email, 8 hours |
Threat model
Every design that solves something gives something up. Ours is written down here, because a security product that only lists its strengths is telling you half of what you need.
An attacker holding both the database and the application key could generate codes for every shared account you enrolled. That is inherent to computing codes on the server, the same property that lets us hand out access without handing out secrets. We narrow it with audit, rate limits, one-period reveal windows and enforced second factors on administrators. If your threat model cannot accept a vendor holding those seeds at all, Vaultio is the wrong tool.
The master key sits in the server-side session while its owner is signed in. Signing out, locking, or going idle drops it.
The key is derived at the one moment the password is available. A session that has not passed its challenge can reach no page, but the key does exist for that window.
We offer it because it gets people onto some second factor rather than none. An administrator can switch it off for everybody.
Questions
Their next request is refused. Nothing is rotated and nothing is re-enrolled, because they never held the seed, only codes that expired within thirty seconds of being drawn. That is the difference between a grant and a copy.
No, and not as a matter of policy. Personal items are sealed under a key derived from your password, which we never store. Shared company material is different by design: the server must be able to read it to generate a code for anyone you have authorised.
Use the recovery code shown to you once when the vault was created; it still works after any number of password changes. Keep it somewhere that is not Vaultio.
An authenticator app or a code sent by email. Either can be switched off, and on Business either can be required for everybody with a per-account override. Hardware keys are not supported today.
On day thirty-one you choose Team or Business and your enrolled accounts, grants and audit history carry across untouched. Choose nothing and the workspace turns read-only for thirty more days: codes stop, but nothing is deleted.
Still have a question? [email protected]
Start a trial
Trials are opened by a person rather than a signup form, because the first thing worth doing is enrolling one of your real shared accounts, and it helps to have somebody on hand while you do it.