How it works

The tembo Helm chart installs the whole platform in one namespace. Agent sessions don’t run in the cluster: they run in virtual machines on agent hosts, which the chart’s host controller launches next to it (see Agent hosts).

​

Services in the cluster

The chart generates the secrets the platform needs once, such as signing and encryption keys and the GitHub webhook secret, and keeps them across upgrades.

​

Postgres and Redis

By default, Postgres and Redis run as single pods in your cluster, which suits evaluation. For production, use managed services, such as Amazon RDS and ElastiCache. Agent hosts run outside the cluster and connect to both directly. See Postgres and Redis.

​

Object storage

Tembo keeps project images, session snapshots, file uploads and agent assets in one object storage bucket. On AWS, the Terraform module creates an S3 bucket and its access.

​

Configuration

Your Helm values describe the whole install (see Configuration). The chart passes the same configuration to agent hosts through a Kubernetes Secret, which each host reads when it starts. Model providers, workspaces and members are set up in the Tembo app.

---

​

Need Help?

If you run into any issues, contact support@tembo.io.