Security
Built so a mistake stays small
Aker assumes mistakes happen: a laptop is lost, a password is pasted into the wrong window. The design keeps one mistake from becoming a company-wide incident.
Nothing sensitive at the edge
The portal you sign in to never holds a secret or a key. Sensitive work happens where it can't be inspected from a browser.
One key per secret
Each secret is locked with its own key, so opening one reveals nothing about the others. A leak stays a single leak.
Keys that can't be copied out
Encryption keys cannot be exported, downloaded, or carried away. Rotation is restricted to administrators and recorded.
Secret names stay private
Even the names of your secrets are hidden in storage, logs, and reports, so a report or log can't reveal what you hold.
Credentials that expire
Access is issued per request and expires on its own. Nothing standing to leak, and nothing for anyone to chase down later.
Every access on record
Who, what, and when, for every read, rotation, and expiry. Old values are never kept, so history can't become a liability.
When something goes wrong
A leak is a matter of when, not if. What matters is how small it stays and how fast you recover.
Contain it to one secret
A leaked value tells an attacker nothing about the next one. There is no shared password that unlocks the estate.
Rotate in minutes
Rotate the affected secret immediately. Systems that need it get the new value on their next request, with nothing to redeploy.
See exactly what was touched
The audit trail shows every access with who, when, and from where, so recovery starts with facts instead of guesswork.