Runs on Google GKE
Install IntegraCI with Helm into a namespace on Google GKE, the managed Kubernetes you already operate on GCP. The same Helm profiles cover an evaluation tenant and a production setup.
Cloud deployment
Deploy IntegraCI into your own Google Cloud project. The platform installs on Google GKE, and your pipeline, secrets, and compliance evidence stay inside your project. You self-host the platform on GCP, all the way to air-gapped if you need it, so your pipeline, your secrets, and the evidence you have to defend never leave your control.
What you get
Runs on Google GKE
Install IntegraCI with Helm into a namespace on Google GKE, the managed Kubernetes you already operate on GCP. The same Helm profiles cover an evaluation tenant and a production setup.
Data stays in your project
The portal, the engine, the connectors, and your compliance evidence run inside your GCP project. Nothing has to leave it for the platform to work.
Sovereign, air-gapped option
Run it in the region you choose, or with no path to the public internet at all. Mirror the images into a registry inside your boundary and install from there, on your schedule.
Works with your GCP stack
IntegraCI orchestrates the cloud-native tools you already run on GCP as one governed line, with every step inspected and recorded.
How to run it
IntegraCI ships as a self-host edition you install on infrastructure you own. On GCP that means a Google GKE cluster you operate, a Helm install, and the same governance you would get from a hosted setup, running inside your project.
Bring your own GCP cluster
Point the install at a Google GKE cluster you operate. IntegraCI deploys into a namespace; CPU and memory scale with your tenant count and workload, so you size the install to your footprint.
Install with Helm
One Helm install brings up the portal, the engine, and the policy checks. The same approach powers a small evaluation install and a production one, so you scale the install, not the method.
Keep the governance with it
Database row-level security, the SHA-256 hash-chained audit trail, and your policy-as-code bundles run where you run them. Self-hosting on GCP moves the location, not the guarantees.
Request a demo to see the platform working, then follow the docs to install it on Google GKE in your own project, air-gapped if you need it.