Start with install notes or jump straight into the API.

Operations

Install

A hev layer install has two stages. Terraform provisions the required AWS resources: IAM, S3, ECR, networking, cost-read roles, and, for the recommended path, a fresh EKS cluster. Helm installs the gateway, operator, and document cache into that cluster and wires them to the AWS resources Terraform produced.

You can skip Terraform if you already have the AWS resources hev layer needs. At minimum, provide an S3 bucket and gateway IRSA role for snapshots and history. For the full operations surface, also provide dashboard cost-read IAM, image registry locations, and cluster-level components equivalent to the Terraform outputs.

Terraform Provision IAM, S3, ECR, cost access, and the recommended EKS cluster for hev layer. Helm Install Install the gateway, operator, and document cache into your cluster. Operator Overview How the layer-operator reconciles Index, InfraRules, Pipeline, and Function CRDs.

What ships in 0.1

The 0.1 install is single-tenant: one Helm release per environment, one Turbopuffer credential per release, one S3 bucket for snapshot and history data. Multi-tenant gateway scoping is on the 0.2+ roadmap and is not exposed at the install layer yet.