Skip to content

Application, API and machine identity

Machine and Workload Identity

Identity for software, not just people.

Cryptographic identities for services, background jobs, containers, workloads and non-human principals.

In practice

What this service does.

Authenticate the systems behind your systems. Establish clear workload identities so applications, services and automated processes can identify themselves without depending on long-lived shared secrets.

Best for

Cloud-native software, infrastructure teams and automated operations

Integration detail — endpoints, token shapes, SDKs and the standards each flow follows — lives in the developer portal.

Capabilities

  • Service and workload registration
  • Short-lived workload identities and credential exchange
  • Public-key ownership and key rotation
  • Environment, tenant and deployment binding
  • Attestation and workload metadata when supported
  • Machine credential inventory and revocation

Capabilities describe what the service is built to do. Which of them a given tenant uses — and in which environments — is part of the configuration you choose.

Put Machine and Workload Identity to work.

Start with a development tenant and one application, or talk through the architecture first — tenancy, credential lifecycle and which parts stay in your own stack.

Packages and metered usage are set out on the pricing page; the figures themselves are agreed with our team against the services you need.