Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.
TypeScript acmeagentsai-agentscertificate-managementdevsecopsenvironment-variableskubernetesopen-sourcepampkipostgresprivate-caprivileged-access-managementsecret-managementsecret-managersecretssecrets-managementsecuritysecurity-toolsvault
docs(get-started): overhaul get started section (#8098)
Adrian Kahali1c5b0dbe757c
diff --git a/docs/.vale/styles/config/vocabularies/Infisical/any-case/accept.txt b/docs/.vale/styles/config/vocabularies/Infisical/any-case/accept.txtindex 202b451fd9..f57989d1da 100644--- a/docs/.vale/styles/config/vocabularies/Infisical/any-case/accept.txt+++ b/docs/.vale/styles/config/vocabularies/Infisical/any-case/accept.txt@@ -285,6 +285,7 @@ I(?i)Realtime(?i)Secrets Management(?i)Certificate Management+(?i)Key Management(?i)Privileged Access Management(?i)Honey Token(?i)Honey Tokensdiff --git a/docs/docs.json b/docs/docs.jsonindex 0fd16d588a..267cfda33c 100644--- a/docs/docs.json+++ b/docs/docs.json@@ -42,23 +42,31 @@"tab": "Get started","pages": ["documentation/getting-started/overview",+ "documentation/getting-started/quickstarts","documentation/getting-started/introduction",+ "documentation/getting-started/set-up-with-ai",+ "documentation/platform/external-migrations/overview",+ "documentation/getting-started/concepts/deployment-models",{- "group": "Concepts",+ "group": "Use cases","pages": [- "documentation/getting-started/concepts/deployment-models",- "documentation/getting-started/concepts/platform-hierarchy",- "documentation/getting-started/concepts/platform-iam",- "documentation/getting-started/concepts/client-integrations",- "documentation/getting-started/concepts/audit-logs"+ "documentation/getting-started/choose-a-product/secrets-management/overview",+ "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"]},{- "group": "Migrate to Infisical",+ "group": "Understand the platform","pages": [- "documentation/platform/external-migrations/overview",- "documentation/platform/external-migrations/doppler",- "documentation/platform/external-migrations/vault"+ "documentation/getting-started/concepts/platform-hierarchy",+ "documentation/getting-started/concepts/platform-iam",+ "documentation/getting-started/concepts/audit-logs",+ "documentation/getting-started/concepts/app-connections",+ "documentation/getting-started/concepts/networking",+ "documentation/getting-started/concepts/internals",+ "documentation/getting-started/concepts/contributing"]}]@@ -87,7 +95,15 @@"documentation/platform/secrets-mgmt/concepts/approval-workflows"]},- "documentation/platform/secret-sharing"+ "documentation/platform/secret-sharing",+ {+ "group": "Migrate to Infisical",+ "root": "documentation/platform/secrets-mgmt/quick-starts/migrate",+ "pages": [+ "documentation/platform/external-migrations/doppler",+ "documentation/platform/external-migrations/vault"+ ]+ }]},{@@ -4675,6 +4691,10 @@}},"redirects": [+ {+ "source": "/ai/model-context-protocol",+ "destination": "/documentation/getting-started/set-up-with-ai"+ },{"source": "/integrations/platforms/docker-intro","destination": "/integrations/platforms/docker"diff --git a/docs/documentation/getting-started/choose-a-product/kms.mdx b/docs/documentation/getting-started/choose-a-product/kms.mdxnew file mode 100644index 0000000000..504e70764c--- /dev/null+++ b/docs/documentation/getting-started/choose-a-product/kms.mdx@@ -0,0 +1,43 @@+---+title: "Manage cryptographic keys"+sidebarTitle: "Manage cryptographic keys"+description: "Perform encryption, decryption, and signing operations using keys stored centrally in Infisical."+---++Infisical KMS is a key management service that stores cryptographic keys and performs cryptographic operations with them on behalf of applications. Applications reference a key by its identifier when calling the KMS API, so they never receive the key material directly.++<Card title="KMS docs" icon="key" href="/documentation/platform/kms/overview">+ Creating keys, encryption and decryption, signing and verification, and HSM integration.+</Card>++## Use cases++<CardGroup cols={2}>+ <Card title="Encrypt and decrypt with a KMS key" icon="lock" href="/documentation/platform/kms/overview">+ Encrypt sensitive data by reference to a key that never leaves Infisical.+ </Card>+ <Card title="Sign and verify with a KMS key" icon="signature" href="/documentation/platform/kms/overview">+ Sign payloads with an asymmetric key managed centrally, and verify signatures without holding the key.+ </Card>+ <Card title="Back the root key with an HSM" icon="microchip" href="/self-hosting/guides/hsm-integration">+ Use a hardware security module for the root key that protects data stored in Infisical.+ </Card>+</CardGroup>++## What is a key management service?++A key management service (KMS) is a system that stores cryptographic keys in a central location and provides an API through which applications can request cryptographic operations. Instead of storing a private key locally, an application stores a reference to the key and calls the KMS to perform operations such as encryption, decryption, or signing. Because the key material isn't stored on the application side, an application that has been compromised doesn't expose the key.++## Why manage keys centrally++Cryptographic keys require careful handling. If a key is lost or exposed, the data and systems that depend on it are also compromised. Rotating a key that is stored across many applications requires coordinating the rotation across every location that uses it. If a key is stored in a container image or on disk, every location that stores or transmits that image also stores the key.++A centralized key management service reduces these risks by keeping the key in a single location. Applications interact with the key through an API rather than storing it locally, so the key isn't present on application servers, in container images, or in configuration files. When a supported encrypt-decrypt key with Infisical-managed key material is rotated, applications continue to use the same reference and don't need to be updated.++## How Infisical does it++Infisical KMS stores cryptographic keys within the platform and provides an API for using them. Each key is created with an algorithm (for example, `AES-GCM-256` for symmetric encryption, or an asymmetric algorithm for signing) and a usage type, such as encrypt and decrypt, sign and verify, or generate and verify a message authentication code (MAC). To perform an operation, an application calls the KMS API with the key's identifier and the input payload, and Infisical returns the operation's result.++When a key is created, it can be configured so that its raw key material can't be exported. In this configuration, the key material remains inside Infisical regardless of a user's permissions. The root key that Infisical uses to protect platform data can itself be backed by a hardware security module ([HSM](/self-hosting/guides/hsm-integration)).++Infisical also uses its own KMS internally. Projects and the data within them are encrypted at rest using a key managed by Infisical, so the protections applied to customer-managed keys also apply to Infisical's own storage.diff --git a/docs/documentation/getting-started/choose-a-product/pam.mdx b/docs/documentation/getting-started/choose-a-product/pam.mdxnew file mode 100644index 0000000000..8abbe3318b--- /dev/null+++ b/docs/documentation/getting-started/choose-a-product/pam.mdx@@ -0,0 +1,44 @@+---+title: "Manage privileged access"+sidebarTitle: "Manage privileged access"+description: "Broker access to databases and servers so that users and applications don't receive the underlying credentials."+---++Infisical Privileged Access Management (PAM) brokers connections to systems such as databases and servers. When a user or application needs to access one of these systems, Infisical opens the connection using a credential stored within Infisical, without providing the credential to the requester. All sessions are recorded, and the credential isn't exposed at any point during the session.++<Card title="PAM docs" icon="user-shield" href="/documentation/platform/pam/overview">+ Templates, folders, and accounts; access control; AI agent workflows; and the Gateway architecture.+</Card>++## Use cases++<CardGroup cols={2}>+ <Card title="Broker access to a database" icon="database" href="/documentation/platform/pam/quick-starts/launch-first-session">+ Allow users to connect to PostgreSQL, MySQL, and other databases without providing them with the credential.+ </Card>+ <Card title="Broker access to a server" icon="server" href="/documentation/platform/pam/quick-starts/launch-first-session">+ Allow users to open SSH sessions to jump boxes and production servers under policy-gated, recorded sessions.+ </Card>+ <Card title="Give AI agents scoped access" icon="robot" href="/documentation/platform/pam/ai-agents/overview">+ Allow an AI agent to access infrastructure under the identity of the user who started it, or as its own machine identity.+ </Card>+ <Card title="Record and replay sessions" icon="film" href="/documentation/platform/pam/overview">+ Attribute every action to the identity that opened the session, and replay the session for later review.+ </Card>+</CardGroup>++## What is privileged access?++A privileged credential is a credential that grants access to a sensitive system, such as a production database, a shared administrator account on a server, or an administrator login to a web-based console. Privileged credentials are often used by multiple people or applications, and each use of the credential can have significant impact on the system it accesses. For these reasons, access to privileged credentials is typically subject to additional controls, such as logging and approval.++## Why broker privileged access++Without a system for brokering access, privileged credentials are typically shared between users. This is often done by storing credentials in a shared password manager, or by distributing them through messaging or documentation tools. When a credential is shared in this way, rotating it requires updating every location where it has been shared, auditing who has used it becomes difficult, and removing a person's access when they leave the team requires rotating the credential.++When access is brokered instead, the credential is stored in a single location and isn't distributed to users. To access a system, a user requests a session. Infisical opens a connection to the target system on the user's behalf and uses the stored credential to authenticate. The user doesn't see or hold the credential. Each session is recorded and attributed to the user or application that requested it.++## How Infisical does it++Infisical PAM organizes credentials into three types of resources: templates, folders, and accounts. A template defines the structure of a type of credential, a folder groups related credentials, and an account is a specific credential that can be used to access a system. To access a system, a user requests a session against an account they have been granted access to. Infisical opens a connection to the target system through a [Gateway](/documentation/platform/gateways/overview), and the account's credential is applied within that connection. The credential isn't sent to the user's client. Sessions are recorded and can be replayed for later review.++PAM sessions can be requested by users or by AI agents. A user connects through a browser or through the CLI. An [AI agent](/documentation/platform/pam/ai-agents/overview) can be configured to act as the user who started it, or to act as its own [machine identity](/documentation/platform/identities/machine-identities) with a distinct set of permissions. In both configurations, the credential is stored in Infisical, and every action is recorded in the audit log.diff --git a/docs/documentation/getting-started/choose-a-product/pki.mdx b/docs/documentation/getting-started/choose-a-product/pki.mdxnew file mode 100644index 0000000000..17d9d12e56--- /dev/null+++ b/docs/documentation/getting-started/choose-a-product/pki.mdx@@ -0,0 +1,54 @@+---+title: "Manage certificates"+sidebarTitle: "Manage certificates"+description: "Issue, distribute, and renew the X.509 certificates that authenticate services, devices, and code."+---++Infisical Certificate Management manages the lifecycle of X.509 certificates for an organization. This includes issuing certificates from certificate authorities, deploying them to services, tracking their expiration, and signing code with managed keys. It replaces manual processes such as running `openssl` scripts, tracking certificates in spreadsheets, and monitoring expiration by hand.++<Card title="Certificate Management docs" icon="file-certificate" href="/documentation/platform/pki/overview">+ Certificate authorities, issuance protocols, discovery, sync, alerting, and code signing.+</Card>++## Use cases++<CardGroup cols={2}>+ <Card title="Issue TLS and mTLS certificates" icon="certificate" href="/documentation/platform/pki/applications/overview">+ Issue certificates for web servers, service-to-service authentication, and device identity.+ </Card>+ <Card title="Enroll devices with ACME, EST, or SCEP" icon="mobile" href="/documentation/platform/pki/applications/enrollment-methods/overview">+ Issue certificates to devices using an enrollment protocol supported by the device or its management system.+ </Card>+ <Card title="Sync certificates to cloud destinations" icon="arrows-rotate" href="/documentation/platform/pki/applications/certificate-syncs/overview">+ Push issued certificates to destinations such as AWS ACM, Azure Key Vault, and Cloudflare.+ </Card>+ <Card title="Discover certificates already deployed" icon="radar" href="/documentation/platform/pki/discovery/overview">+ Scan infrastructure to identify certificates that were issued outside of Infisical and add them to the inventory.+ </Card>+ <Card title="Sign code with centralized keys" icon="file-signature" href="/documentation/platform/pki/code-signing/overview">+ Sign binaries, container images, and firmware using keys managed within Infisical.+ </Card>+ <Card title="Get alerts before certificates expire" icon="bell" href="/documentation/platform/pki/applications/alerting/overview">+ Send alerts through Slack, PagerDuty, or webhooks when a certificate approaches its expiration date.+ </Card>+</CardGroup>++## What is a certificate?++An X.509 certificate binds a public key to an identity, such as a domain, service, device, or person. The certificate is signed by a certificate authority (CA) that other systems are configured to trust. TLS uses a single certificate so that a client can verify a server's identity. Mutual TLS uses two certificates, one on each side of the connection, so that both parties can verify the other's identity. Device certificates authenticate a device such as a phone or laptop when it enrolls with a device management system. Code signing certificates are used to verify that a binary or other software artifact hasn't been modified since it was signed.++## Why manage certificates++When a certificate expires, the service that relies on it stops functioning correctly. Preventing this requires tracking the expiration date of every certificate in use and renewing each one before it expires. When certificates are managed through manual processes, an expiration can be missed if the person responsible doesn't receive an alert, doesn't know where the certificate is deployed, or isn't aware that a renewal is required.++A certificate management system maintains a single record of every certificate that has been issued, the certificate authority that issued it, the systems where it's deployed, and its expiration date. Expiring certificates can be renewed automatically, or an alert can be raised so that a person can renew them. Issuance can be governed by documented policies rather than by informal knowledge held by individual team members.++## How Infisical does it++Infisical Certificate Management supports three stages of the certificate lifecycle.++- **Issuance.** Certificates can be issued from private [CA hierarchies](/documentation/platform/pki/ca/overview) managed within Infisical, or from external providers such as DigiCert, AWS Private CA, and Let's Encrypt. Requests can be submitted through the API or through the [ACME](/documentation/platform/pki/applications/enrollment-methods/acme), [EST](/documentation/platform/pki/applications/enrollment-methods/est), and [SCEP](/documentation/platform/pki/applications/enrollment-methods/scep) enrollment protocols.+- **Delivery.** Certificates can be [synchronized](/documentation/platform/pki/applications/certificate-syncs/overview) to destinations such as AWS ACM, Azure Key Vault, and Cloudflare. The [discovery](/documentation/platform/pki/discovery/overview) feature scans infrastructure to identify certificates that were issued outside of Infisical so they can be added to the inventory.+- **Renewal and alerting.** Certificates can be renewed automatically before they expire, and [alerts](/documentation/platform/pki/applications/alerting/overview) can be sent through Slack, PagerDuty, or webhooks when a certificate requires attention. [Approval workflows](/documentation/platform/pki/applications/approvals) can be configured so that certain certificates require review before they're issued.++[Code signing](/documentation/platform/pki/code-signing/overview) is available for signing binaries, container images, and firmware. Signing operations use centrally managed keys and can be gated by approval workflows. Infisical also supports PKCS#11 integration for use with existing signing tools.diff --git a/docs/documentation/getting-started/choose-a-product/secret-scanning.mdx b/docs/documentation/getting-started/choose-a-product/secret-scanning.mdxnew file mode 100644index 0000000000..6469d4ae13--- /dev/null+++ b/docs/documentation/getting-started/choose-a-product/secret-scanning.mdx@@ -0,0 +1,44 @@+---+title: "Detect leaked secrets"+sidebarTitle: "Detect leaked secrets"+description: "Identify credentials that have been stored in source code or developer systems."+---++Infisical Secrets Scanning detects credentials that have been placed in locations where they shouldn't be stored, such as source code repositories, configuration files, and helper scripts. Scanning can be performed against connected cloud-hosted repositories or against local files on a developer's machine.++<Card title="Secrets Scanning docs" icon="radar" href="/documentation/platform/secret-scanning/overview">+ Data sources, scan modes, findings and lifecycle, custom rules, and CLI usage.+</Card>++## Use cases++<CardGroup cols={2}>+ <Card title="Monitor connected repositories" icon="code-branch" href="/documentation/platform/secret-scanning/github">+ Continuously scan GitHub, GitLab, and Bitbucket repositories as new commits are added.+ </Card>+ <Card title="Scan locally with the CLI" icon="terminal" href="/cli/commands/scan">+ Scan a working directory, Git history, or staged changes before they're pushed to a shared branch.+ </Card>+ <Card title="Manage findings across scans" icon="list-check" href="/documentation/platform/secret-scanning/overview">+ Review detected credentials with file, line, commit, and rule; resolve, ignore, or mark them as false positives.+ </Card>+</CardGroup>++## What is a leaked secret?++A leaked secret is a credential that has been stored or exposed in a location where it can be accessed by users who aren't authorized to use it. Common examples include public source code repositories, private repositories with a large set of readers, shared configuration files, and build logs. A credential that has been leaked can be used by anyone who can read it until the credential is rotated or revoked.++## Why scan for leaked secrets++Secrets are often leaked unintentionally. Common examples include committing a `.env` file to a repository, printing environment variables to a CI log, and pushing a script that contains credentials to a shared branch. These events don't require any intent to expose the credential, and they will continue to occur unless there is an automated process to detect them.++Secrets scanning provides this automated process. Continuous scanning of connected repositories detects credentials as new commits are added, and local scanning before a push prevents credentials from being pushed at all. Together, these two approaches reduce the time between when a credential is leaked and when it's detected.++## How Infisical does it++Infisical Secrets Scanning runs in two environments.++- **Connected repositories.** [GitHub](/documentation/platform/secret-scanning/github), [GitLab](/documentation/platform/secret-scanning/gitlab), and [Bitbucket](/documentation/platform/secret-scanning/bitbucket) repositories can be monitored continuously. Each new commit is scanned. When a credential is detected, Infisical records a finding that includes the file path, line number, commit hash, and the detection rule that matched.+- **Local environments.** The [`infisical scan`](/cli/commands/scan) CLI command scans a working directory, Git history, or staged changes in a CI pipeline before the changes are pushed to a shared branch.++The detection engine uses pattern matching, entropy analysis, and user-defined rules to identify credentials. Findings can be resolved, ignored, or marked as false positives, and each scan is recorded in an audit log. To reduce the number of false positives, users can define custom detection patterns, ignore rules through `infisical-scan:ignore` and `.infisicalignore`, adjust the entropy threshold, and exclude specific file paths from scanning.diff --git a/docs/documentation/getting-started/choose-a-product/secrets-management/overview.mdx b/docs/documentation/getting-started/choose-a-product/secrets-management/overview.mdxnew file mode 100644index 0000000000..6e73a5e7ec--- /dev/null+++ b/docs/documentation/getting-started/choose-a-product/secrets-management/overview.mdx@@ -0,0 +1,76 @@+---+title: "Manage secrets"+sidebarTitle: "Manage secrets"+description: "Store credentials centrally in Infisical and deliver them to the applications and infrastructure that use them."+---++Infisical Secrets Management is a central store for the secrets used by applications and infrastructure. It replaces `.env` files, hardcoded credentials, and secrets that are shared between team members through channels such as Slack. Once secrets are stored in Infisical, they can be delivered to the systems that use them.++<Card title="Secrets Management docs" icon="vault" href="/documentation/platform/secrets-mgmt/overview">+ Quickstart, project structure, delivery methods, rotation, dynamic secrets, and integrations.+</Card>++## Use cases++### Pull at runtime++<CardGroup cols={2}>+ <Card title="Deliver secrets to running apps" icon="truck-fast" href="/documentation/platform/secrets-mgmt/quick-starts/deliver-first-secret">+ Fetch secrets from Infisical at runtime through the CLI, SDKs, agents, Kubernetes, or CI/CD.+ </Card>+ <Card title="Replace .env in local development" icon="laptop-code" href="/documentation/guides/local-development">+ Run an application locally and fetch its secrets from Infisical instead of a `.env` file.+ </Card>+</CardGroup>++### Sync to a native store++<CardGroup cols={1}>+ <Card title="Sync secrets to third-party stores" icon="arrows-rotate" href="/integrations/secret-syncs/overview">+ Forward secrets from Infisical to platforms such as GitHub, GitLab, AWS Secrets Manager, and Vercel.+ </Card>+</CardGroup>++### Generate per request++<CardGroup cols={2}>+ <Card title="Rotate a long-lived credential" icon="rotate" href="/documentation/platform/secret-rotation/overview">+ Automatically replace a credential on a schedule managed by Infisical.+ </Card>+ <Card title="Generate short-lived credentials" icon="bolt" href="/documentation/platform/dynamic-secrets/overview">+ Generate a credential at the time of the request and revoke it after a short period.+ </Card>+</CardGroup>++### Broker to AI agents++<CardGroup cols={1}>+ <Card title="Broker credentials to AI agents" icon="robot" href="/documentation/platform/agent-proxy/overview">+ Attach credentials to agent requests at a proxy so that the agent never receives the credential.+ </Card>+</CardGroup>++## What is a secret?++A secret is a confidential value that an application uses to authenticate with or otherwise access another system. Common examples include database passwords, API keys, signing keys, and access tokens. If a secret is exposed to a party that isn't authorized to use it, the systems it grants access to are also exposed.++## Why manage secrets centrally?++As an organization grows, secrets tend to be duplicated across multiple locations. The same credential can be committed to source code, shared in chat messages, copied into CI/CD configuration, and stored in developer `.env` files. When a credential is stored in many places, it becomes difficult to track who has access to it, when it was last rotated, and where its value needs to be updated when it changes.++Storing secrets centrally in Infisical addresses these problems by providing a single location where a secret's value is stored, a single set of access controls that determine who can read the secret, an audit log of accesses and changes, and a single place from which the secret can be rotated.++## How Infisical does it++Infisical stores secrets in a four-level hierarchy:++```+Project → Environment → Folder → Secret+```++- **Projects** contain the secrets used by a single application or service, along with the access rules that determine who can read them.+- **Environments** separate secrets by where they're used. The same secret key can hold different values in `development`, `staging`, and `production`.+- **Folders** group related secrets within an environment and can be used as boundaries for access control.+- **Secrets** are key-value pairs. Every change to a secret is versioned, secrets can reference the values of other secrets, and a secret can be restored to a previous value.++In addition to storing secrets, Infisical delivers them to applications and infrastructure through the [CLI](/cli/overview), [SDKs](/sdks/overview), [agents](/integrations/platforms/infisical-agent), [Kubernetes](/integrations/platforms/kubernetes/overview), and CI/CD. Long-lived credentials can be [rotated](/documentation/platform/secret-rotation/overview) on a schedule, short-lived credentials can be [generated on demand](/documentation/platform/dynamic-secrets/overview), and changes to secrets in sensitive folders can require [approval](/documentation/platform/pr-workflows) before they're applied.diff --git a/docs/documentation/getting-started/concepts/app-connections.mdx b/docs/documentation/getting-started/concepts/app-connections.mdxnew file mode 100644index 0000000000..4004f66445--- /dev/null+++ b/docs/documentation/getting-started/concepts/app-connections.mdx@@ -0,0 +1,15 @@+---+title: "External integrations"+sidebarTitle: "External integrations"+description: "Stored credentials that allow Infisical to authenticate with third-party services on your behalf."+---++<Card title="App connections docs" icon="plug" href="/integrations/app-connections/overview">+ Every supported connection type, how to create a connection, and how to scope one to a project.+</Card>++An App Connection is a stored credential that Infisical uses to authenticate with a third-party service. App Connections are used by Secret Syncs, external migrations, dynamic secret providers, and other integrations that need to reach a system outside of Infisical.++App Connections can be scoped to a single project or to the entire organization. A project-scoped connection is only visible inside the project where it was created. An organization-scoped connection is visible across every project in the organization.++Infisical supports App Connections for cloud providers, secret managers, source control platforms, CI/CD systems, databases, and many other services.diff --git a/docs/documentation/getting-started/concepts/audit-logs.mdx b/docs/documentation/getting-started/concepts/audit-logs.mdxindex 4b7b42d107..964035b2ef 100644--- a/docs/documentation/getting-started/concepts/audit-logs.mdx+++ b/docs/documentation/getting-started/concepts/audit-logs.mdx@@ -4,7 +4,11 @@ sidebarTitle: "Audit logs"description: "Understand how Infisical logs activity and supports external audit streaming."----Infisical records a detailed audit trail of actions across the platform — providing deep visibility into access, changes, and usage for security and compliance purposes.+<Card title="Audit logs docs" icon="clipboard-list" href="/documentation/platform/audit-logs">+ Every event Infisical records, how to filter and inspect them, and how to stream them to a SIEM.+</Card>++Infisical records a detailed audit trail of actions across the platform, providing deep visibility into access, changes, and usage for security and compliance purposes.Every interaction with Infisical resources generates an audit event. These events are immutable and include metadata such as the actor, event type, affected resources, timestamp, IP address, and client source.diff --git a/docs/documentation/getting-started/concepts/contributing.mdx b/docs/documentation/getting-started/concepts/contributing.mdxnew file mode 100644index 0000000000..6b36e11b41--- /dev/null+++ b/docs/documentation/getting-started/concepts/contributing.mdx@@ -0,0 +1,13 @@+---+title: "Contributing"+sidebarTitle: "Contributing"+description: "How to propose a change to Infisical, run the platform locally, and open a pull request."+---++<Card title="Contributing docs" icon="code-pull-request" href="/contributing/getting-started/overview">+ Local development setup, contribution workflow, and pull request guidelines.+</Card>++Infisical is [open source](https://github.com/Infisical/infisical), and community contributions are accepted through the main repository. The contributing documentation covers how to set up a local development environment, how to run the platform against a local database, and how to submit a pull request.++Contributions can include bug fixes, new features, documentation updates, and translations. Larger changes are typically discussed in an issue or a draft pull request before implementation begins.diff --git a/docs/documentation/getting-started/concepts/deployment-models.mdx b/docs/documentation/getting-started/concepts/deployment-models.mdxindex 5940a85f3e..483d8fb322 100644--- a/docs/documentation/getting-started/concepts/deployment-models.mdx+++ b/docs/documentation/getting-started/concepts/deployment-models.mdx@@ -1,9 +1,12 @@----title: "Deployment models: Cloud or self-hosted"-sidebarTitle: "Cloud vs. self-host"-description: "Choose between Infisical Cloud or a self-managed deployment"+title: "Cloud vs. self-hosting"+description: "Choose between Infisical Cloud or a self-managed deployment."---+<Card title="Self-hosting docs" icon="server" href="/self-hosting/overview">+ Deployment options, configuration, upgrades, and reference architectures for running Infisical yourself.+</Card>+Infisical can be used in two ways: via [Infisical Cloud](https://app.infisical.com), a managed offering, or through a self-hosted deployment within your own infrastructure.Both options provide the same core platform capabilities. The decision depends on your operational model, trust boundaries, and compliance requirements. While Infisical Cloud comes with built-in security and operational guarantees, a self-hosted deployment gives you full control—but also full responsibility for securing and maintaining the system.diff --git a/docs/documentation/getting-started/concepts/internals.mdx b/docs/documentation/getting-started/concepts/internals.mdxnew file mode 100644index 0000000000..b40316322f--- /dev/null+++ b/docs/documentation/getting-started/concepts/internals.mdx@@ -0,0 +1,13 @@+---+title: "Architecture and security"+sidebarTitle: "Architecture and security"+description: "How Infisical is built, how permissions are evaluated, and how data is encrypted."+---++<Card title="Internals docs" icon="diagram-project" href="/internals/overview">+ Architecture, the security and encryption model, and the details of how permissions are evaluated.+</Card>++The internals documentation describes how Infisical is built and how its security-critical components work. This includes the platform's architecture, the components that run in each deployment configuration, the encryption model that protects stored data, and the algorithm used to evaluate permissions.++The internals pages are primarily useful for readers who need to review Infisical for a security audit, integrate with it at a low level, or understand its behavior in edge cases. Users who are only configuring or using the platform typically don't need to read them.diff --git a/docs/documentation/getting-started/concepts/networking.mdx b/docs/documentation/getting-started/concepts/networking.mdxnew file mode 100644index 0000000000..8561300721--- /dev/null+++ b/docs/documentation/getting-started/concepts/networking.mdx@@ -0,0 +1,13 @@+---+title: "Private network access"+sidebarTitle: "Private network access"+description: "How Infisical reaches systems that aren't directly accessible from its own network."+---++<Card title="Networking docs" icon="network-wired" href="/documentation/platform/gateways/overview">+ Gateways, gateway pools, relays, and the network architecture that connects them to Infisical.+</Card>++Infisical uses gateways and relays to reach systems that aren't directly accessible from its own network. A gateway is a process that runs inside a customer network and forwards requests from Infisical to systems on the same network, such as an internal database or an on-premises certificate authority. A relay is a component that connects a gateway to Infisical when a direct network connection between the two isn't possible.++Gateways are required when Infisical needs to access a system that isn't exposed to the public internet, such as a database inside a private cloud VPC, a Kubernetes cluster in an air-gapped environment, or a device management server behind a corporate firewall.diff --git a/docs/documentation/getting-started/concepts/platform-hierarchy.mdx b/docs/documentation/getting-started/concepts/platform-hierarchy.mdxindex ef26b5f999..66fc5e49c4 100644--- a/docs/documentation/getting-started/concepts/platform-hierarchy.mdx+++ b/docs/documentation/getting-started/concepts/platform-hierarchy.mdx@@ -1,9 +1,13 @@----title: "Platform hierarchy"-sidebarTitle: "Platform hierarchy"-description: "Understand how organizations and projects are structured in Infisical."+title: "Account structure"+sidebarTitle: "Account structure"+description: "How organizations and projects are structured in Infisical."---+<Card title="Organizations docs" icon="building" href="/documentation/platform/organization">+ Organization settings, projects, audit logs, admin console, and organization planning.+</Card>+Infisical is structured around organizations and projects, allowing teams to manage multiple products, access scopes, and use cases within a single account while keeping boundaries and responsibilities clearly defined.## Organizationsdiff --git a/docs/documentation/getting-started/concepts/platform-iam.mdx b/docs/documentation/getting-started/concepts/platform-iam.mdxindex 39e637c639..ad853dd5c8 100644--- a/docs/documentation/getting-started/concepts/platform-iam.mdx+++ b/docs/documentation/getting-started/concepts/platform-iam.mdx@@ -1,9 +1,13 @@----title: "Platform identity and access management"-sidebarTitle: "Platform IAM"-description: "Understand how users, machine identities, roles, and permissions are managed."+title: "Identity and access"+sidebarTitle: "Identity and access"+description: "How users, machine identities, roles, and permissions are managed."---+<Card title="Identity and access docs" icon="id-card" href="/documentation/platform/identities/overview">+ User identities, machine identities, groups, SSO, SCIM, and access control.+</Card>+Infisical uses identity-based access control to govern how users and systems interact with secrets, certificates, infrastructure, and other resources on the platform.There are two types of identities:diff --git a/docs/documentation/getting-started/introduction.mdx b/docs/documentation/getting-started/introduction.mdxindex 8995587f00..2ba66f781d 100644--- a/docs/documentation/getting-started/introduction.mdx+++ b/docs/documentation/getting-started/introduction.mdx@@ -12,22 +12,9 @@ It provides modern security workflows — including secrets rotation, dynamic crStart managing secrets securely with [Infisical Cloud](https://app.infisical.com) or learn how to [host Infisical](/self-hosting/overview) yourself.-The short video below provides a guided overview of Infisical's platform and key concepts, helping you build the right mental model before diving into the rest of the documentation.--<br />---<div style={{ position: "relative", paddingBottom: "56.25%", height: 0, overflow: "hidden", maxWidth: "100%" }}>- <iframe- src="https://www.youtube.com/embed/2GrrScI2Qms"- title="YouTube video player"- style={{ position: "absolute", top: 0, left: 0, width: "100%", height: "100%", border: 0 }}- allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"- allowFullScreen- ></iframe>-</div>--<br />+<Tip>+ Visual learner? Watch a [guided overview of the Infisical platform](https://www.youtube.com/watch?v=2GrrScI2Qms) to build the right mental model before diving into the rest of the documentation.+</Tip>## Why use Infisical?@@ -46,12 +33,52 @@ Infisical addresses this challenge by providing an all-in-one platform and workfInfisical is designed to integrate cleanly into your stack—improving security without adding complexity.-## What does Infisical include?--Infisical consists of several tightly integrated products, each designed to solve a specific part of the infrastructure security surface:--- [Secrets Management](/documentation/platform/secrets-mgmt/overview): Securely store, access, and distribute secrets across environments with fine-grained controls, automatic rotation, and audit logging.-- [Secrets Scanning](/documentation/platform/secret-scanning/overview): Detect hardcoded secrets in code, CI pipelines, and infrastructure—integrated with GitHub, GitLab, Bitbucket, and more.-- [Certificate Management](/documentation/platform/pki/overview): Issue and manage X.509 certificates using protocols like EST, with support for internal and external CAs.-- [Infisical KMS](/documentation/platform/kms/overview): Encrypt and decrypt data using centrally managed keys with enforced access policies and full audit visibility.-- [Infisical PAM](/documentation/platform/pam/overview): Manage access to resources like databases, servers, and accounts with policy-based controls and approvals.+## 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.++<CardGroup cols={2}>+ <Card title="Manage secrets" icon="vault" 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-certificate" 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">+ Perform encryption, decryption, and signing operations using keys stored within Infisical.+ </Card>+ <Card title="Manage privileged access" icon="user-shield" 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>+</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.++<CardGroup cols={2}>+ <Card title="Account structure" icon="building" href="/documentation/getting-started/concepts/platform-hierarchy">+ How organizations, projects, and members are structured within Infisical.+ </Card>+ <Card title="Identity and access" icon="id-card" href="/documentation/getting-started/concepts/platform-iam">+ How users and machine identities authenticate, and how roles determine their permissions.+ </Card>+ <Card title="External integrations" icon="plug" href="/documentation/getting-started/concepts/app-connections">+ Stored credentials that allow Infisical to authenticate with third-party services on your behalf.+ </Card>+ <Card title="Private network access" icon="network-wired" href="/documentation/getting-started/concepts/networking">+ How Infisical reaches systems that aren't directly accessible from its own network.+ </Card>+ <Card title="Cloud vs. self-host" icon="server" href="/documentation/getting-started/concepts/deployment-models">+ Choose between running Infisical on Infisical Cloud or on your own infrastructure.+ </Card>+ <Card title="Architecture and security" icon="diagram-project" href="/documentation/getting-started/concepts/internals">+ How Infisical is built, how permissions are evaluated, and how data is encrypted.+ </Card>+ <Card title="Contributing" icon="code-pull-request" href="/documentation/getting-started/concepts/contributing">+ How to propose a change to Infisical, run the platform locally, and open a pull request.+ </Card>+</CardGroup>diff --git a/docs/documentation/getting-started/overview.mdx b/docs/documentation/getting-started/overview.mdxindex 3ebd43ad06..34c2760c55 100644--- a/docs/documentation/getting-started/overview.mdx+++ b/docs/documentation/getting-started/overview.mdx@@ -7,9 +7,14 @@ icon: "play"import AiAgentsCallout from "/snippets/ai-agents-callout.mdx";-<Card title="What is Infisical?" href="/documentation/getting-started/introduction">- Learn what Infisical is and how it can help you manage secrets, certificates, and secure access across your infrastructure.-</Card>+<CardGroup cols={2}>+ <Card title="Quickstarts" icon="rocket" href="/documentation/getting-started/quickstarts">+ Follow guides for common tasks in Infisical, grouped by product.+ </Card>+ <Card title="What is Infisical?" icon="circle-info" href="/documentation/getting-started/introduction">+ Learn how Infisical manages secrets, certificates, and infrastructure access.+ </Card>+</CardGroup>## Productsdiff --git a/docs/documentation/getting-started/quickstarts.mdx b/docs/documentation/getting-started/quickstarts.mdxnew file mode 100644index 0000000000..5ab2fd7fec--- /dev/null+++ b/docs/documentation/getting-started/quickstarts.mdx@@ -0,0 +1,150 @@+---+title: "Quickstarts"+description: "Guides for the most common tasks in Infisical."+mode: "frame"+---++<div className="qs-index">++<div className="qs-index__hero">+ <h1 className="qs-index__title">Quickstarts</h1>+ <p className="qs-index__description">Guides for the most common tasks in Infisical, grouped by product area.</p>+</div>++<div className="qs-index__jump" role="navigation" aria-label="Quickstart sections">+ <span className="qs-index__jump-label">Jump to</span>+ <div className="qs-index__jump-links">+ <a href="#secrets-management" className="qs-index__jump-chip qs-index__jump-chip--secrets">Secrets Management</a>+ <a href="#secrets-scanning" className="qs-index__jump-chip qs-index__jump-chip--scanning">Secrets Scanning</a>+ <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>+ </div>+ <div className="qs-index__jump-links">+ <a href="#identity-and-access" className="qs-index__jump-chip qs-index__jump-chip--identity">Identity</a>+ <a href="#networking" className="qs-index__jump-chip qs-index__jump-chip--networking">Networking</a>+ <a href="#self-hosting" className="qs-index__jump-chip qs-index__jump-chip--self-hosting">Self-hosting</a>+ </div>+</div>++<section className="qs-index__section qs-index__section--secrets">++<h2 id="secrets-management"><a href="/documentation/platform/secrets-mgmt/overview" className="qs-index__section-link">Secrets Management<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">Store secrets in Infisical and deliver them to the applications and infrastructure that use them.</p>++| Quickstart | Description |+| --- | --- |+| [Add your secrets to Infisical](/documentation/platform/secrets-mgmt/quick-starts/deliver-first-secret) | Store your secrets in Infisical and inject them into a running application. |+| [Run an app locally with secrets from Infisical](/documentation/guides/local-development) | Use the Infisical CLI to inject secrets into a locally running application. |+| [Inject secrets into a Docker container](/integrations/platforms/docker) | Deliver secrets from Infisical to a Docker container at startup. |+| [Inject secrets into a GitHub Actions workflow](/integrations/cicd/githubactions) | Fetch secrets from Infisical inside a GitHub Actions workflow at runtime. |+| [Sync secrets into Kubernetes](/documentation/guides/kubernetes-operator) | Use the Infisical Kubernetes Operator to pull secrets into a cluster. |+| [Rotate a PostgreSQL credential](/documentation/platform/secret-rotation/postgres-credentials) | Automatically replace a PostgreSQL credential on a schedule. |+| [Generate a short-lived PostgreSQL credential](/documentation/platform/dynamic-secrets/postgresql) | Generate a PostgreSQL credential on demand and revoke it after a short period. |++</section>++<section className="qs-index__section qs-index__section--scanning">++<h2 id="secrets-scanning"><a href="/documentation/platform/secret-scanning/overview" className="qs-index__section-link">Secrets Scanning<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">Detect credentials that have been committed to a source code repository.</p>++| Quickstart | Description |+| --- | --- |+| [Scan a GitHub repository for leaked secrets](/documentation/platform/secret-scanning/github) | Connect a GitHub repository to Infisical and detect exposed credentials. |+| [Scan a GitLab repository for leaked secrets](/documentation/platform/secret-scanning/gitlab) | Connect a GitLab repository to Infisical and detect exposed credentials. |+| [Scan a Bitbucket repository for leaked secrets](/documentation/platform/secret-scanning/bitbucket) | Connect a Bitbucket repository to Infisical and detect exposed credentials. |++</section>++<section className="qs-index__section qs-index__section--certificates">++<h2 id="certificate-management"><a href="/documentation/platform/pki/overview" className="qs-index__section-link">Certificate Management<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">Issue and manage X.509 certificates through a private or public certificate authority.</p>++| Quickstart | Description |+| --- | --- |+| [Issue your first certificate](/documentation/platform/pki/quick-starts/issue-first-certificate) | Set up a certificate authority and issue an X.509 certificate. |+| [Enroll certificates with ACME](/documentation/platform/pki/applications/enrollment-methods/acme) | Issue certificates to servers and workloads through the ACME protocol. |+| [Enroll a device with Microsoft Intune SCEP](/documentation/platform/pki/guides/applications/microsoft-intune-scep) | Push certificates to Intune-managed devices through SCEP. |++</section>++<section className="qs-index__section qs-index__section--kms">++<h2 id="key-management"><a href="/documentation/platform/kms/overview" className="qs-index__section-link">Key Management<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">Store cryptographic keys in Infisical and use them to encrypt, decrypt, and sign.</p>++| Quickstart | Description |+| --- | --- |+| [Back Infisical KMS with an HSM](/self-hosting/guides/hsm-integration) | Use a hardware security module to protect the root key. |+| [Encrypt Kubernetes secrets with Infisical KMS](/documentation/platform/kms/kubernetes-encryption) | Use Infisical KMS as the encryption provider for Kubernetes secrets. |+| [Sign container images with Cosign](/documentation/platform/kms/sigstore-cosign) | Use a key from Infisical KMS to sign and verify container images with Cosign. |+| [Serve keys through KMIP](/documentation/platform/kms/kmip) | Expose keys from Infisical KMS to KMIP clients. |++</section>++<section className="qs-index__section qs-index__section--pam">++<h2 id="privileged-access-management"><a href="/documentation/platform/pam/overview" className="qs-index__section-link">Privileged Access Management<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">Give users time-bound, audited access to databases and servers without sharing the underlying credential.</p>++| Quickstart | Description |+| --- | --- |+| [Access a database or server through Infisical](/documentation/platform/pam/quick-starts/launch-first-session) | Open a session to a database or server without exposing the credential. |+| [Open an SSH session through Infisical](/documentation/platform/pam/accounts/ssh) | Reach a server over SSH without handing out the credential. |+| [Access a PostgreSQL database through Infisical](/documentation/platform/pam/accounts/postgresql) | Open a session to a PostgreSQL database without exposing the credential. |++</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>++<p className="qs-index__section-desc">Authenticate applications and users to Infisical.</p>++| Quickstart | Description |+| --- | --- |+| [Authenticate a machine identity with universal auth](/documentation/platform/identities/universal-auth) | Configure universal auth so an application can authenticate with a client ID and secret. |+| [Authenticate a workload from Kubernetes](/documentation/platform/identities/kubernetes-auth) | Use a Kubernetes service account token to authenticate a workload with Infisical. |+| [Authenticate a workload with OIDC](/documentation/platform/identities/oidc-auth/general) | Use an OIDC identity token from a supported provider to authenticate a workload. |+| [Set up single sign-on](/documentation/platform/sso/overview) | Configure SSO through a supported identity provider. |++</section>++<section className="qs-index__section qs-index__section--networking">++<h2 id="networking"><a href="/documentation/platform/gateways/overview" className="qs-index__section-link">Networking<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">Reach systems that aren't on the public internet through a Gateway.</p>++| Quickstart | Description |+| --- | --- |+| [Reach private systems with a Gateway](/documentation/platform/gateways/overview) | Set up a Gateway to reach systems that aren't on the public internet. |+| [Deploy a Gateway](/documentation/platform/gateways/gateway-deployment) | Install and run a Gateway in your own infrastructure. |++</section>++<section className="qs-index__section qs-index__section--self-hosting">++<h2 id="self-hosting"><a href="/self-hosting/overview" className="qs-index__section-link">Self-hosting<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">Run Infisical on your own infrastructure.</p>++| Quickstart | Description |+| --- | --- |+| [Self-host Infisical with Docker Compose](/self-hosting/deployment-options/docker-compose) | Run Infisical on your own infrastructure using Docker Compose. |+| [Self-host Infisical with the standalone Docker image](/self-hosting/deployment-options/standalone-infisical) | Run the frontend and backend from a single Docker image. |+| [Self-host Infisical on Kubernetes with Helm](/self-hosting/deployment-options/kubernetes-helm) | Deploy Infisical to a Kubernetes cluster with the Helm chart. |+| [Self-host Infisical on AWS with ECS Fargate](/self-hosting/deployment-options/aws-native) | Deploy Infisical on AWS using ECS Fargate, RDS, and ElastiCache. |+| [Self-host Infisical on GCP with GKE](/self-hosting/deployment-options/gcp-native) | Deploy Infisical on GCP using GKE, Cloud SQL, and Memorystore. |+| [Install Infisical from the Linux package](/self-hosting/deployment-options/native/linux-package/installation) | Install Infisical directly on a Linux host with the native package. |++</section>++</div>diff --git a/docs/documentation/getting-started/set-up-with-ai.mdx b/docs/documentation/getting-started/set-up-with-ai.mdxnew file mode 100644index 0000000000..0f03ccf110--- /dev/null+++ b/docs/documentation/getting-started/set-up-with-ai.mdx@@ -0,0 +1,157 @@+---+title: "Build with AI tools"+description: "Connect AI tools such as Claude, Cursor, and Codex to the Infisical documentation and skills."+---++The Infisical documentation is designed to be consumed by AI tools as well as by people. If you use an AI agent such as Claude Code, Cursor, or Codex when working with Infisical, we recommend connecting it through the hosted [MCP server](#mcp-server) described below. The MCP server keeps the agent pointed at the current documentation, so answers reflect the latest version of Infisical without any files to re-upload as the docs change.++## MCP server++The Infisical documentation MCP server is available at the following URL:++```+https://infisical.com/docs/mcp+```++Authentication isn't required. Once an AI tool is connected to the server, it can search the documentation and retrieve the content of individual pages. This allows the tool to answer questions from the current documentation rather than from the data it was trained on.++### Connect++<Tabs>+ <Tab title="Claude">+ <Steps>+ <Step title="Open Claude's connector settings">+ Navigate to the [Connectors](https://claude.ai/settings/connectors) page in your Claude settings.+ </Step>+ <Step title="Add the Infisical MCP server">+ 1. Select **Add custom connector**.+ 2. Enter the following values:+ - **Name**: `Infisical`+ - **URL**: `https://infisical.com/docs/mcp`+ 3. Select **Add**.+ </Step>+ <Step title="Use the MCP server in a chat">+ 1. In a Claude chat, select the attachments button (the plus icon).+ 2. Select the Infisical MCP server.+ 3. Ask Claude a question about Infisical.+ </Step>+ </Steps>++ See the [Model Context Protocol documentation](https://modelcontextprotocol.io/docs/tutorials/use-remote-mcp-server#connecting-to-a-remote-mcp-server) for more details.+ </Tab>++ <Tab title="Claude Code">+ Run the following command to add the Infisical MCP server to Claude Code:++ ```bash+ claude mcp add --transport http Infisical https://infisical.com/docs/mcp+ ```++ Verify the connection:++ ```bash+ claude mcp list+ ```++ See the [Claude Code documentation](https://docs.anthropic.com/en/docs/claude-code/mcp#installing-mcp-servers) for more details.+ </Tab>++ <Tab title="Cursor">+ <Steps>+ <Step title="Open MCP settings">+ 1. Use <kbd>Command</kbd> + <kbd>Shift</kbd> + <kbd>P</kbd> (<kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>P</kbd> on Windows) to open the command palette.+ 2. Search for **Open MCP settings**.+ 3. Select **Add custom MCP**. This opens the `mcp.json` file.+ </Step>+ <Step title="Configure the Infisical MCP server">+ In `mcp.json`, add the following configuration:++ ```json+ {+ "mcpServers": {+ "Infisical": {+ "url": "https://infisical.com/docs/mcp"+ }+ }+ }+ ```+ </Step>+ <Step title="Test the connection">+ In Cursor's chat, ask "What tools do you have available?" Cursor lists the Infisical MCP server among the available tools.+ </Step>+ </Steps>++ See [Installing MCP servers](https://docs.cursor.com/en/context/mcp#installing-mcp-servers) in the Cursor documentation for more details.+ </Tab>++ <Tab title="VS Code">+ Create a `.vscode/mcp.json` file in your workspace and add the following configuration:++ ```json+ {+ "servers": {+ "Infisical": {+ "type": "http",+ "url": "https://infisical.com/docs/mcp"+ }+ }+ }+ ```++ See the [VS Code documentation](https://code.visualstudio.com/docs/copilot/chat/mcp-servers) for more details.+ </Tab>+</Tabs>++### Using it alongside other tools++An AI tool can be connected to multiple MCP servers simultaneously. A connected server adds only its tool descriptions to the context. The server itself isn't queried until the AI tool decides one of its tools is relevant to the request.++The following practices can improve results when using the Infisical MCP server:++- **Reference Infisical in the prompt.** When asking a question that should be answered from the Infisical documentation, mention Infisical explicitly (for example, "Using Infisical's CLI, how do I..."). This makes it more likely that the tool will query the Infisical MCP server.+- **Install the skills as well.** The skills described below provide additional guidance on top of the documentation.+- **Disconnect unused MCP servers.** If many MCP servers are connected, removing those that aren't actively in use can reduce the total context available to the tool for each request.++### Context files++For AI tools that don't support MCP but can accept text as context, the Infisical documentation hosts the following two files:++- [`llms.txt`](https://infisical.com/docs/llms.txt): a structured index of every documentation page.+- [`llms-full.txt`](https://infisical.com/docs/llms-full.txt): the complete documentation site compiled into a single file.++If the AI tool supports MCP, use the MCP server rather than these files. The MCP server always returns the current version of the documentation, whereas the context files must be re-uploaded when the documentation changes.++## Per-page shortcuts++Every documentation page includes a menu in the upper-right corner that provides shortcuts for interacting with AI tools. From this menu, you can:++- Ask the built-in assistant a question about the current page.+- Copy the page as Markdown, or view the page's Markdown source.+- Open the page in ChatGPT or Claude.+- Copy the MCP server URL for use with a different AI tool.++## Skills++The Infisical skills can be installed with a single command:++```bash+npx skills add Infisical/ai-skills+```++The skills cover setup for the CLI and SDKs, App Connections, Secret Syncs, dynamic secrets, secret rotation, PKI, KMS, PAM, secrets scanning, access control, SSO, gateways, and self-hosting. The full list of skills and per-agent installation instructions are available in the [`Infisical/ai-skills`](https://github.com/infisical/ai-skills) repository.++## FAQ++<AccordionGroup>+ <Accordion title="What's the difference between the MCP server and skills?">+ The MCP server lets an AI tool search and retrieve the Infisical documentation on demand, so its answers stay in sync with the current docs. Skills are a set of instructions that describe how to work with Infisical, including conventions and common workflows.++ We recommend using the MCP server to interact with the documentation, which contains the most up-to-date information about how to use Infisical.+ </Accordion>+ <Accordion title="Do I need an Infisical account to use the MCP server?">+ No. The Infisical documentation MCP server is publicly available and doesn't require authentication.+ </Accordion>+ <Accordion title="Can I use the MCP server with any AI tool?">+ The MCP server can be used with any AI tool that supports the Model Context Protocol over HTTP.+ </Accordion>+</AccordionGroup>diff --git a/docs/documentation/platform/external-migrations/overview.mdx b/docs/documentation/platform/external-migrations/overview.mdxindex 8e030c85e2..fc297121e2 100644--- a/docs/documentation/platform/external-migrations/overview.mdx+++ b/docs/documentation/platform/external-migrations/overview.mdx@@ -1,29 +1,28 @@----title: "External migrations"-sidebarTitle: "Overview"-description: "Learn how to migrate resources from third-party secrets management platforms to Infisical."+title: "Migrate to Infisical"+description: "Move existing secrets and related resources from another platform into Infisical."----## Overview+Infisical supports migrating existing resources from Vault and Doppler. A migration can be performed either through an ongoing in-platform connection to the source, or through a one-time bulk import.-Infisical supports migrating resources from third-party secrets management platforms to Infisical. This is useful if you're looking to easily switch to Infisical and wish to move over your existing resources from a different platform.+## Per-platform guides-Infisical offers two types of migration approaches:+The guides below cover the migration process for each supported platform. Each guide includes the steps to configure the connection, a description of which resources can be migrated, and any translation that Infisical performs during the import.-- **In-Platform Migration Tooling**: Connect to a supported platform (like Vault or Doppler) using an **App Connection** — either project-scoped (created inside a project) or organization-scoped (visible across every project). Import resources on demand from anywhere the App Connection is visible.+<CardGroup cols={2}>+ <Card title="Vault" icon="vault" href="/documentation/platform/external-migrations/vault">+ Migrate KV secrets, Kubernetes authentication configuration, dynamic secret configurations, and policies from HashiCorp Vault.+ </Card>+ <Card title="Doppler" icon="capsules" href="/documentation/platform/external-migrations/doppler">+ Migrate secrets from Doppler projects and configs, including both root and branch environments.+ </Card>+</CardGroup>-- **Bulk Data Import**: Run a one-time, organization-wide import directly from raw platform credentials. This is ideal for an initial cutover when you're moving entirely to Infisical. Currently available for HashiCorp Vault.+If a platform isn't listed, open an issue on the [Infisical repository](https://github.com/infisical/infisical/issues) to request support for it.-## Supported platforms+## Migration approaches+The guides above use one of the following two migration approaches.-**In-platform migration (per-platform guides)**--- [Vault](./vault) — KV secrets, Kubernetes auth and dynamic secret shapes, policy translation-- [Doppler](./doppler) — secrets from Doppler projects and configs (root and branch)--**Bulk one-shot organization import**--- HashiCorp Vault — see the [bulk import section in the Vault guide](./vault#one-time-bulk-import-from-vault).--We're always looking to add more migration paths for other providers. If we're missing a platform, please open an issue on our [GitHub repository](https://github.com/infisical/infisical/issues).+- **In-platform migration.** Infisical connects to the source platform using an [App Connection](/integrations/app-connections/overview) that is scoped either to a single project or to the entire organization. Resources can be imported on demand from any location where the connection is available. This approach is supported for Vault and Doppler.+- **Bulk one-time import.** Infisical performs a one-time, organization-wide import using credentials provided at the time of the import. This approach is suitable for an initial cutover when moving entirely from another platform to Infisical. It's supported for HashiCorp Vault. See the [bulk import section of the Vault guide](/documentation/platform/external-migrations/vault#one-time-bulk-import-from-vault) for details.diff --git a/docs/documentation/platform/secrets-mgmt/quick-starts/deliver-first-secret.mdx b/docs/documentation/platform/secrets-mgmt/quick-starts/deliver-first-secret.mdxindex 73db662dc4..9a7a6e2aab 100644--- a/docs/documentation/platform/secrets-mgmt/quick-starts/deliver-first-secret.mdx+++ b/docs/documentation/platform/secrets-mgmt/quick-starts/deliver-first-secret.mdx@@ -1,12 +1,12 @@----title: "Deliver your first secret"+title: "Add your secrets"sidebarTitle: "Quickstart"description: "Create a project, add your secrets, and choose how to deliver them to your application or infrastructure."---import ConfigureProject from "/snippets/documentation/platform/secrets-mgmt/configure-project.mdx";-This quickstart walks you through the steps shared by every Infisical secrets delivery workflow. You'll create a [project](/documentation/platform/secrets-mgmt/project), add a secret, and then continue with instructions for your application or infrastructure.+This quickstart walks you through the steps shared by every Infisical secrets delivery workflow. You'll create a [project](/documentation/platform/secrets-mgmt/project), add your secrets, and then continue with instructions for your application or infrastructure.## Prerequisitesdiff --git a/docs/documentation/platform/secrets-mgmt/quick-starts/migrate.mdx b/docs/documentation/platform/secrets-mgmt/quick-starts/migrate.mdxnew file mode 100644index 0000000000..4ce6bcde51--- /dev/null+++ b/docs/documentation/platform/secrets-mgmt/quick-starts/migrate.mdx@@ -0,0 +1,18 @@+---+title: "Migrate your secrets"+sidebarTitle: "Migrate your secrets"+description: "Import existing secrets from another platform into an Infisical Secrets Management project."+---++Existing secrets can be migrated into an Infisical Secrets Management project from another platform. The guides below cover the migration process for each supported platform, including the steps to configure the connection, a description of which secrets can be migrated, and any translation that Infisical performs during the import.++<CardGroup cols={2}>+ <Card title="Vault" icon="vault" href="/documentation/platform/external-migrations/vault">+ Migrate KV secrets, Kubernetes authentication configuration, dynamic secret configurations, and policies from HashiCorp Vault.+ </Card>+ <Card title="Doppler" icon="capsules" href="/documentation/platform/external-migrations/doppler">+ Migrate secrets from Doppler projects and configs, including both root and branch environments.+ </Card>+</CardGroup>++If a platform isn't listed, open an issue on the [Infisical repository](https://github.com/infisical/infisical/issues) to request support for it.diff --git a/docs/snippets/ai-agents-callout.mdx b/docs/snippets/ai-agents-callout.mdxindex 974146e643..0178261b3b 100644--- a/docs/snippets/ai-agents-callout.mdx+++ b/docs/snippets/ai-agents-callout.mdx@@ -1,11 +1,11 @@<Tip>- **Using an AI coding tool?** Point it at our resources for better results when working with Infisical.+ **Using an AI coding tool?** Connect it to the Infisical resources described below for better results.- Install the Infisical skill to give your agent context on platform structure, services, and best practices:+ Install the Infisical skills to provide the tool with information about the platform's structure, services, and conventions:```bash- npx skills add https://github.com/infisical/ai-skills+ npx skills add Infisical/ai-skills```- Then add the Infisical MCP server for access to documentation search. Follow the setup instructions at [`https://infisical.com/docs/ai/model-context-protocol`](https://infisical.com/docs/ai/model-context-protocol).+ Then add the Infisical MCP server to give the tool access to the current documentation. See [Set up with AI](https://infisical.com/docs/documentation/getting-started/set-up-with-ai) for the full setup instructions.</Tip>diff --git a/docs/style.css b/docs/style.cssindex a927837820..47ba72e89f 100644--- a/docs/style.css+++ b/docs/style.css@@ -2,6 +2,304 @@border-radius: 0 !important;}+/* Quickstarts index page */+.qs-index {+ max-width: 960px;+ margin: 0 auto;+ padding: 3rem 1.5rem 4rem;+ --qs-accent: #5f7000;+}++.qs-index__hero {+ margin-bottom: 2rem;+}++.qs-index__title {+ font-size: 2.25rem;+ font-weight: 600;+ letter-spacing: -0.02em;+ color: #171718;+ margin: 0 0 0.75rem 0;+ line-height: 1.15;+}++.qs-index__description {+ font-size: 1.0625rem;+ color: #6f6f6f;+ margin: 0;+ line-height: 1.5;+}++.dark .qs-index__title {+ color: #f4f4f4;+}++.dark .qs-index__description {+ color: #9f9f9f;+}++.qs-index__jump {+ margin-bottom: 2.5rem;+}++.qs-index__jump-label {+ display: block;+ margin-bottom: 0.75rem;+ color: #6f6f6f;+ font-size: 0.8125rem;+ font-weight: 500;+}++.qs-index__jump-links {+ display: flex;+ flex-wrap: wrap;+ gap: 0.5rem;+}++.qs-index__jump-links + .qs-index__jump-links {+ margin-top: 0.5rem;+}++.qs-index__jump-chip {+ display: inline-flex;+ align-items: center;+ gap: 0.5rem;+ padding: 0.375rem 0.75rem;+ border: 1px solid #ebebeb;+ background: #fbfbfa;+ color: #5c5c5c;+ font-size: 0.8125rem;+ font-weight: 500;+ line-height: 1.5;+ text-decoration: none;+ transition: border-color 0.2s, background-color 0.2s;+}++.qs-index__jump-chip::before {+ content: "";+ width: 0.5rem;+ height: 0.5rem;+ background: var(--qs-chip-color, #cfcfcf);+ flex-shrink: 0;+}++.qs-index__jump-chip--secrets { --qs-chip-color: #56a600; }+.qs-index__jump-chip--scanning { --qs-chip-color: #8b2fd0; }+.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--identity { --qs-chip-color: #cfcfcf; }+.qs-index__jump-chip--networking { --qs-chip-color: #cfcfcf; }+.qs-index__jump-chip--self-hosting { --qs-chip-color: #cfcfcf; }++.qs-index__jump-chip:hover {+ border-color: var(--qs-chip-color, #cfcfcf);+ background-color: color-mix(in srgb, var(--qs-chip-color, #cfcfcf) 7%, #fbfbfa);+}++.qs-index__jump-chip:focus-visible {+ outline: 2px solid var(--qs-chip-color, #5f7000);+ outline-offset: 3px;+}++.dark .qs-index__jump-label {+ color: #9f9f9f;+}++.dark .qs-index__jump-chip {+ background: #101114;+ border-color: #1e1f24;+ color: #b4b4b4;+}++.dark .qs-index__jump-chip--secrets { --qs-chip-color: #9ee067; }+.dark .qs-index__jump-chip--scanning { --qs-chip-color: #b056f0; }+.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--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; }++.dark .qs-index__jump-chip:hover {+ border-color: var(--qs-chip-color, #3a3f47);+ background-color: color-mix(in srgb, var(--qs-chip-color, #3a3f47) 10%, #101114);+}++.qs-index__section {+ margin: 2.5rem 0;+}++.qs-index__section--secrets { --qs-accent: #56a600; }+.qs-index__section--scanning { --qs-accent: #8b2fd0; }+.qs-index__section--certificates { --qs-accent: #a16207; }+.qs-index__section--kms { --qs-accent: #109e7a; }+.qs-index__section--pam { --qs-accent: #dc2626; }+.qs-index__section--identity,+.qs-index__section--networking,+.qs-index__section--self-hosting {+ --qs-accent: #5c5c5c;+}++.qs-index__section h2 {+ scroll-margin-top: 9rem;+ font-size: 1.1875rem;+ font-weight: 600;+ letter-spacing: -0.01em;+ color: #171718;+ margin: 0 0 0.375rem;+ padding: 0 0 0 0.75rem;+ border: 0;+ border-left: 3px solid var(--qs-accent);+ line-height: 1.3;+}++.qs-index__section-link {+ display: inline-flex;+ align-items: center;+ gap: 0.375rem;+ color: inherit;+ text-decoration: none;+ transition: color 0.15s;+}++.qs-index__section-link:hover {+ color: var(--qs-accent);+}++.qs-index__section-arrow {+ flex: none;+ opacity: 0;+ transform: translateX(-4px);+ transition: opacity 0.2s, transform 0.2s;+}++.qs-index__section-link:hover .qs-index__section-arrow,+.qs-index__section-link:focus-visible .qs-index__section-arrow {+ opacity: 1;+ transform: translateX(0);+}++.qs-index__section-link:focus-visible {+ outline: 2px solid var(--qs-accent);+ outline-offset: 3px;+}++.qs-index__section-desc {+ font-size: 0.875rem;+ color: #6f6f6f;+ margin: 0 0 0.875rem 0;+ padding-left: 0.75rem;+ line-height: 1.55;+}++.qs-index table {+ display: table;+ width: 100%;+ table-layout: fixed;+ border-collapse: collapse;+ margin: 0;+ font-size: 0.875rem;+ line-height: 1.6;+}++.qs-index th,+.qs-index td {+ padding: 0.875rem 1rem;+ border: 0;+ border-bottom: 1px solid #ebebeb;+ text-align: left;+ vertical-align: top;+ overflow-wrap: anywhere;+}++.qs-index th:first-child,+.qs-index td:first-child {+ width: 42%;+}++.qs-index th {+ background: #f7f7f6;+ color: #171718;+ font-size: 0.8125rem;+ font-weight: 600;+}++.qs-index td {+ color: #5c5c5c;+}++.qs-index td a {+ color: #171718;+ font-weight: 600;+ text-decoration: none;+ border-bottom: 1px solid rgb(var(--primary));+ word-wrap: break-word;+}++.qs-index td a:hover {+ border-bottom-width: 2px;+}++.qs-index td a:focus-visible {+ outline: 2px solid currentColor;+ outline-offset: 4px;+}+++.dark .qs-index__section h2 {+ color: #f4f4f4;+}++.dark .qs-index__section-desc {+ color: #9f9f9f;+}++.dark .qs-index__section--secrets { --qs-accent: #9ee067; }+.dark .qs-index__section--scanning { --qs-accent: #b056f0; }+.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--identity,+.dark .qs-index__section--networking,+.dark .qs-index__section--self-hosting {+ --qs-accent: #cfcfcf;+}++.dark .qs-index th {+ color: #f4f4f4;+ background: #141518;+}++.dark .qs-index th,+.dark .qs-index td {+ border-bottom-color: #292a2f;+}++.dark .qs-index td {+ color: #b4b4b4;+}++.dark .qs-index td a {+ color: #ffffff;+ border-bottom-color: rgb(var(--primary-light));+}++@media (max-width: 640px) {+ .qs-index {+ padding: 2rem 1rem 3rem;+ }++ .qs-index__title {+ font-size: 1.875rem;+ }++ .qs-index th,+ .qs-index td {+ padding: 0.75rem 0.5rem;+ }+}+.chat-assistant-floating-input {visibility: hidden !important;}