Developers & API
Identities

Scoped keys, and non-human identities for automation.

Create scoped API keys — live or test — with optional IP and environment restrictions and an expiry. Give automation its own service account with its own keys, so a person leaving never quietly breaks a pipeline.

Keys are scoped to exactly what they should touch, issued as live or test, and can be pinned to an IP range or an environment and given an expiry. Give automation a service account — a non-human identity that owns its own keys — so a pipeline outlives the person who set it up. A key can never carry more access than its owner, so least-privilege is the default rather than something you remember to configure.

  • Scoped keys, live or test with IP / environment restrictions and expiry.
  • Service accounts — non-human identities that own their own keys.
  • Least privilege — a key never carries more access than its owner.
api keys · acme
ci-deploy · sk_live_…7f3c
scopes: monitors:write · expires in 89d
Live
staging-smoke · sk_test_…a1b2
IP: 203.0.113.0/24 · env: staging
Test
svc: orders-bot
service account · 2 keys
Service acct