LIVESave the World, live from Salt Lake City during KubeCon · Wed Nov 11, 11:00 MT →
darkshift
// who it's for · the enterprise

Your own factory, in your own cloud.

You need the whole factory, not a hosted tool: a control plane in your own cloud, building infrastructure through your own accounts, governed by your directory and kept in a gitops repo you own.

Infrared installs with one command onto your GKE or EKS cluster. From there it manages itself, your clusters and your Products through Argo CD. You hold the license, the keys stay yours, and nothing leaves your account that you didn't send.

become a design partner →book a call
your own factory, in your own cloud⤢ fullscreen
// your week with infrared

What it's like.

  1. day one

    One command.

    ir install puts the operator, API, UI and MCP server on your cluster and takes it through setup: your forge, your gitops repo, your sign-in, your backups. Then Argo CD syncs everything from the repo.

  2. week one

    Orgs for your business units.

    Platform admins create an org per business unit, each with its own forge connection, gitops repo, model key and cloud accounts, and its own people through access groups.

  3. week two

    The factory builds its own floor.

    Cloud accounts reach Google Cloud and AWS without stored keys. Infrared builds GKE and EKS workload clusters from templates with OpenTofu, and registers any other cluster you run by its kubeconfig.

  4. every release

    Upgrades are a pull request.

    A new Infrared release is a one-line change to your gitops repo, watched by an upgrade guard. Encrypted backups go to your own bucket, and a restore brings an install back onto new servers.

  5. every day

    Products ship, humans decide.

    Your teams ask for Changes, agents build and review them, and humans approve every merge and every promotion to production, with a full record of all of it.

infrared.darkshift.io
A cluster's page in Infrared: its zones, health and what runs on it
// what you get

What Infrared does for you.

Your cloud, your keysWorkload Identity and IAM roles: Infrared stores no cloud keys.
Infrastructure as part of the flowGKE and EKS clusters from proven templates, built and deleted cleanly.
Gitops you ownArgo CD syncs everything from your repo; every change to the platform is a pull request.
Governed accessGoogle Workspace groups, GitHub teams, sign-in through your own OAuth client, recorded break glass.
ResilienceEncrypted backups to S3 or Cloud Storage, restore onto new servers, guarded upgrades.
Many orgs, one installBusiness units separated, each with its own forge, repo, key and clouds.
// how you run it

Self-hosted, licensed, yours.

Everything runs in your cloud. darkshift gives you access to the chart and images, a license, and the people who built it.

Google CloudGKE, with Workload Identity and backups to Cloud Storage.
AWSEKS, with IAM roles, ECR and backups to S3.
A licenseNo license needed through November 30, 2026. After the open beta, a license from darkshift.
// other stories

Not quite you?

Infrared serves every one of these teams with the same factory. Read the story closest to yours.

Ship your app. Host nothing.You built something with an AI assistant and people are using it.A platform team in a box.A handful of engineers, more repos than people, and no platform team.The agent your security team will approve.Agents run in your account, on your model key.

Build your factory with us.

Our first enterprise design partners get the founders' time, a say in the roadmap, and a control plane in their own cloud from week one.

become a design partner →book a call