Who can get in, if you're not there?
Vault stores the passwords, keys and access details per customer project, and gives your customer access to them through a portal or their own environment — without a password ever travelling through a mailbox.
What Vault is for
Anyone who manages environments for others — a web agency, an IT partner, a
system administrator with a handful of regular customers — naturally
accumulates a mountain of access details. Hosting panels, DNS, mail
accounts, licences, API keys, SSH keys. That mountain is usually spread
across a password manager, a few mailboxes and the memory of whoever set the
project up in the first place.
That’s fine until the moment it matters: someone leaves, a customer moves on,
or management passes to another party. Then it turns out nobody knows
exactly what there is, let alone how to hand it over properly.
- Record what belongs to each customer project. Passwords, keys,
certificates and licence files in one folder, with the backup status
alongside.
- Share what needs to be shared. A single item, or the whole project in
one action — to the customer’s own environment, or via a portal link if
they don’t have one.
- Withdraw it again once it’s done. One action, and the copies on the
other side are gone.
Who it’s for
- Web and IT agencies who manage environments for customers and want the
handover to be just as tidy as the delivery.
- Organisations with an external management party who want to be able
to show that they can reach their own access details themselves.
- Administrators working alone who don’t want to answer “and if you’re
not there?” with a spreadsheet.
Handing over without anything lying around
The usual way to share a password is to send it. That means it leaves your
control: it ends up in two mailboxes, maybe in a backup of those mailboxes,
and you can’t retrieve it anymore.
With Vault, a share stays a connection between two vaults. The recipient gets
their own copy, encrypted for them, in their own environment. If anything
changes on your side, they see that their version is outdated. Withdraw the
share, and the copy is gone — including the files in storage.
What it does
-
Organised per customer project
Not one big list, but a folder per customer and per project: hosting access, DNS, email accounts, licences and API keys together. Whoever opens the project sees at a glance what that environment runs on.
-
Files too, not just passwords
An SSH key, a certificate, a keystore or a licence file belongs with an environment just as much as a password does. You store those files encrypted in the same vault, and share them the same way.
-
Share a whole project in one go
Hand over a customer environment to the customer themselves, or to a colleague agency, in a single action instead of credential by credential. Add something to the project later, and it's included automatically.
-
Revoke it again in one action
When the collaboration ends, you withdraw the whole share and the shared copies disappear on the other side, including the files in storage. No leftover copies in mailboxes or spreadsheets.
-
Customer portal with its own link
Doesn't your customer have an account with you? Then share via a portal link: a restricted page where they can view their own access details, without any user management and without you forwarding anything.
-
Backup status at a glance
For every project you keep track of how the backup is doing, so the question 'is that backup actually still running?' has a place instead of staying an assumption.
What does Vault cost?
Free to use
Demo
Free
30-day trial
Gratis
Free
Prices exclude VAT. You activate the applications you need and pay for those only; you can cancel per billing period. The 30-day trial ends on its own.Create account
Frequently asked questions
- Why is this better than a shared password manager?
- Because the problem usually isn't storing, it's handing over. A customer who leaves, an agency that takes over management, or a colleague who joins the project: then something has to go out, and in practice that happens by email or a messaging app. Vault turns that handover into an action in the system — with a trail of who got what and when, and a button to withdraw it again.
- What happens if I add a password to a shared project later?
- It's shared automatically with the existing share, so the recipient doesn't fall behind your vault. Change a password, and the recipient sees that their copy is outdated and fetches the new version.
- Can my customer get in without an account?
- Yes, via the customer portal: a restricted link to a page with only the data intended for that customer. If the customer does have their own environment on the platform, you can instead share directly to that environment — then the data ends up in their own vault.
- How is the data secured?
- Passwords and files are stored encrypted with a key per organisation. When shared, the value is re-encrypted for the receiving organisation, so both sides keep their own key. Data belonging to another organisation is never reachable, not even by a detour — that's a boundary guarded in several places at once.
