Platform features

Every secret in one place, with access on demand

Everything a team needs to stop secrets living in spreadsheets, chat, and code, and to recover in minutes when something leaks.

Secrets

Group secrets by team or project and decide who can see or change them. Each secret is locked with its own key, so a leak of one tells an attacker nothing about the rest.

  • Each secret locked with its own key
  • Access by team, role, or project
  • Secret names kept private, even in logs
  • Full history of every change
  • Optional expiry with automatic clean-up
  • No spreadsheets, no shared notes, no secrets in code
app.aker.tech/stashes/platform
prod-database
v7 · rotated 2d ago
billing-mssql
v3 · rotated 9d ago
session-cache
expires in 6d

Access on demand

Rather than passing a password around, Aker issues a value for each request: scoped to that person and expiring on its own. Database and cache integrations are included, so teams keep the tools they already use.

  • Temporary credentials, issued per request
  • Scope limited to what the request needs
  • Values expire without anyone remembering to revoke
  • Rotate the underlying value in seconds, rules untouched
  • Temporary logins for Postgres, MySQL, and SQL Server
  • Generated values for demos, tests, and honeypot traps
app.aker.tech/stashes/platform/secrets/prod-database
Access rules first match wins
role is contractor pgsql · read only
team is platform pgsql · narrow ttl
user.id is any pgsql · 24h
Redis cache wraps pgsql
key = pg:{user.id} cache · 5m

Access that fits your organisation

Sign in with Google or passwordless email. Access follows team and role, so joining or leaving a project never leaves a password behind.

  • Google sign-in and passwordless email links
  • A personal workspace for every user
  • Teams and roles per organisation
  • Separate credentials for systems and bots
  • Sessions the browser can't read
  • No shared logins, no passwords in chat

Access follows the person

Sign-in decides who you are and what you may reach. That decision is made for you and can't be claimed by the requester.

Nothing sensitive in the browser

Sessions are held where the browser can't reach them, so tokens never end up in links, logs, or page content.

Rotation without the panic

Rotating a secret takes seconds. The systems that use it receive the new value on their next request, so nothing is redeployed and no one has to coordinate.

  • Rotate one secret or every secret at once
  • No downtime and no code changes
  • Keys cannot be exported or copied
  • Every rotation recorded
  • Recovery in minutes after a suspected leak

Nothing to redeploy

New values take effect immediately. Systems holding an old one pick up the replacement on their next request.

Every use attributed

Each read, rotation, and expiry records who, what, and when, ready for a review or an auditor.

Works with your systems

Bots and automated jobs get their own credentials, with the same scoping and expiry as people. Every machine access is recorded alongside human ones.

  • API access for every secret and project
  • Separate credentials for machines
  • Same rules and expiry as people
  • Access for AI assistants (planned)
fetch a scoped credential
$ curl -X POST $AKER_API/v1/stashes/$STASH/secrets/lookup \ -H "Authorization: Bearer $TOKEN" \ -d '{"name":"prod-database","request":{"role":"contractor"}}' { "action": "pgsql", "value": "postgres://aker_7f3a:••••@db.internal:5432/analytics", "expiresAt": "2026-09-25T16:33:00Z" } $ curl -X POST $AKER_API/v1/stashes/$STASH/secrets/$ID/rotate { "version": 7, "rotatedAt": "2026-09-25T16:32:11Z" }

See it in action

See how a request gets only the access it needs, and how fast you can rotate when something leaks.

Open the app