<!-- Agent-readable view of https://infisical.com/platform/secrets-management -->
<!-- Site index: https://infisical.com/llms.txt -->

# Secrets Management

Credentials like API keys, database URLs, and tokens live in Infisical and are fetched at runtime,
so nothing sensitive sits in a `.env` file, a CI variable, or git history.

For AI agents, Agent Proxy lets the agent make authenticated calls without ever receiving the
credential, by proxying outbound traffic and replacing a dummy credential with the real one.

Unlike legacy secrets managers, Infisical runs on Postgres and does not need a dedicated team to operate. There is no unseal ritual, no storage backend to choose, and upgrades are ordinary deploys. The work those tools leave as manual runbooks (rotating credentials, provisioning access, revoking it, copying values into each platform that needs them) is automated here.

## How you use it

Pick whichever interface matches where the credential is needed. They all read the same projects and obey the same access controls, so mixing them is normal.

| Interface               | Use it when                                                  | Entry point                                        |
|-------------------------|--------------------------------------------------------------|----------------------------------------------------|
| **CLI**                 | Local development, CI jobs, containers. The default, and needs no code change | `infisical run -- npm start`                       |
| **SDKs**                | The application should fetch its own secrets at boot         | 9 languages                                        |
| **Kubernetes operator** | Workloads want native `Secret` objects or mounted files      | `InfisicalStaticSecret` CRD                        |
| **Terraform provider**  | Secrets and Infisical resources are managed as code          | Ephemeral resources, so values never land in state |
| **Agent Proxy**         | An AI agent must make authenticated calls without ever holding the key | `HTTPS_PROXY`                                      |
| **Secret syncs**        | Another platform insists on holding its own copy             | Pushes to 40+ destinations                         |
| **REST API**            | Anything the above does not cover                            |                                                    |

## What you can do with it

