Skip to content

Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.

docs(agent-vault): fit into product model (#8178)

Adrian Kahali0a0c37894382
diff --git a/docs/docs.json b/docs/docs.json
index 911974313e..009d54b39e 100644
--- a/docs/docs.json
+++ b/docs/docs.json
@@ -57,7 +57,8 @@
"documentation/getting-started/choose-a-product/secret-scanning",
"documentation/getting-started/choose-a-product/pki",
"documentation/getting-started/choose-a-product/kms",
- "documentation/getting-started/choose-a-product/pam"
+ "documentation/getting-started/choose-a-product/pam",
+ "documentation/getting-started/choose-a-product/agent-vault"
]
},
{
diff --git a/docs/documentation/getting-started/choose-a-product/agent-vault.mdx b/docs/documentation/getting-started/choose-a-product/agent-vault.mdx
new file mode 100644
index 0000000000..04819a46ac
--- /dev/null
+++ b/docs/documentation/getting-started/choose-a-product/agent-vault.mdx
@@ -0,0 +1,21 @@
+---
+title: "Run AI agents securely"
+sidebarTitle: "Run AI agents securely"
+description: "Give AI agents access to the services they need without ever handing them a real credential."
+---
+
+Infisical Agent Vault is an access layer for AI agents. Agents route their API calls through a proxy that attaches the real credentials on the way out, so the agent itself never holds them. If a [prompt injection](https://en.wikipedia.org/wiki/Prompt_injection) tricks the agent into revealing a credential, there's nothing there to reveal.
+
+<Warning>
+ Agent Vault is in preview and subject to change. We don't currently recommend it for production use.
+</Warning>
+
+<Card title="Agent Vault docs" icon="vault" href="/documentation/platform/agent-vault/overview">
+ Access bundles, services, sessions, proxies, and access control.
+</Card>
+
+## Why brokering access matters for agents
+
+Traditional secrets management involves returning credentials back to applications and services. This isn't suitable for AI agents because a credential in the agent's environment can leak in many ways. An agent may inadvertently include it in a log line, a message, or a tool call it makes, or an attacker may deliberately extract it through [prompt injection](https://en.wikipedia.org/wiki/Prompt_injection).
+
+Infisical Agent Vault solves this by brokering credentials using a proxy at the network boundary. The proxy attaches real credentials to services you've allowed, and only until the session expires (or you revoke it).
\ No newline at end of file
diff --git a/docs/documentation/getting-started/introduction.mdx b/docs/documentation/getting-started/introduction.mdx
index e1e6656981..a979f21cfd 100644
--- a/docs/documentation/getting-started/introduction.mdx
+++ b/docs/documentation/getting-started/introduction.mdx
@@ -4,9 +4,9 @@ sidebarTitle: "What is Infisical?"
description: "The open source platform for managing secrets, certificates, and secure infrastructure access."
---
-[Infisical](https://infisical.com) is the [open source](https://github.com/Infisical/infisical), all-in-one platform for secrets, certificates, and privileged access management.
+[Infisical](https://infisical.com) is the [open source](https://github.com/Infisical/infisical), all-in-one platform for secrets, certificates, privileged access, and AI agent access.
-It provides modern security workflows — including secrets rotation, dynamic credentials, access approvals, and privileged access management — all within one platform designed for developers, infrastructure, and security teams.
+It provides modern security workflows — including secrets rotation, dynamic credentials, access approvals, privileged access management, and credential-free access for AI agents — all within one platform designed for developers, infrastructure, and security teams.
Start managing secrets securely with [Infisical Cloud](https://app.infisical.com) or learn how to [host Infisical](/self-hosting/overview) yourself.
@@ -27,35 +27,39 @@ Infisical addresses this challenge by providing an all-in-one platform and workf
- Automate X.509 certificate issuance and renewal.
- Govern privileged access to infrastructure with policy-driven sessions.
- Encrypt and decrypt sensitive data with centralized key control.
+- Broker outbound API access for AI agents so they never hold real credentials.
- Audit every access, credential use, and change.
Infisical is designed to integrate cleanly into your stack—improving security without adding complexity.
## What can you do with Infisical?
-Infisical consists of five integrated products, each addressing a specific aspect of infrastructure security. The cards below link to an introduction to each product and the tasks it can be used for.
+Infisical consists of six integrated products, each addressing a specific aspect of infrastructure security. The cards below link to an introduction to each product and the tasks it can be used for.
<CardGroup cols={2}>
- <Card title="Manage secrets" icon="vault" href="/documentation/getting-started/choose-a-product/secrets-management/overview">
+ <Card title="Manage secrets" icon="key" href="/documentation/getting-started/choose-a-product/secrets-management/overview">
Store, deliver, and rotate credentials used by applications, and broker access to services for AI agents.
</Card>
<Card title="Detect leaked secrets" icon="radar" href="/documentation/getting-started/choose-a-product/secret-scanning">
Scan source code and developer systems to identify credentials that have been exposed.
</Card>
- <Card title="Manage certificates" icon="file-badge" href="/documentation/getting-started/choose-a-product/pki">
+ <Card title="Manage certificates" icon="file-key" href="/documentation/getting-started/choose-a-product/pki">
Issue and automatically renew TLS, mTLS, and device certificates from internal or external certificate authorities.
</Card>
- <Card title="Manage cryptographic keys" icon="key" href="/documentation/getting-started/choose-a-product/kms">
+ <Card title="Manage cryptographic keys" icon="lock" href="/documentation/getting-started/choose-a-product/kms">
Perform encryption, decryption, and signing operations using keys stored within Infisical.
</Card>
- <Card title="Manage privileged access" icon="shield-user" href="/documentation/getting-started/choose-a-product/pam">
+ <Card title="Manage privileged access" icon="users" href="/documentation/getting-started/choose-a-product/pam">
Give users and AI agents session-based access to databases and servers without providing them with the underlying credentials.
</Card>
+ <Card title="Run AI agents securely" icon="vault" href="/documentation/getting-started/choose-a-product/agent-vault">
+ Broker outbound API access for AI agents so they call services under stored credentials they never see.
+ </Card>
</CardGroup>
## How the platform fits together
-All five products share the same underlying platform. This platform includes organizations, projects, identities, deployment configuration, and integrations with external services.
+All six products share the same underlying platform. This platform includes organizations, projects, identities, deployment configuration, and integrations with external services.
<CardGroup cols={2}>
<Card title="Account structure" icon="building" href="/documentation/getting-started/concepts/platform-hierarchy">
diff --git a/docs/documentation/getting-started/quickstarts.mdx b/docs/documentation/getting-started/quickstarts.mdx
index 5ab2fd7fec..9af0209cff 100644
--- a/docs/documentation/getting-started/quickstarts.mdx
+++ b/docs/documentation/getting-started/quickstarts.mdx
@@ -19,6 +19,7 @@ mode: "frame"
<a href="#certificate-management" className="qs-index__jump-chip qs-index__jump-chip--certificates">Certificates</a>
<a href="#key-management" className="qs-index__jump-chip qs-index__jump-chip--kms">Key Management</a>
<a href="#privileged-access-management" className="qs-index__jump-chip qs-index__jump-chip--pam">Privileged Access</a>
+ <a href="#agent-vault" className="qs-index__jump-chip qs-index__jump-chip--agent-vault">Agent Vault</a>
</div>
<div className="qs-index__jump-links">
<a href="#identity-and-access" className="qs-index__jump-chip qs-index__jump-chip--identity">Identity</a>
@@ -102,6 +103,20 @@ mode: "frame"
</section>
+<section className="qs-index__section qs-index__section--agent-vault">
+
+<h2 id="agent-vault"><a href="/documentation/platform/agent-vault/overview" className="qs-index__section-link">Agent Vault<svg className="qs-index__section-arrow" width="15" height="15" viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" aria-hidden="true"><path d="m9 18 6-6-6-6" /></svg></a></h2>
+
+<p className="qs-index__section-desc">Let AI agents call third-party APIs through a proxy that attaches stored credentials on the way out, so the agent never sees them.</p>
+
+| Quickstart | Description |
+| --- | --- |
+| [Launch an agent through Agent Vault](/documentation/platform/agent-vault/quickstart) | Run an AI agent that reaches external APIs without holding real credentials. |
+| [Build an access bundle](/documentation/platform/agent-vault/access-bundles) | Define the set of services an agent session can reach. |
+| [Add a service to an access bundle](/documentation/platform/agent-vault/services) | Store credentials for an external API the proxy will call on the agent's behalf. |
+
+</section>
+
<section className="qs-index__section qs-index__section--identity">
<h2 id="identity-and-access"><a href="/documentation/platform/identities/overview" className="qs-index__section-link">Identity and access<svg className="qs-index__section-arrow" width="15" height="15" viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" aria-hidden="true"><path d="m9 18 6-6-6-6" /></svg></a></h2>
diff --git a/docs/documentation/guides/governance-models.mdx b/docs/documentation/guides/governance-models.mdx
index 84c154f6e6..0886aa93d5 100644
--- a/docs/documentation/guides/governance-models.mdx
+++ b/docs/documentation/guides/governance-models.mdx
@@ -9,7 +9,7 @@ Organizations adopt different approaches to secrets management governance based
This guide covers how to configure Infisical for different governance approaches and what tradeoffs to consider.
<Note>
-Infisical spans several products: [Secrets Management](/documentation/platform/secrets-mgmt/overview), [Certificate Manager](/documentation/platform/pki/overview), [KMS](/documentation/platform/kms/overview), [Secret Scanning](/documentation/platform/secret-scanning/overview), and [Privileged Access Management](/documentation/platform/pam/overview). This guide focuses on Secrets Management, but the same governance foundations apply across all of them: organization structure, authentication and identity, access control, approval workflows, and audit.
+Infisical spans several products: [Secrets Management](/documentation/platform/secrets-mgmt/overview), [Certificate Manager](/documentation/platform/pki/overview), [KMS](/documentation/platform/kms/overview), [Secret Scanning](/documentation/platform/secret-scanning/overview), [Privileged Access Management](/documentation/platform/pam/overview), and [Agent Vault](/documentation/platform/agent-vault/overview). This guide focuses on Secrets Management, but the same governance foundations apply across all of them: organization structure, authentication and identity, access control, approval workflows, and audit.
</Note>
## Understanding the spectrum
diff --git a/docs/documentation/guides/organization-structure.mdx b/docs/documentation/guides/organization-structure.mdx
index 0a6a724c2c..1945235846 100644
--- a/docs/documentation/guides/organization-structure.mdx
+++ b/docs/documentation/guides/organization-structure.mdx
@@ -49,9 +49,10 @@ For detailed information on resource inheritance, project ownership, and enterpr
- **[KMS](/documentation/platform/kms/overview)**: Generate, store, and use cryptographic keys to encrypt, decrypt, sign, and verify against managed CMKs.
- **[Secret Scanning](/documentation/platform/secret-scanning/overview)**: Continuously scan repositories, builds, and runtime artifacts for leaked secrets and misconfigurations.
- **[Privileged Access Manager](/documentation/platform/pam/overview)**: Connect to databases and servers securely with session brokering, recording, and credential vaulting.
+ - **[Agent Vault](/documentation/platform/agent-vault/overview)**: Broker outbound API calls from AI agents through a proxy so agents never hold real credentials.
- **How Products Are Structured**: Products differ in how they organize work, so not everything is project-based:
- **Secrets Management**, **KMS**, and **Secret Scanning** organize their resources into one or more **[projects](/documentation/platform/project)** (see below).
- - **Certificate Manager** and **Privileged Access Manager** operate at the organization level as a single workspace, rather than a list of separate projects.
+ - **Certificate Manager**, **Privileged Access Manager**, and **Agent Vault** operate at the organization level as a single workspace, rather than a list of separate projects.
### 2.1 Projects
diff --git a/docs/index.mdx b/docs/index.mdx
index 1faa280615..b2897b0891 100644
--- a/docs/index.mdx
+++ b/docs/index.mdx
@@ -128,6 +128,19 @@ import { HomeHero, HomeButton, HomeSection, HomeGrid, HomeCard, HomeStack, HomeS
>
Encrypt and decrypt sensitive data with centrally managed keys.
</HomeCard>
+ <HomeCard
+ title="Agent Vault"
+ href="/documentation/platform/agent-vault/overview"
+ icon="shield-keyhole"
+ product="agent-vault"
+ links={[
+ { label: "Quickstart", href: "/documentation/platform/agent-vault/quickstart" },
+ { label: "Access bundles", href: "/documentation/platform/agent-vault/access-bundles" },
+ { label: "Sessions", href: "/documentation/platform/agent-vault/sessions" }
+ ]}
+ >
+ Run AI agents with the access they need to do work, without giving them the underlying credentials.
+ </HomeCard>
</HomeGrid>
</HomeSection>
diff --git a/docs/snippets/home.jsx b/docs/snippets/home.jsx
index b30d681ca8..38f2d9808d 100644
--- a/docs/snippets/home.jsx
+++ b/docs/snippets/home.jsx
@@ -280,6 +280,13 @@ export const HomeCard = ({
<path d="m16 18 6-6-6-6" />
<path d="m8 6-6 6 6 6" />
</>
+ ),
+ "shield-keyhole": (
+ <>
+ <path d="M12 22s8-4 8-10V5l-8-3-8 3v7c0 6 8 10 8 10z" />
+ <circle cx="12" cy="10" r="1.5" />
+ <path d="M12 11.5v3" />
+ </>
)
};
diff --git a/docs/style.css b/docs/style.css
index ad6f3346c8..a00743ef1c 100644
--- a/docs/style.css
+++ b/docs/style.css
@@ -88,6 +88,7 @@
.qs-index__jump-chip--certificates { --qs-chip-color: #a16207; }
.qs-index__jump-chip--kms { --qs-chip-color: #109e7a; }
.qs-index__jump-chip--pam { --qs-chip-color: #dc2626; }
+.qs-index__jump-chip--agent-vault { --qs-chip-color: #5f7000; }
.qs-index__jump-chip--identity { --qs-chip-color: #cfcfcf; }
.qs-index__jump-chip--networking { --qs-chip-color: #cfcfcf; }
.qs-index__jump-chip--self-hosting { --qs-chip-color: #cfcfcf; }
@@ -117,6 +118,7 @@
.dark .qs-index__jump-chip--certificates { --qs-chip-color: #f5c451; }
.dark .qs-index__jump-chip--kms { --qs-chip-color: #34edbf; }
.dark .qs-index__jump-chip--pam { --qs-chip-color: #ff8a85; }
+.dark .qs-index__jump-chip--agent-vault { --qs-chip-color: #a1d434; }
.dark .qs-index__jump-chip--identity { --qs-chip-color: #3a3f47; }
.dark .qs-index__jump-chip--networking { --qs-chip-color: #3a3f47; }
.dark .qs-index__jump-chip--self-hosting { --qs-chip-color: #3a3f47; }
@@ -135,6 +137,7 @@
.qs-index__section--certificates { --qs-accent: #a16207; }
.qs-index__section--kms { --qs-accent: #109e7a; }
.qs-index__section--pam { --qs-accent: #dc2626; }
+.qs-index__section--agent-vault { --qs-accent: #5f7000; }
.qs-index__section--identity,
.qs-index__section--networking,
.qs-index__section--self-hosting {
@@ -260,6 +263,7 @@
.dark .qs-index__section--certificates { --qs-accent: #f5c451; }
.dark .qs-index__section--kms { --qs-accent: #34edbf; }
.dark .qs-index__section--pam { --qs-accent: #ff8a85; }
+.dark .qs-index__section--agent-vault { --qs-accent: #a1d434; }
.dark .qs-index__section--identity,
.dark .qs-index__section--networking,
.dark .qs-index__section--self-hosting {
@@ -864,8 +868,7 @@ a.ifx-steps__label:hover {
display: grid;
grid-template-columns: minmax(0, 1fr);
gap: 1px;
- border: 1px solid #ebebeb;
- background-color: #ebebeb;
+ background-color: transparent;
}
.ifx-card {
@@ -876,6 +879,7 @@ a.ifx-steps__label:hover {
flex-direction: column;
padding: 1.5rem;
background-color: #fbfbfa;
+ outline: 1px solid #ebebeb;
text-decoration: none;
transition: background-color 0.2s, box-shadow 0.2s;
}
@@ -905,6 +909,11 @@ a.ifx-steps__label:hover {
--ifx-accent: #109e7a;
}
+.ifx-card--agent-vault {
+ --ifx-ink: #5f7000;
+ --ifx-accent: #5f7000;
+}
+
.ifx-card__links {
display: flex;
flex-direction: column;
@@ -1040,13 +1049,13 @@ a.ifx-card__title:hover .ifx-card__chevron {
}
.dark .ifx-grid {
- border-color: #1e1f24;
- background-color: #1e1f24;
+ background-color: transparent;
}
.dark .ifx-card {
--ifx-ink: #707174;
background-color: #101114;
+ outline-color: #1e1f24;
}
.dark .ifx-card--secrets {
@@ -1074,6 +1083,11 @@ a.ifx-card__title:hover .ifx-card__chevron {
--ifx-accent: #34edbf;
}
+.dark .ifx-card--agent-vault {
+ --ifx-ink: #a1d434;
+ --ifx-accent: #a1d434;
+}
+
.dark .ifx-card__title {
color: #ebebeb;
}