Runs on Azure AKS
Install IntegraCI with Helm into a namespace on Azure AKS, the managed Kubernetes you already operate on Azure. The same Helm profiles cover an evaluation tenant and a production setup.
Cloud deployment
Deploy IntegraCI into your own Azure subscription. The platform installs on Azure AKS, and your pipeline, secrets, and compliance evidence stay inside your subscription. You self-host the platform on Azure, 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 Azure AKS
Install IntegraCI with Helm into a namespace on Azure AKS, the managed Kubernetes you already operate on Azure. The same Helm profiles cover an evaluation tenant and a production setup.
Data stays in your subscription
The portal, the engine, the connectors, and your compliance evidence run inside your Azure subscription. 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 Azure stack
IntegraCI orchestrates the cloud-native tools you already run on Azure 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 Azure that means a Azure AKS cluster you operate, a Helm install, and the same governance you would get from a hosted setup, running inside your subscription.
Bring your own Azure cluster
Point the install at a Azure AKS 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 Azure moves the location, not the guarantees.
Request a demo to see the platform working, then follow the docs to install it on Azure AKS in your own subscription, air-gapped if you need it.