Update docs to be multi-product

docs/documentation/getting-started/concepts/audit-logs.mdx

@@ -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

docs/documentation/getting-started/concepts/client-integrations.mdx

@@ -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.

docs/documentation/getting-started/concepts/deployment-models.mdx

@@ -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>

docs/documentation/getting-started/concepts/platform-hierarchy.mdx

@@ -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.
+
+![organization](/images/platform/organization/organization.png)
+
+## 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.
+
+![organization projects](/images/platform/organization/organization-projects.png)
+
+## 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.

docs/documentation/getting-started/concepts/platform-iam.mdx

@@ -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).