Skip to main content
Truefoundry Control-Plane ships as a helm chart (https://github.com/truefoundry/infra-charts/tree/main/charts/truefoundry) that can be deployed on any Kubernetes cluster. The installation process is different based on if you are spinning up a Kubernetes cluster from scratch or using an existing cluster to install the control-plane.
Please read the control-plane architecture to understand the key components of the control plane.

Control-plane Dependencies

The TrueFoundry control-plane requires a Kubernetes cluster, a Postgres database, and Blob Storage. Below is a table outlining popular options for each, along with typical cost ranges. Actual cost may vary depending on region, resource choice, scale, and provider pricing. All costs are rough monthly estimates.
ComponentSupported OptionsTypical Cost Range (USD/month)Remarks
Kubernetes Cluster
K8s version >= 1.28
AWS EKS
GCP GKE
Azure AKS
Self-Managed K8s
$400-1200 (depending on if we want AI deployment or AI Gateway or both features)Kubernetes cluster is required to host the control-plane helm chart which brings up all the components.
Postgres Database
Postgres version >= 13, Storage size: 30GB
-AWS RDS/Postgres (db.t4g.medium)
- GCP CloudSQL (db-custom-1-3840)
-Azure Postgres (GP_Standard_D4ds_v5)
-Self-hosted Postgres
$200-400 (Depending on the cloud provider and the instance type)The database stores all the data including deployment configuration, model registry metadata, user information, gateway configuration, etc.
Blob StorageAWS S3
GCP Cloud Storage
Azure Blob Storage
Any S3-compatible storage like Minio
Depends on storage (Provision for 200GB min)Stores ML models and artifacts, Gateway request and response logs
Domain NameAny provider (Route53, Cloudflare, etc.)Typically free with domain or varies per providerWe need one domain to be pointed to the control-plane dashboard so that the UI can be accessed over the browser.

Control-Plane Compute Requirements

The control-plane has different components which can be disabled or enabled based on your needs. The control-plane helm chart also has the Gateway plane bundled with it in case you want to deploy it. Here’s the compute requirements based on the features you want to enable in the control-plane.
  • Small (Dev)
  • Medium (Prod)
  • Large (Prod)
The small tier is recommended for POC/dev purposes. Here all the components are deployed on Kubernetes and in non HA mode (single replica). This is suitable if you are just testing out the different features of Truefoundry.
This setup brings up 1 replica of the services and is not highly-available. It can enable you to test the features but we do not recommend this for production mode.
ConfigurationCPU / MemoryBlock Storage PVMin NodesCost
AI Deployment + AI Gateway2 vCPU / 8GB60GB
2
Pods should be spread over min 2 nodes
~ $120 pm
AI Deployment Only1 vCPU / 4GB50GB
2
Pods should be spread over min 2 nodes
~ $60 pm
AI Gateway Only2 vCPU / 8GB60GB
2
Pods should be spread over min 2 nodes
~ $120 pm
AI Gateway + Gateway Plane3 vCPU / 10GB60GB
2
Pods should be spread over min 2 nodes
~ $120 pm
Postgres
(Deployed on Kubernetes)
0.5 vCPU / 0.5GB5GB
Blob Storage
(S3 Compatible)
20GB

Deploying Control-Plane

There are different scenarios to install the control-plane depending on if you are spinning up a new Kubernetes cluster or using an existing cluster. 1. Spin up a new Kubernetes cluster and deploy control-plane Truefoundry provides Terraform code to spin up a new Kubernetes cluster and deploy the control-plane on it. You can customize the network configuration and Kubernetes configuration as per your needs. Please follow the guides below: 2. Deploy control-plane on an existing Kubernetes cluster Install the control-plane helm chart using helm install. Follow this guide to install the control-plane helm chart.