> ## Documentation Index
> Fetch the complete documentation index at: https://docs.prisme.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Installation Overview

> Five sequential steps to install a self-hosted Prisme.ai platform, each linking to the next.

A self-hosted Prisme.ai install has five sequential steps. Each step links to the next, so you can follow the whole flow without jumping around the menu.

<Steps>
  <Step title="Plan">
    Review the [Requirements](/self-hosting/requirements) and [Resources & Autoscaling](/self-hosting/kubernetes/resources) to understand what to provision.

    → Next: provision your cloud environment.
  </Step>

  <Step title="Provision the cloud environment">
    Before installing Prisme.ai with Helm, you need a Kubernetes cluster, managed databases, object storage and a load balancer in place. Provider-specific instructions:

    * [AWS](/self-hosting/cloud/aws) — EKS, RDS / Atlas, OpenSearch, ElastiCache, S3 (+ optional CloudFront), EFS, ALB.
    * [Azure](/self-hosting/cloud/azure) — AKS, CosmosDB / Postgres Flexible Server, Elastic Cloud, Azure Managed Redis, Blob, Azure Files ZRS, AGIC.
    * [GCP](/self-hosting/cloud/gcp) — GKE, Cloud SQL / Atlas, Memorystore, GCS, Filestore regional, GKE Ingress.
    * [OpenShift](/self-hosting/cloud/openshift) — OCP cluster, operators for Mongo / Redis / ES, ODF for object + file storage, Routes.

    Per-engine details (versions, sizing, least privileges): [Databases](/self-hosting/databases/overview).

    → Next: install Prisme.ai with Helm.
  </Step>

  <Step title="Install with Helm">
    [Install with Helm](/self-hosting/kubernetes/helm) is the single source of truth for the Helm-level configuration. It covers both namespaces (`core` and `apps`), the critical values, secrets and ingress.

    The values you set here wire Prisme.ai to the cloud resources from step 2 (DB URLs, S3 buckets, ingress hostnames, etc.).

    Most of the tuning that follows — auth, mail, retention, resource requests, HPA targets, SSO, custom code — lives in the **same `prismeai-core-values.yaml` / `prismeai-apps-values.yaml`** and is applied by re-running `helm upgrade -f <values>`.

    → Next: tune the same Helm values and install products.
  </Step>

  <Step title="Tune the platform">
    All four bullets below are additional **Helm values** layered onto the files from step 3 — edit, then `helm upgrade -f` to apply.

    * [Configuration](/self-hosting/kubernetes/configuration) — the most important post-install settings (auth, mail, retention, upload limits, crawler, runtime).
    * [Resources & Autoscaling](/self-hosting/kubernetes/resources) — pick Balanced or Performance, HPA targets, per-service requests/limits.
    * [Environment variables reference](/self-hosting/kubernetes/environment-variables) — full per-service env-var list, all settable under `<service>.env` in your values file.
    * [Enterprise Services](/self-hosting/entreprise/authentication) — SSO, RBAC, custom code, crawler.

    → Next: operate and install products.
  </Step>

  <Step title="Operate">
    * [Install products](/self-hosting/install-products) — provision the platform workspaces (Governe, LLM Gateway, Storage, Agent Creator, Insights, Builder, Helper Agents).
    * [Migration to v27](/self-hosting/operations/migration-v27) if you're upgrading from a legacy install.
    * [Updates](/self-hosting/operations/updates), [Backup](/self-hosting/operations/backup), [Scaling](/self-hosting/operations/scaling).
    * [Network Policies](/self-hosting/kubernetes/network-policies) — minimal service, database and external egress flows for default-deny clusters (applied as separate Kubernetes resources, not via Helm values).
  </Step>
</Steps>