When people say “decentralized password manager,” they often mean one of two things: a client that encrypts locally and syncs through some backend, or a service that does not live on a single company's infrastructure. Qerron is the second kind, with the first kind of encryption in front of it.
If you build software, you already know what a single-region outage looks like from the other side — and what it means when your users' most important data sits on a landlord's servers under terms that can change. That is the problem Qerron is built around, and why it runs on the Internet Computer.
The app is a pair of canisters, not a rented VM.
Qerron is a passkey vault. The frontend and backend are canisters: WebAssembly units that serve the app and store ciphertext. Those canisters are replicated across many independent machines, in different data centers, run by different operators. There is no single company server that has to stay up for the vault to be reachable, and no single host that can decrypt what you stored.
That is the same idea, in plainer language, as the note on what happens when a big cloud provider has a bad day. On ICP, the app and its data are not sitting on one vendor's stack. Costs are straightforward and predictable, with no surprise bills from piling up separate cloud services.
Encryption, and who can read the store.
Items are encrypted on your device with vetKeys threshold encryption before they are stored. We cannot open your vault, and no single server can either. Operators can see counts, check-in state, and billing status. They cannot see vault contents. The canister itself cannot decrypt the items.
Sign-in is a passkey through Internet Identity. We do not keep a password database of ours to leak. The product is a password manager without a master password; the comparison of the two unlock methods is in passkey vs password.
What this is not claiming.
This is not a claim that the system is unhackable or tamper-proof. It is a different trust model: threshold cryptography, a public network, and a company that cannot read stored data. You should still be careful about whom you share a vault with, and whom you name for emergency access.
If we ever shut the company down, the plan is that the canisters can keep serving the vault, and you can always export. That is a design goal worth stating plainly, not a guarantee about the future of any network.
Try the product, not just the architecture.
The useful test is still the one a person does: create a passkey, put something in, share a vault, and set a check-in. You can try the full product for fourteen days, with no credit card required. Personal is $48 a year. Household is $72 a year. The walk-through is on how it works.
Try it free for 14 days, no credit card needed.