Secrets

Secrets keeps passwords, tokens and keys encrypted under your own KMS keys and hands them to your apps and workflows by name: a Default value with an override per environment, a version history with rollback, grants per consumer and repository, an access log of every read, and values synced from 1Password or HashiCorp Vault / OpenBao.

Get started

  • What is Secrets?

    Secrets keeps passwords, tokens and keys encrypted under one of your KMS keys and hands them to your apps and workflows by name, never in your code.

  • Get started with Secrets

    Store a secret, let deployed apps read it, read it back yourself, and delete it again, in about ten minutes.

  • Secrets and versions

    What a secret is made of, how its versions work, and which secrets the platform writes for you.

Popular tasks

  • Create a secret

    Store a value as a secret, encrypted under one of your KMS keys, as the Default or for one environment.

  • Grant a consumer access to a secret

    Let workflow jobs, app deployments or another part of the platform read a secret, for every repository or one, with or without an expiry, and revoke it again.

  • Use a secret in a workflow

    Hand a secret to one workflow job as ${{ secrets.NAME }}, for one repository only.

  • Connect 1Password

    Connect a 1Password service account as a source, so that op:// references become synced secrets.

Operate and secure

  • Security in Secrets

    Who may do what (IAM), what is recorded, and how a secret is protected.

  • Monitoring Secrets

    Where to see rotation due dates, sync failures, key problems and who has read a value.

  • What runs where

    Where a secret's value is decrypted, who it is handed to, what the platform records, and what happens when a source or a key fails.

Guides and references