Early access is open. Stagd is free during the beta. Sign up
Concepts

Signing in as Stagd

How Stagd reaches your cloud without a stored key: it's an OpenID Connect issuer, and your cloud trusts it for your workspace.

Some integrations can sign in as Stagd instead of using a key you make and paste. Stagd then keeps no secret of yours, nothing expires, and you never rotate anything. Removing the trust in your cloud cuts Stagd off at once.

This works the way GitHub Actions, Vercel and Terraform Cloud reach clouds. Stagd is an OpenID Connect issuer. When it needs your storage, it signs a five-minute token saying “this is Stagd, acting for workspace X”. Your cloud checks the token against Stagd’s published keys, and swaps it for credentials of its own that last about an hour. It does so because you told it to trust Stagd’s issuer for that workspace. The token never leaves Stagd: your previews only get what they’d get anyway, such as their seed through Stagd.

What your cloud trusts

Issuer https://app.stagd.dev
Keys https://app.stagd.dev/.well-known/jwks.json
Subject org:<workspace id>, the same for every integration in the workspace

The subject uses your workspace’s id, never its slug, because slugs can change. Settings → General shows your workspace’s id, and the connect dialog the whole subject.

Each cloud also checks the token’s audience:

Cloud Audience
Azure (Microsoft Entra ID) api://AzureADTokenExchange
AWS sts.amazonaws.com
Google Cloud Your workload identity provider’s full name

Only Stagd’s own server signs tokens, and only for the workspace an integration belongs to, read from Stagd’s database. No request can ask Stagd to sign for another workspace.

Where you can use it

  • Azure Blob Storage: a federated credential on an app registration or managed identity.
  • Amazon S3: an IAM role that trusts Stagd’s OIDC provider.
  • Google Cloud Storage: a workload identity pool with Stagd as its provider.

Sign in as Stagd sets each one up, step by step.

Previews that fork a container or bucket still need a SAS token or access key for now: the credentials from an exchange end after about an hour, and a fork runs for longer.

Keys

Stagd signs with RSA keys (RS256), which every cloud accepts. A new key is published a day before Stagd signs with it, and an old one stays published for a day after. Clouds cache the keys for hours, so a rotation never breaks a trust you’ve set up.

For language models and agents: this page as Markdown, or every page through llms.txt.