Plan
Review the Requirements and Resources & Autoscaling to understand what to provision.→ Next: provision your cloud environment.
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 — EKS, RDS / Atlas, OpenSearch, ElastiCache, S3 (+ optional CloudFront), EFS, ALB.
- Azure — AKS, CosmosDB / Postgres Flexible Server, Elastic Cloud, Azure Managed Redis, Blob, Azure Files ZRS, AGIC.
- GCP — GKE, Cloud SQL / Atlas, Memorystore, GCS, Filestore regional, GKE Ingress.
- OpenShift — OCP cluster, operators for Mongo / Redis / ES, ODF for object + file storage, Routes.
Install with Helm
Install with 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.).→ Next: tune resources and configure products.Tune the platform
- Configuration — the most important post-install settings (auth, mail, retention, upload limits, crawler, runtime).
- Network Policies — minimal service, database and external egress flows for default-deny clusters.
- Resources & Autoscaling — pick Balanced or High-throughput, HPA targets.
- Environment variables reference — full per-service env-var list.
- Enterprise Services — SSO, RBAC, custom code, crawler.
Operate
- Install products — provision the platform workspaces (Governe, LLM Gateway, Storage, Agent Creator, Insights, Builder, Helper Agents).
- Migration to v27 if you’re upgrading from a legacy install.
- Updates, Backup, Scaling.