Skip to main content
This section applies only if you’re running Aperium on your own infrastructure. We also offer a fully hosted version of Aperium that we operate for you. If that’s what you’re after, you can skip the deployment docs entirely and reach out to us to get set up.
Aperium runs on Google Cloud through a Terraform, ArgoCD, and Helm setup against a GKE Autopilot cluster, or on an on-premises Kubernetes cluster with a local model server. Pick the path that matches your hosting model and security boundary.

Requirements

Runtimes and services Aperium depends on.

Google Cloud

Deploy the prod-style topology on GKE Autopilot.

On-prem Kubernetes

Run inside your network boundary with in-cluster MCP services and a local LLM.

Environment variables

Every backend and frontend env var, grouped by purpose.

​
Picking a path

  • Google Cloud. The supported cloud production deployment, deployed with Terraform, ArgoCD, and Helm against a GKE Autopilot cluster.
  • On-prem Kubernetes. A Kubernetes cluster you own, running Aperium with each enabled connector exposed as an in-cluster HTTP MCP service and the primary LLM served locally inside your network boundary. See On-prem overview for the requirements contract.

​
GCP vs. on-prem at a glance

The two paths share the same in-cluster application shape: Aperium frontend, backend, document worker, optional scheduler and cleanup jobs, in-cluster MCP services, and the supporting data services. They differ in what backs the platform: