mirror of
https://github.com/awatertrevi/infisical.git
synced 2026-09-22 13:39:35 +00:00
Update docs to be multi-product
This commit is contained in:
Tuan Dang
40
docs/documentation/getting-started/concepts/audit-logs.mdx
Normal file
40
docs/documentation/getting-started/concepts/audit-logs.mdx
Normal file
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: "Audit Logs"
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
Audit logs enable teams to:
|
||||
|
||||
- Monitor access and changes to secrets, certificates, and infrastructure.
|
||||
- Investigate incidents with full context around who did what, when, and how.
|
||||
- Meet compliance and governance requirements with structured activity records.
|
||||
|
||||
To learn more, refer to the [audit logs documentation](/documentation/platform/audit-logs).
|
||||
|
||||
## Log Coverage
|
||||
|
||||
Infisical tracks dozens of event types across the platform — including secret access, permission changes, certificate issuance, SSH session activity, and identity management.
|
||||
|
||||
Each audit entry includes structured fields that make it easy to search, filter, and correlate across systems. For example:
|
||||
|
||||
- Event Type: Action that occurred (e.g., `create-secret`, `issue-ssh-cert`).
|
||||
- Actor: Who performed the action (user or machine identity).
|
||||
- Resource: What was affected (e.g., project, secret, certificate).
|
||||
- Context: IP address, user agent, permissions, and more.
|
||||
|
||||
## External Log Streaming
|
||||
|
||||
For centralized monitoring and long-term retention, Infisical supports [audit log streaming](/documentation/platform/audit-log-streams/audit-log-streams) to external systems.
|
||||
|
||||
You can forward logs to SIEM platforms, storage buckets, or observability stacks using JSON-based collectors. Infisical integrates well with tools like [Fluent Bit](https://localhost:3000/documentation/platform/audit-log-streams/audit-log-streams-with-fluentbit#deploy-fluent-bit), enabling teams to route logs to destinations such as:
|
||||
|
||||
- AWS S3
|
||||
- Elasticsearch
|
||||
- Splunk
|
||||
- Datadog
|
||||
- Cloud-native log pipelines
|
||||
@@ -0,0 +1,31 @@
|
||||
---
|
||||
title: "Client Ecosystem"
|
||||
sidebarTitle: "Client Ecosystem"
|
||||
description: "Get an overview of the CLI, SDKs, agents, APIs, and integrations that interact with Infisical."
|
||||
---
|
||||
|
||||
Infisical provides a flexible interface for integrating into development workflows and infrastructure. Around it is a rich ecosystem of clients and integrations that allow users and systems to interact with Infisical across any environment.
|
||||
|
||||
These clients enable access to secrets, certificates, and other resources from wherever they’re needed—whether that’s a developer’s terminal, a CI/CD pipeline, or a running Kubernetes workload.
|
||||
|
||||
## Available Clients and Interfaces
|
||||
|
||||
Infisical offers a non-exhaustive set of clients and interfaces to support a wide range of use cases:
|
||||
|
||||
- [CLI](/cli/overview): A powerful command-line interface for developers and operators to interact with Infisical from local or automated environments. Commonly used for secret access, SSH credential issuance, and more.
|
||||
|
||||
- [SDKs](/sdks/overview): Official client libraries for languages like Go, Node.js, and Python make it easy to integrate Infisical directly into applications and internal tooling.
|
||||
|
||||
- [HTTP API](/api-reference/overview/introduction): A fully documented RESTful API powers all core functionality and enables advanced or custom integrations.
|
||||
|
||||
- [Agents](/integrations/platforms/infisical-agent): Lightweight background processes that can fetch and sync secrets or credentials into local environments, containers, or file systems.
|
||||
|
||||
- [Kubernetes Operator](/integrations/platforms/kubernetes/overview): A native controller that syncs Infisical secrets into Kubernetes as native Secrets, and supports secure workload integration.
|
||||
|
||||
- [External Secrets Operator (ESO)](https://external-secrets.io/latest/provider/infisical): Allows Infisical to act as a backend provider for syncing secrets into Kubernetes `Secret` objects using the widely adopted External Secrets Operator.
|
||||
|
||||
- [Kubernetes PKI Issuer](/documentation/platform/pki/pki-issuer): A controller that issues X.509 certificates from Infisical PKI using the cert-manager Issuer and Certificate CRDs.
|
||||
|
||||
- [Secret Syncs](/integrations/secret-syncs/overview): Native integrations to forward secrets to services like GitHub, GitLab, AWS Secrets Manager, Vercel, and more.
|
||||
|
||||
This modular ecosystem lets teams use Infisical alongside their existing stack—without requiring opinionated workflows or lock-in.
|
||||
@@ -0,0 +1,52 @@
|
||||
---
|
||||
title: "Using Infisical: Cloud or Self-Hosted"
|
||||
sidebarTitle: "Cloud vs. Self-Host"
|
||||
description: "Choose between Infisical Cloud or a self-managed deployment"
|
||||
---
|
||||
|
||||
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.
|
||||
|
||||
## Infisical Cloud
|
||||
|
||||
Infisical Cloud is our managed service found at [app.infisical.com](https://app.infisical.com). It includes automated updates, availability guarantees, and secure infrastructure operations.
|
||||
|
||||
For most teams, Infisical Cloud is the recommended way to get started. It simplifies adoption by removing the need to manage deployment, scaling, or maintenance internally.
|
||||
|
||||
Use this if:
|
||||
|
||||
- You prefer not to operate infrastructure or handle upgrades
|
||||
- You require a secure, production-grade hosted service
|
||||
- You want to adopt Infisical with minimal operational overhead
|
||||
|
||||
<Info>
|
||||
<p>
|
||||
By default, Infisical Cloud is a secure, multi-tenant service. For
|
||||
enterprises with stricter isolation or regulatory needs, dedicated cloud
|
||||
instances are available.
|
||||
</p>
|
||||
<p>Contact sales@infisical.com to learn more.</p>
|
||||
</Info>
|
||||
|
||||
## Self-Hosted Infisical
|
||||
|
||||
Infisical can also be deployed and managed within your own infrastructure. This approach provides full control over platform configuration, data storage, and operational security. In this model, your team is responsible for maintaining uptime, monitoring, patching, and integrations.
|
||||
|
||||
Use this if:
|
||||
|
||||
- You require complete control over data, deployment, and security posture
|
||||
- Your compliance model mandates self-managed or on-premise systems
|
||||
- You need to tightly integrate with internal tooling and infrastructure
|
||||
|
||||
Infisical supports multiple deployment methods, including [Docker](/self-hosting/deployment-options/standalone-infisical), [Docker Compose](/self-hosting/deployment-options/docker-compose), [Kubernetes](/self-hosting/deployment-options/kubernetes-helm), and [Linux package](/self-hosting/deployment-options/native/linux-package/installation).
|
||||
|
||||
To learn more, refer to the [self-hosting documentation](/self-hosting/overview).
|
||||
|
||||
<Info>
|
||||
<p>
|
||||
The open-source core is available under the MIT license. Additional
|
||||
enterprise features and support are available with a commercial license.
|
||||
</p>
|
||||
<p>Contact sales@infisical.com to learn more.</p>
|
||||
</Info>
|
||||
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: "Platform Hierarchy"
|
||||
sidebarTitle: "Platform Hierarchy"
|
||||
description: "Understand how organizations and projects are structured in Infisical."
|
||||
---
|
||||
|
||||
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.
|
||||
|
||||
## Organizations
|
||||
|
||||
An [organization](/documentation/platform/organization) typically represents a company or high-level entity (e.g. Acme Corp). It acts as the umbrella for all projects, members, and billing settings.
|
||||
|
||||
[Users](/documentation/platform/identities/user-identities) are invited to an organization and assigned [organization-level roles](/documentation/platform/access-controls/role-based-access-controls#organization-level-access-controls) that determine what they can manage—such as members, machine identities, and billing details.
|
||||
|
||||
|
||||
|
||||
## Projects
|
||||
|
||||
A [project](/documentation/platform/project) belongs to an organization and defines a specific scope of work. Each project has a product type such as Secrets Management, SSH, or PKI that determines what features are available in that project.
|
||||
|
||||
For example:
|
||||
|
||||
- A Secrets Management project manages application secrets across environments.
|
||||
|
||||
- An SSH project enables certificate-based access to infrastructure.
|
||||
|
||||
- A PKI project manages certificate authorities and X.509 certificate workflows.
|
||||
|
||||
Users are added to a project and assigned [project-level roles](/documentation/platform/access-controls/role-based-access-controls#project-level-access-controls) that determine what they can manage—such as secrets, access policies, or certificate authorities. A user can have different roles across projects, allowing for flexible and fine-grained access control that reflects how teams operate in practice.
|
||||
|
||||
|
||||
|
||||
## Key Characteristics
|
||||
|
||||
- Projects are isolated in terms of configuration, permissions, and product workflows.
|
||||
|
||||
- Access is managed independently at both the organization and project level.
|
||||
|
||||
- All projects within an organization share the same billing and user directory.
|
||||
|
||||
Teams can adopt Infisical incrementally—starting with one product and expanding as needed.
|
||||
29
docs/documentation/getting-started/concepts/platform-iam.mdx
Normal file
29
docs/documentation/getting-started/concepts/platform-iam.mdx
Normal file
@@ -0,0 +1,29 @@
|
||||
---
|
||||
title: "Platform Identity and Access Management"
|
||||
sidebarTitle: "Platform IAM"
|
||||
description: "Understand how users, machine identities, roles, and permissions are managed."
|
||||
---
|
||||
|
||||
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:
|
||||
|
||||
- [User identities](/documentation/platform/identities/user-identities): Represent individuals such as developers or administrators that typically access the platform via browser.
|
||||
|
||||
- [Machine identities](/documentation/platform/identities/machine-identities): Represent systems such as CI pipelines or applications that programmatically interact with the platform.
|
||||
|
||||
Each identity is granted access based on its assigned roles and permissions and must authenticate with the platform in order to access any resources.
|
||||
|
||||
To learn more, refer to the [identities documentation](/documentation/platform/identities/overview).
|
||||
|
||||
## Roles and Access
|
||||
|
||||
Infisical provides a robust and flexible access control system. The primary authorization mechanism is [role-based access control (RBAC)](/documentation/platform/access-controls/role-based-access-controls), where identities are assigned roles at two access control levels:
|
||||
|
||||
- [Organization-level access control](/documentation/platform/access-controls/role-based-access-controls#organization-level-access-controls): Control billing, member management, and platform-wide settings
|
||||
|
||||
- [Project-level access control](/documentation/platform/access-controls/role-based-access-controls#project-level-access-controls): Control access to specific product resources like secrets, SSH hosts, or certificates
|
||||
|
||||
Beyond RBAC, Infisical also supports additional project-level permissioning features, [including attribute-based access control (ABAC)](/documentation/platform/access-controls/abac/overview), [temporary access grants](/documentation/platform/access-controls/temporary-access), and [additional privileges](/documentation/platform/access-controls/additional-privileges) for select project types.
|
||||
|
||||
To learn more, refer to the [access control documentation](/documentation/platform/access-controls/overview).
|
||||
@@ -1,107 +0,0 @@
|
||||
---
|
||||
mode: 'custom'
|
||||
---
|
||||
|
||||
export function openSearch() {
|
||||
document.getElementById('search-bar-entry').click();
|
||||
}
|
||||
|
||||
<div
|
||||
className="relative w-full flex items-center justify-center"
|
||||
style={{ height: '24rem', backgroundColor: '#1F1F33', overflow: 'hidden' }}
|
||||
>
|
||||
<div style={{ flex: 'none' }}>
|
||||
<img
|
||||
src="/images/background.png"
|
||||
style={{ height: '68rem', width: '68rem' }}
|
||||
/>
|
||||
</div>
|
||||
<div style={{ position: 'absolute', textAlign: 'center' }}>
|
||||
<div
|
||||
style={{
|
||||
color: 'white',
|
||||
fontWeight: '400',
|
||||
fontSize: '48px',
|
||||
margin: '0',
|
||||
}}
|
||||
>
|
||||
Infisical Documentation
|
||||
</div>
|
||||
<p
|
||||
style={{
|
||||
color: 'white',
|
||||
fontWeight: '400',
|
||||
fontSize: '20px',
|
||||
opacity: '0.7',
|
||||
}}
|
||||
>
|
||||
What can we help you build?
|
||||
</p>
|
||||
<button
|
||||
type="button"
|
||||
className="mx-auto w-full flex items-center text-sm leading-6 shadow-sm text-gray-400 bg-white ring-1 ring-gray-400/20 focus:outline-primary"
|
||||
id="home-search-entry"
|
||||
style={{
|
||||
maxWidth: '24rem',
|
||||
borderRadius: '4px',
|
||||
marginTop: '3rem',
|
||||
paddingLeft: '0.75rem',
|
||||
paddingRight: '0.75rem',
|
||||
paddingTop: '0.75rem',
|
||||
paddingBottom: '0.75rem',
|
||||
}}
|
||||
onClick={openSearch}
|
||||
>
|
||||
<svg
|
||||
className="h-4 w-4 ml-1.5 mr-3 flex-none bg-gray-500 hover:bg-gray-600 dark:bg-white/50 dark:hover:bg-white/70"
|
||||
style={{
|
||||
maskImage:
|
||||
'url("https://mintlify.b-cdn.net/v6.5.1/solid/magnifying-glass.svg")',
|
||||
maskRepeat: 'no-repeat',
|
||||
maskPosition: 'center center',
|
||||
}}
|
||||
/>
|
||||
Start a chat with us...
|
||||
</button>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div style={{marginTop: '6rem', marginBottom: '8rem', maxWidth: '70rem', marginLeft: 'auto',
|
||||
marginRight: 'auto', paddingLeft: '1.25rem',
|
||||
paddingRight: '1.25rem' }}>
|
||||
|
||||
<div
|
||||
style={{
|
||||
textAlign: 'center',
|
||||
fontSize: '24px',
|
||||
fontWeight: '600',
|
||||
color: '#121142',
|
||||
marginBottom: '3rem',
|
||||
}}
|
||||
>
|
||||
Choose a topic below or simply{' '}
|
||||
<span className="text-primary">get started</span>
|
||||
</div>
|
||||
|
||||
<CardGroup cols={3}>
|
||||
<Card title="Getting Started" icon="book-open" href="/guides">
|
||||
Practical guides and best practices to get you up and running quickly.
|
||||
</Card>
|
||||
<Card title="API Reference" icon="code-simple" href="/reference">
|
||||
Comprehensive details about the Infisical API.
|
||||
</Card>
|
||||
<Card title="Security" icon="code-simple" href="/reference">
|
||||
Learn more about Infisical's architecture and underlying security.
|
||||
</Card>
|
||||
<Card title="Self-hosting" icon="link-simple" href="/integrations">
|
||||
Read self-hosting instruction for Infisical.
|
||||
</Card>
|
||||
<Card title="Integrations" icon="link-simple" href="/integrations">
|
||||
Infisical's growing number of third-party integrations.
|
||||
</Card>
|
||||
<Card title="Releases" icon="party-horn" href="/release-notes">
|
||||
News about features and changes in Pinecone and related tools.
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
||||
</div>
|
||||
@@ -1,106 +1,40 @@
|
||||
---
|
||||
title: "What is Infisical?"
|
||||
sidebarTitle: "What is Infisical?"
|
||||
description: "An Introduction to the Infisical secret management platform."
|
||||
description: "The open source platform for managing secrets, certificates, and secure infrastructure access."
|
||||
---
|
||||
|
||||
**[Infisical](https://infisical.com)** is the open source secret management platform that developers use to centralize their application configuration and secrets like API keys and database credentials as well as manage their internal PKI. Additionally, developers use Infisical to prevent secrets leaks to git and securely share secrets amongst engineers.
|
||||
## What is Infisical?
|
||||
|
||||
[Infisical](https://infisical.com) is the [open source](https://github.com/Infisical/infisical), all-in-one platform for secrets, certificates, and privileged access management.
|
||||
|
||||
It provides modern security workflows — including secrets rotation, dynamic credentials, access approvals, and SSH certificate-based access — 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.
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card
|
||||
title="Infisical Cloud"
|
||||
href="https://app.infisical.com/signup"
|
||||
icon="cloud"
|
||||
color="#000000"
|
||||
>
|
||||
Get started with Infisical Cloud in just a few minutes.
|
||||
</Card>
|
||||
<Card
|
||||
href="/self-hosting/overview"
|
||||
title="Self-hosting"
|
||||
icon="server"
|
||||
color="#000000"
|
||||
>
|
||||
Self-host Infisical on your own infrastructure.
|
||||
</Card>
|
||||
</CardGroup>
|
||||
## Why use Infisical?
|
||||
|
||||
## Why Infisical?
|
||||
Managing secrets, credentials, and infrastructure access is a critical concern for engineering teams. As infrastructure scales and environments become more complex, [secrets start to sprawl](https://infisical.com/blog/what-is-secret-sprawl) — across codebases, CI/CD pipelines, configuration files, and cloud services. This makes them difficult to track, rotate, and secure.
|
||||
|
||||
Infisical helps developers achieve secure centralized secret management and provides all the tools to easily manage secrets in various environments and infrastructure components. In particular, here are some of the most common points that developers mention after adopting Infisical:
|
||||
Without proper management, secret sprawl turns into risk: hardcoded credentials, unrotated keys, fragmented access controls that attackers can exploit amongst other things.
|
||||
|
||||
- Streamlined **local development** processes (switching .env files to [Infisical CLI](/cli/commands/run) and removing secrets from developer machines).
|
||||
- **Best-in-class developer experience** with an easy-to-use [Web Dashboard](/documentation/platform/project).
|
||||
- Simple secret management inside **[CI/CD pipelines](/integrations/cicd/githubactions)** and staging environments.
|
||||
- Secure and compliant secret management practices in **[production environments](/sdks/overview)**.
|
||||
- **Facilitated workflows** around [secret change management](/documentation/platform/pr-workflows), [access requests](/documentation/platform/access-controls/access-requests), [temporary access provisioning](/documentation/platform/access-controls/temporary-access), and more.
|
||||
- **Improved security posture** thanks to [secret scanning](/cli/scanning-overview), [granular access control policies](/documentation/platform/access-controls/overview), [automated secret rotation](https://infisical.com/docs/documentation/platform/secret-rotation/overview), and [dynamic secrets](/documentation/platform/dynamic-secrets/overview) capabilities.
|
||||
Infisical addresses this challenge by providing an all-in-one platform and workflows to:
|
||||
|
||||
## How does Infisical work?
|
||||
- Securely store and manage application secrets from development to production.
|
||||
- Scan code and pipelines for exposed credentials.
|
||||
- Automate X.509 certificate issuance and renewal.
|
||||
- Manage SSH access using short-lived, policy-driven certificates.
|
||||
- Encrypt and decrypt sensitive data with centralized key control.
|
||||
- Audit every access, credential use, and change.
|
||||
|
||||
To make secret management effortless and secure, Infisical follows a certain structure for enabling secret management workflows as defined below.
|
||||
Infisical is designed to integrate cleanly into your stack—improving security without adding complexity.
|
||||
|
||||
**Identities** in Infisical are users or machine which have a certain set of roles and permissions assigned to them. Such identities are able to manage secrets in various **Clients** throughout the entire infrastructure. To do that, identities have to verify themselves through one of the available **Authentication Methods**.
|
||||
## What does Infisical include?
|
||||
|
||||
As a result, the 3 main concepts that are important to understand are:
|
||||
Infisical consists of several tightly integrated products, each designed to solve a specific part of the infrastructure security surface:
|
||||
|
||||
- **[Identities](/documentation/platform/identities/overview)**: users or machines with a set permissions assigned to them.
|
||||
- **[Clients](/integrations/platforms/kubernetes)**: Infisical-developed tools for managing secrets in various infrastructure components (e.g., [Kubernetes Operator](/integrations/platforms/kubernetes), [Infisical Agent](/integrations/platforms/infisical-agent), [CLI](/cli/usage), [SDKs](/sdks/overview), [API](/api-reference/overview/introduction), [Web Dashboard](/documentation/platform/organization)).
|
||||
- **[Authentication Methods](/documentation/platform/identities/universal-auth)**: ways for Identities to authenticate inside different clients (e.g., SAML SSO for Web Dashboard, Universal Auth for Infisical Agent, AWS Auth etc.).
|
||||
|
||||
## How to get started with Infisical?
|
||||
|
||||
Depending on your use case, it might be helpful to look into some of the resources and guides provided below.
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card
|
||||
href="../../cli/overview"
|
||||
title="Command Line Interface (CLI)"
|
||||
icon="square-terminal"
|
||||
color="#000000"
|
||||
>
|
||||
Inject secrets into any application process/environment.
|
||||
</Card>
|
||||
<Card
|
||||
title="SDKs"
|
||||
href="/documentation/getting-started/sdks"
|
||||
icon="boxes-stacked"
|
||||
color="#000000"
|
||||
>
|
||||
Fetch secrets with any programming language on demand.
|
||||
</Card>
|
||||
<Card
|
||||
href="../../integrations/platforms/docker-intro"
|
||||
title="Docker"
|
||||
icon="docker"
|
||||
color="#000000"
|
||||
>
|
||||
Inject secrets into Docker containers.
|
||||
</Card>
|
||||
<Card
|
||||
href="../../integrations/platforms/kubernetes"
|
||||
title="Kubernetes"
|
||||
icon="server"
|
||||
color="#000000"
|
||||
>
|
||||
Fetch and save secrets as native Kubernetes secrets.
|
||||
</Card>
|
||||
<Card
|
||||
href="/documentation/getting-started/api"
|
||||
title="REST API"
|
||||
icon="cloud"
|
||||
color="#000000"
|
||||
>
|
||||
Fetch secrets via HTTP request.
|
||||
</Card>
|
||||
<Card
|
||||
href="/integrations/overview"
|
||||
title="Native Integrations"
|
||||
icon="clouds"
|
||||
color="#000000"
|
||||
>
|
||||
Explore integrations for GitHub, Vercel, AWS, and more.
|
||||
</Card>
|
||||
</CardGroup>
|
||||
- [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.
|
||||
- [Infisical PKI](/documentation/platform/pki/overview): Issue and manage X.509 certificates using protocols like EST, with support for internal and external CAs.
|
||||
- [Infisical SSH](/documentation/platform/ssh/overview): Provide short-lived SSH access to servers using certificate-based authentication, replacing static keys with policy-driven, time-bound control.
|
||||
- [Infisical KMS](/documentation/platform/kms/overview): Encrypt and decrypt data using centrally managed keys with enforced access policies and full audit visibility.
|
||||
|
||||
72
docs/documentation/getting-started/overview.mdx
Normal file
72
docs/documentation/getting-started/overview.mdx
Normal file
@@ -0,0 +1,72 @@
|
||||
---
|
||||
title: "Overview"
|
||||
sidebarTitle: "Overview"
|
||||
description: "The open source platform for managing secrets, certificates, and secure infrastructure access."
|
||||
---
|
||||
|
||||
<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>
|
||||
|
||||
## Products
|
||||
|
||||
<Columns cols="2">
|
||||
<Card
|
||||
title="Secrets Management"
|
||||
href="/documentation/platform/secrets-mgmt/overview"
|
||||
>
|
||||
Securely store, manage, and control access to sensitive application secrets across your environments.
|
||||
|
||||
</Card>
|
||||
<Card
|
||||
title="Secrets Scanning"
|
||||
href="/documentation/platform/secret-scanning/overview"
|
||||
>
|
||||
Automatically detect and alert on hardcoded secrets in source code, CI pipelines, and infrastructure.
|
||||
</Card>
|
||||
<Card
|
||||
title="Infisical PKI"
|
||||
href="/documentation/platform/pki/overview"
|
||||
>
|
||||
Automate the issuance and management of X.509 certificates across your infrastructure using modern protocols like EST.
|
||||
</Card>
|
||||
<Card
|
||||
title="Infisical SSH"
|
||||
href="/documentation/platform/ssh/overview"
|
||||
>
|
||||
Replace static SSH keys with short-lived SSH certificates to simplify access and improve security.
|
||||
</Card>
|
||||
<Card
|
||||
title="Infisical KMS"
|
||||
href="/documentation/platform/kms/overview"
|
||||
>
|
||||
Encrypt and decrypt sensitive data using a centralized key management system.
|
||||
</Card>
|
||||
</Columns>
|
||||
|
||||
## Additional Resources
|
||||
|
||||
<Columns cols="2">
|
||||
<Card
|
||||
title="CLI Reference"
|
||||
href="/documentation/getting-started/introduction"
|
||||
>
|
||||
Explore Infisical’s command-line interface for managing secrets,
|
||||
certificates, and system operations via terminal.
|
||||
</Card>
|
||||
<Card
|
||||
title="API Reference"
|
||||
href="/documentation/getting-started/introduction"
|
||||
>
|
||||
Browse Infisical’s API documentation to programmatically interact with
|
||||
secrets, access controls, and certificate workflows.
|
||||
</Card>
|
||||
</Columns>
|
||||
<Card title="Self-Hosting" href="/documentation/getting-started/introduction">
|
||||
Learn how to deploy and operate Infisical on your own infrastructure with full
|
||||
control and data ownership.
|
||||
</Card>
|
||||
Reference in New Issue
Block a user