Credential manager for teams
Human-made passwords break in seconds.
A made-up password follows patterns, and patterns strip out almost all the value its length promises. The hardware attacking it has gotten a hundred times faster since 2019. A machine-generated credential has no patterns to discount — we generate, store, and share your credentials.
- Six item types
- Data in the European Union
- MCP agents, values redacted
Cloudflare — Aurora
Login · Infrastructure
Username
Password
Estimated resistance
2019 — GPU rig
6minutes
10¹¹ guesses/second
2026 — accelerated cluster
4seconds
10¹³ guesses/second
Offline attack on a stolen hash, of the fast-to-compute kind. Half the keyspace, at the rates shown. A password a person chose is worth less than its length suggests — the calculation discounts common patterns.
46
bits in a made-up password
The example in the instrument above, once its patterns are discounted.
123
bits in a generated credential
Twenty characters drawn from an alphabet of 71.
100×
guesses per second, against 2019
From 10¹¹ to 10¹³ — both rates are printed above.
6
item types in every vault
Logins, notes, cards, API keys, SSH keys, identities.
Where they are right now
The clock moved. The team's habits didn't.
Nobody decided to keep the client's password in a chat thread. It was the closest thing to hand on a Tuesday afternoon — and it stayed there.
A credential typed into a channel stays there as long as the channel does. Someone who joins six months later opens the history and reads it, without asking anyone and without leaving a trace.
The spreadsheet is the same thing in another shape: one row per service, nine people with access, and nobody knows who opened it yesterday or where they copied it.
A credential in four places isn't a credential: it's four copies, and the one that counts is the least careful.
The same password, four places
#general · 2:02 pm · two years ago
Ana.Maria.Silva99
Twenty-four people in the channel. Nine joined after this message.
access.xlsx · shared with 9 people
Ana.Maria.Silva99
Row 14, column D. Copied into Meta Business Suite in January.
.env · three laptops, one repository
DATABASE_URL=postgres://demo:EXAMPLE@db.internal:5432/app STRIPE_SECRET_KEY=sk_live_EXAMPLE_4tQ9mZ2pR7wK RESEND_API_KEY=re_EXAMPLE_8nD4kV6yT2xQ
Copied by everyone who set the project up. Nobody deletes it again.
Left the team in March
carlos@aurora.pt
Lost email on the first day. Signs in to Meta Business Suite with the line above.
Generated, not invented
A credential nobody chose has no patterns to discount.
Length is only worth something when every character is drawn. Move the length and the alphabet, and watch where the meter stops.
Generator
Generated credential
zSkde*~JDBe&PMqk+8Bc
Resistance
Strong
123bits of entropy
20 × log₂(71) = 123
Every character comes from crypto.getRandomValues. The alphabet leaves out the glyphs that get confused — 0 and O, 1 and l — so the arithmetic uses the real alphabet rather than the 95 of printable ASCII.
Entropy is in the draw, not in the string
Two strings can look equally scrambled and be forty bits apart. What counts is the space they came from — and for a value we generated, that space is known rather than estimated.
Every character is worth log₂ of the alphabet
Over the full alphabet, each character adds 6.15 bits. Without digits or symbols it adds 4.64 — nearly a bit and a half less, in every position.
Seventy bits is where the year starts
Below 70 bits, the 2026 cluster gets there inside a year. From 90 up, the instrument at the top of the page has no figure left to show.
Vaults
Every system in its own vault, with the fields that kind of item asks for.
Six item types. The fields change with the type, and the ones that are secret arrive covered — revealing is a gesture, not the default state.
Login
Meta Business Suite
Vault: Client — Aurora
Updated 2026-08-14
- Username
- social@aurora.pt
- Password
- hidden value
- Website
- business.facebook.com
Sharing
Who can do what, written once per vault.
Three roles. A member uses the items, an admin decides who gets in, the owner answers for the vault. Nobody has to forward anything to anyone.
| Capability | Owner | Admin | Member |
|---|---|---|---|
| View, reveal, and copy the items | Yes | Yes | Yes |
| Create and edit items | Yes | Yes | Yes |
| Create and revoke one-time links | Yes | Yes | No |
| Manage the vault's members | Yes | Yes | No |
| Transfer or delete the vault | Yes | No | No |
One-time link
rp.link/s/EXAMPLE-9fk2Qm
Opened once · closed
For someone outside the vault: the supplier, the accountant, the person who starts tomorrow. It opens once; the second time, it doesn't.
Leaving the team becomes a membership change.
Removing a person from a vault removes everything that was inside it, at once. Not a hunt through DMs, not a list of services to review, not the password that stayed in circulation.
Vault health
What's weak, what's repeated, what hasn't changed in a year.
The review nobody does by hand. Three counts, and the list of what causes them.
4
Weak
Below 70 bits.
2
Reused
The same value in more than one service.
7
No rotation
Unchanged for more than twelve months.
Flagged items
13
Shared password
The same value in both. Changing one doesn't change the other.
WordPress — AuroraMeta Business SuiteReused2 servicesAnalytics — Aurora
Chosen by a person in 2024, and never touched since.
Google AnalyticsWeak49 bitsMillennium BCP — company
Unchanged since June 2025. Three people with access.
BankingNo rotation14 months- 10 more in the vault's full list.
Agents · MCP
Give your AI access without giving it the secret.
The agent asks for the item by name and gets what it needs to act. The plaintext value stays in the vault. None of the four products we compare against can say that.
The agent asks for a credential
An MCP tool, called with the vault's name and the item's name. The agent doesn't get the whole vault: it asks for what the task needs.
The request is scoped and logged
One vault, read only, a window of minutes. The line lands in the audit log before there is a response — under the agent's name, not a person's.
The response comes back redacted
The secret field returns covered. The agent keeps the shape of the value — the prefix, the length — and enough to use it; never the value itself.
The action completes
The task finishes. What is left in the conversation history is twelve dots, and the credential is still good tomorrow.
Agent
secrets.get_item
Response
{
"item": "Stripe — payments",
"value": "redacted value",
"redacted": true
}
DoneTest charge placed. The value never left the vault.
Illustrative sequence. The key above does not exist.
Scope is per vault, not per account
An agent joins a vault the way a member does: with that vault's items and nothing else. Taking its access away is a membership change, the same as a person's.
Every read is written down
Who asked, which item, at what time, under what scope. The audit log is the same for people and for agents, and it is the only list you have to read afterward.
Sovereignty
Your data stays in the European Union, in a Supabase project you own.
Encryption happens in your browser. What reaches the server is ciphertext — and the server is a database in your account, not a tenant in ours.
What never leaves
- Your passphrase.
- The key derived from it.
- The plaintext value of any covered field.
What leaves, and in what state
- The items, encrypted before they go.
- The metadata that makes the list work: title, vault, date.
- The audit log lines: who, what, when.
A European region, chosen by you
The Supabase project is created wherever you say. Data residency becomes a setting in your account, not a footnote in ours.
The keys don't pass through us
Each vault's key is derived from your passphrase, in your browser. We cannot read a vault's contents — and that is not a policy, it is a lack of means.
The exit stays open
The database is yours from day one. If we ever stop making sense, the data does not move: the software on top of it does.
Comparison
Where we win, and where we don't yet.
Four mature products and one new one. The rows where we are behind are here for the same reason as the rest: they are true.
| Feature | Secrets Manager | 1Password | Bitwarden | LastPass | Dashlane |
|---|---|---|---|---|---|
| MCP server for AI agentsThe agent lists and creates items; the secret's value comes back redacted. | |||||
| Import a whole .env, split by variable | |||||
| Data in the European Union, in your own Supabase project | |||||
| European Portuguese interface | |||||
| End-to-end encryption, zero-knowledge | |||||
| One-time share links | |||||
| Runs on your own infrastructureRuns on a Supabase project you own. | |||||
| Independent security auditWe are new and have not had one yet. It is on the roadmap. | |||||
| Browser extension with autofill | |||||
| Passkey sign-in |
Where we are behind, plainly.
No browser extension, no mobile apps, no passkey sign-in, and no independent security audit. If you need those this week, the mature products are the right pick — and we would rather say so here.
Comparison from August 2026, based on what each product documents publicly. Products change fast; check each vendor's own site. Trademarks belong to their owners, and this is not an affiliation.
Pricing
The vault at market price. Separately, the one thing nobody else sells.
The headline figures are annual. Month to month costs one euro more per user, and canceling ends it at the close of the period you already paid for.
Free
One person, or a team trying it before deciding.
€0per user/month
No card, no term.
- Personal vaults, with all six item types
- Generator, strength meter, and a breach check
- Three one-time links a day
- Vault health panel, in its simple form
Team
RecommendedSmall companies, agencies, and startups, from two users up.
€4per user/month
Billed annually.
€5 per user/month if you pay monthly
- Everything in Free, with no cap on links
- Shared vaults, with owner, admin, and member
- 90 days of audit log
- Data in the European Union, and MFA an admin can require
Business
Larger teams, and anyone who answers to a risk department.
€8per user/month
Billed annually.
€10 per user/month if you pay monthly
- Everything in Team
- SSO and SCIM
- Unlimited audit log, with export
- Region choice, and hosting on your own Supabase
Separate from the seats
Automation
€25per workspace/month
Added to Team or Business.
3 agent connections included · €6 per additional connection/month
The MCP server, time-boxed scopes, and capture of whatever gets pasted into a team channel. It is the line none of the four products beside it has to sell.
- MCP server, with values redacted by default
- Per-vault scopes and time-boxed grants
- Every agent read in the audit log
- Capture of whatever gets pasted into a team channel
Euros, excluding VAT. The first cohort gets half price for twelve months, with the price locked for twenty-four — we are early, and the discount says so.
Questions
Straight answers.
The five that always come up, and three that should come up more.
Can you read my secrets?
We cannot read a vault's contents. The key is derived from your passphrase, in your browser, and end-to-end encryption happens before anything leaves it. What we store is ciphertext and the metadata that makes the list work: titles, vaults, and dates.
Where does my data live?
In a Supabase database you own, created in a European Union region you choose. Data residency does not rest on a promise from us: it rests on where you created the project, and you can see it in your own console.
What happens if I lose my passphrase?
We cannot reset it, and that is exactly the property that answers the first question. A shared vault stays reachable for whoever else has it, and that person lets you back in. A personal vault whose passphrase is gone does not come back.
How does an AI agent use this safely?
Through the MCP server. The agent lists items and creates items; when it reads a secret, the value comes back redacted. Access is per vault, it expires, and every read lands in the audit log under the name of the agent that made it.
What if we leave?
Export the vaults and take them. The database is already yours, so the data does not even move: our software stops running on top of it. Monthly means monthly, and canceling means canceling, at the end of the period you paid for.
What don't you have yet?
A browser extension with autofill, mobile apps, passkey sign-in, and an independent security audit. All of it is on the roadmap and none of it is built. If you need those this week, you heard it from us.
Is this as secure as the established products?
The encryption model is the same class: the key is born in your browser and the server only sees ciphertext. Where we are genuinely behind is track record and the independent security audit. We are new, and a sentence does not fix that.
Why would a team switch?
Three reasons, and if none of them is yours, stay where you are: you want agents using credentials without seeing them, you are tired of carrying .env files from laptop to laptop, and you want your data in the European Union, on infrastructure you control.