Skip to content
New: see your fit and get a tailored quote in minutes.Try the estimator
Menu
Request a demo Sign in

Cloud deployment

Run IntegraCI on Amazon Web Services.

Deploy IntegraCI into your own AWS account. The platform installs on Amazon EKS, and your pipeline, secrets, and compliance evidence stay inside your account. You self-host the platform on AWS, 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.

Request a demo Read the docs

What you get

Deploy on AWS, keep the boundary.

Runs on Amazon EKS

Install IntegraCI with Helm into a namespace on Amazon EKS, the managed Kubernetes you already operate on AWS. The same Helm profiles cover an evaluation tenant and a production setup.

Data stays in your account

The portal, the engine, the connectors, and your compliance evidence run inside your AWS account. 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 AWS stack

IntegraCI orchestrates the cloud-native tools you already run on AWS as one governed line, with every step inspected and recorded.

How to run it

One governed line, on your own AWS.

IntegraCI ships as a self-host edition you install on infrastructure you own. On AWS that means a Amazon EKS cluster you operate, a Helm install, and the same governance you would get from a hosted setup, running inside your account.

  • Bring your own AWS cluster

    Point the install at a Amazon EKS 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 AWS moves the location, not the guarantees.

How self-host works Sovereign & air-gapped AWS integration

Run it on your own AWS.

Request a demo to see the platform working, then follow the docs to install it on Amazon EKS in your own account, air-gapped if you need it.

Request a demo Read the docs