**Stop storing secrets on disk.** `infisical run -- <command>` injects secrets as environment
variables into the process, so they exist only in memory for the life of the command. Usually a
one-line change to a `package.json` script or a Dockerfile `CMD`, with no application code touched.
[Secrets delivery](https://infisical.com/docs/documentation/platform/secrets-mgmt/concepts/secrets-delivery): every delivery mechanism and when to use each.

**Give every workload its own revocable identity.** A machine identity is a non-human principal that authenticates CI jobs, containers, and agents with no person present. Native methods (AWS, GCP, Azure, Kubernetes, OIDC) verify the workload's own platform identity so there is no long-lived secret tostore; Universal Auth is the portable client ID and secret fallback for anywhere else. [Machine identities](https://infisical.com/docs/documentation/platform/identities/machine-identities): auth methods, scoping, and token lifetimes.

**Stop onboarding people by hand.** Projects, environments, and folder paths mirror how teams already work, so a new service or engineer inherits the right access instead of waiting on a ticket. Secret referencing and imports mean shared values live in one place rather than being copied per environment.
[Core concepts](https://infisical.com/docs/documentation/platform/secrets-mgmt/concepts/secrets-mgmt): projects, environments, folders, and references.

**Undo mistakes.** Every change is versioned and a folder rolls back to any previous snapshot, so a
bad edit to a production secret is a revert rather than an incident.

**Remove long-lived credentials entirely.** Dynamic secrets mint a short-lived credential on demand that expires by itself, so there is no durable value to leak and nobody has to remember to clean it up.
[Dynamic secrets](https://infisical.com/docs/documentation/platform/dynamic-secrets/overview): supported providers, lease TTLs, and revocation.

**Rotate what cannot be short-lived.** Rotation policies regenerate credentials on a schedule automatically. Most providers use a dual-phase overlap, where the previous value stays valid for one more cycle, so consumers do not break mid-rotation.
[Secret rotation](https://infisical.com/docs/documentation/platform/secret-rotation/overview): providers and the rotation model for each.

**Control who can read what.** Role-based and attribute-based access control scope access by role, project, environment, and folder path for humans and machines alike, with custom roles, grants that expire on their own, and approval workflows on changes.
[Access controls](https://infisical.com/docs/documentation/platform/access-controls/overview): roles, attributes, additional privileges, and temporary access.

**Reach private infrastructure without opening ports.** A gateway is a lightweight relay you deploy inside your network that connects outbound only, so Infisical can rotate credentials on and mint dynamic secrets for private databases without a firewall change request. Advanced and Enterprise. [Gateways](https://infisical.com/docs/documentation/platform/gateways/overview): deployment, pools, and network architecture.

**Hold your own encryption keys.** Secrets are encrypted under a multilayer key hierarchy with
separate organization- and project-level data keys, so projects are cryptographically isolated. The root key can live in an external KMS (AWS KMS, GCP KMS) or an HSM you control, which is
usually the real requirement behind "we need to hold our own keys. [KMS configuration](https://infisical.com/docs/documentation/platform/kms-configuration/overview): internal KMS, external KMS, and HSM backing.

**Know when something leaks.** Honey tokens are decoy credentials that fire an alert the moment
anyone tries to use them, and audit logs record every access.[Audit logs](https://infisical.com/docs/documentation/platform/audit-logs): event coverage, retention, and SIEM streaming.

## Agent Proxy

Agent Proxy is Infisical’s credential broker. It’s a MITM proxy that intercepts egress and appends real credentials to the request. The agent only holds placeholders.

**The problem.** A credential AI can read is a credential it can leak. Prompt injection from a page it reads, a poisoned tool result, or a compromised dependency can all leak credentials.

**What it does.** The credential stays in Infisical. Infisical runs a forward proxy in the agent’s environment with the standard `HTTPS_PROXY` variable. The agent sends a placeholder, the
proxy swaps in the real credential at the network boundary, and the request goes out authenticated.

The value never enters the agent's context, environment, filesystem, or transcript, so nothing the
agent is told can leak a secret it never had.

CLI example:

```bash
infisical secrets agent-proxy run --projectId=<id> --env=dev --path=/coding-agent -- claude
```

Any program honoring `HTTPS_PROXY` works, which means Agent Proxy works on nearly every environment and agent harness, including Claude Code, Codex, OpenClaw, Pi, and others. No SDK and code change is required in the agent. Targets are anything that requires authentication: third-party APIs, CLIs, MCPs, and other tools. They’re authenticated with a header or bearer token or basic auth: There are 30+ presets for tools like Slack, GitHub, Anthropic, and OpenAI, but any service can be configured. Every brokered request is logged, so you can see what an agent actually called.

Included from **Free** up for static secrets; brokering a **dynamic** secret needs Advanced or
Enterprise, where dynamic secrets start.

[Agent Proxy](https://infisical.com/docs/documentation/platform/agent-proxy/overview): proxied services, deployment modes, sandbox behavior, and activity logs.

[ai-agents.md](https://infisical.com/ai-agents.md): everything Infisical does for AI agents, including how Agent Proxy and brokered PAM sessions compose in one agent session.

## Getting started

[Deliver your first secret](https://infisical.com/docs/documentation/platform/secrets-mgmt/quick-starts/deliver-first-secret): the equivalent quickstart for a human.

## Pricing

Billed per identity, counting human users plus the machine identities your workloads authenticate as. Free covers 5 identities. The features gated by plan are dynamic secrets, rotation, gateways, SSO enforcement, and audit retention.

[pricing.md](https://infisical.com/pricing.md): prices, plan contents, and which features sit at which tier.
[Talk to an expert](https://infisical.com/talk-to-us) to find out more.

## Where it works

Complete lists as of this page's last update. The docs are authoritative if something is missing.

### App connections

Authenticate Infisical to a platform once, then reuse that connection for syncs, rotations, and
dynamic secrets. [App connections](https://infisical.com/docs/integrations/app-connections)

- **Cloud:** AWS, GCP, Azure App Configuration, Azure Client Secrets, Azure DevOps, Azure DNS, Azure Entra ID, Azure Key Vault, OCI, DigitalOcean, Fly.io, OVH Cloud
- **Databases and data:** PostgreSQL, MySQL, Microsoft SQL Server, MongoDB, OracleDB, Redis, Snowflake, Databricks, Convex, Supabase, Hasura Cloud, dbt
- **AI providers:** Anthropic, OpenAI, OpenRouter, LiteLLM, Fireworks, Devin, Ona
- **CI/CD and DevOps:** GitHub, GitLab, Bitbucket, CircleCI, TeamCity, Travis CI, Azure DevOps, Terraform Cloud, Spacelift, Octopus Deploy, Rundeck, Windmill, Trigger.dev, Camunda, Chef, Humanitec, Laravel Forge
- **Hosting and PaaS:** Vercel, Netlify, Heroku, Render, Railway, Northflank, Qovery, Cloud 66, DigitalOcean
- **Identity:** Okta, Auth0, LDAP, Azure Entra ID, Salesforce, ServiceNow
- **Other secret stores:** HashiCorp Vault, 1Password, Doppler, another Infisical instance
- **PKI and network devices:** Microsoft ADCS, Azure ADCS, DigiCert, GoDaddy, Venafi, Venafi TPP, F5 BIG-IP, NetScaler, Kemp LoadMaster, Nutanix Prism Central, Microsoft Intune
- **Monitoring:** Datadog, Checkly, Zabbix
- **Infrastructure access:** SSH, SMB, Windows (WinRM)
- **Networking:** Cloudflare, DNS Made Easy

### Secret syncs (Infisical to a third party)

Push secrets outward and keep the destination current as values change.

AWS Secrets Manager, AWS Parameter Store, GCP Secret Manager, Azure Key Vault, Azure App Configuration, Azure DevOps, Azure Entra ID (SCIM), OCI Vault, HashiCorp Vault, 1Password, GitHub, GitLab, Bitbucket, CircleCI, TeamCity, Travis CI, Terraform Cloud, Spacelift, Octopus Deploy, Rundeck, Windmill, Trigger.dev, Camunda, Chef, Humanitec, Vercel, Netlify, Heroku, Render, Railway, Northflank, Qovery, Cloud 66, Laravel Forge, Fly.io, DigitalOcean App Platform, Cloudflare Pages, Cloudflare Workers, Databricks, Snowflake, Supabase, Hasura Cloud, Checkly, Zabbix, Devin, Ona, OVH Cloud, another Infisical instance

### Secret rotation

Regenerate a credential on a schedule. Below is a selection of popular rotations offered, with many more secret rotations available. Full list in: [Secret rotations](https://infisical.com/docs/integrations/secret-rotations)

- **Databases:** PostgreSQL, MySQL, Microsoft SQL Server, MongoDB, OracleDB, Redis, Snowflake (user key pair)
- **Cloud and identity:** AWS IAM user, Azure client secret, Okta client secret, Auth0 client secret, LDAP password, Salesforce OAuth credentials
- **AI providers:** OpenAI service account, OpenRouter API key, LiteLLM API key, Fireworks API key
- **Infrastructure:** Windows local account, Unix/Linux local account, HP iLO local account
- **Other services:** Cloudflare API token, Cloudflare R2 access key, Datadog API key, Datadog application key, Databricks service principal secret, dbt service token, Convex access key, Supabase API key

### Dynamic secrets

Mint a short-lived credential on demand that expires by itself. [Dynamic secrets](https://infisical.com/docs/integrations/dynamic-secrets)

- **Databases:** PostgreSQL, MySQL, Microsoft SQL Server, Oracle, MongoDB, MongoDB Atlas, Redis, AWS ElastiCache, AWS MemoryDB, Azure SQL Database, Cassandra, ClickHouse, Couchbase, Elasticsearch, Milvus, RabbitMQ, SAP ASE, SAP HANA, Snowflake, Vertica
- **Cloud and identity:** AWS IAM, GCP IAM, Azure Entra ID, LDAP, GitHub, Kubernetes, Tailscale, IBM API Connect
- **Other:** SSH, TOTP

### Platforms and runtimes

Deliver secrets into the runtime that needs them. [All integrations](https://infisical.com/docs/integrations/all)

- **Runtimes:** Kubernetes, Docker, Amazon ECS, AWS Lambda, Ansible, Apache Airflow, PM2
- **Kubernetes operator:** `InfisicalStaticSecret`, `InfisicalDynamicSecret`, `InfisicalPushSecret`, `InfisicalConnection`, and `InfisicalAuth` CRDs, plus a CSI provider and an agent injector
- **Delivery agents:** Infisical Agent, for platforms with no native operator, which is how ECS works; Infisical Proxy

### Frameworks

Infisical has native integrations for various development [Frameworks](https://infisical.com/docs/integrations/frameworks), including:

Next.js, React, Vue, Nuxt, SvelteKit, Remix, Gatsby, Vite, Express, NestJS, Django, Flask, Rails, Laravel, Spring Boot (Maven), .NET, Fiber, Terraform, Pulumi, Packer, Ab Initio

### SDKs

Infisical [SDKs](https://infisical.com/docs/sdks/overview)are the easiest way to get secrets into your application on demand in the most popular programming languages:

Node.js, Python, Go, Java, .NET, Ruby, PHP, Rust, C++

## Docs

[Secrets Management documentation](https://infisical.com/docs/documentation/platform/secrets-mgmt/overview): full product reference.