For small teams
Two problems show up once more than one person needs a password. Everyone ends up sharing one login nobody can change, and the deployment scripts end up with a copy pasted into a settings page. Passoword gives each person their own account and each script its own limited key.
What a team gets
a separate key for every script
The key a build server holds opens one vault. Not the account, not another team’s vault, and it cannot create more keys.
-
one key per job
each key opens one vault and nothing else. Switch it off without disturbing anyone.
-
you can see who changed what
every edit is signed by the device that made it.
-
people leave, laptops get switched off
turn off their device and its access ends. No mass password reset.
-
€40 per person per year
or €4 a month. 10 GiB of file storage each.
-
keep it on your own servers
same software, no licence check. Useful if your contracts say where data lives.
-
we cannot read it either
the hosted version holds scrambled data. Paying does not change that.
In a build job
The script asks for a password by name instead of keeping its own copy. Nothing is written to disk unless you ask for it, and when it is, only the owner can read the file.
One honest limit: switching a key off stops the next read, not the last one. Anything a script already copied somewhere is still sitting there, so change those passwords too.
on the build server, then in the job
$ PASSOWORD_ADAPTER_TOKEN=pwauto_... \
passoword-adapter --state-dir ./state
$ passoword inject \
--input app.env --output .envNot built yet
There is no single sign-on, no syncing with your staff directory, and no admin console. You add people one account at a time and each seat is billed on its own. If your company needs those things to approve a purchase, this is not ready for you yet, and the Business plan is priced for what it actually does.