Installing with Helm
Platz ships as a single Helm chart that installs five backend workers (API, k8s-agent, chart-discovery, resource-sync, status-updates) plus the web frontend. Everything runs in one Kubernetes namespace and connects to:
Installing with Terraform
The terraform-aws-platzio module is
Database
Platz keeps all of its state in a single PostgreSQL database — users, envs, clusters, deployments, tasks, secrets, k8s resource snapshots, helm chart metadata. Every backend worker connects to the same database; there is no separate cache, queue, or event store. PostgreSQL's LISTEN/NOTIFY is what powers the live UI updates.
Single EKS cluster
This guide walks through the simplest production-grade topology: Platz runs in one
Multiple EKS clusters
The recommended production topology separates the control cluster (where Platz
Multiple AWS accounts
When your EKS clusters are spread across several AWS accounts — a common setup where each
Security considerations
Platz is a control plane with real power: it can install, upgrade, and delete Helm