Skip to main content

Infrared 0.1 is planned for Monday, October 26

· 3 min read
The darkshift team
The darkshift team
The team behind Kubefirst, Konstruct and Colony

Infrared 0.1 is planned for Monday, October 26, 2026. It is the first release of Infrared, the gitops control plane where humans and agents work on software together through one change flow. Until now Infrared has shipped as pre-releases on the 0.1 track; on Monday, 0.1.0 becomes the version these docs describe.

What 0.1 is​

Infrared runs on a Kubernetes cluster, the management cluster, and manages itself and your Products through pull requests to a gitops repo. Every Change, whoever wrote it, moves through an AgentWorkflow: AgentRoles do defined jobs, humans hold the gates, and every AgentWorkflowRun records each step's verdict, cost and evidence. A merged Change becomes a deployment, promoted zone by zone, each zone watched by its release guard.

0.1 is an alpha. Every phase of the roadmap has working pieces in it, and every phase lists what is not there yet.

What is in 0.1​

  • Install and bootstrap: four ways to run Infrared (the hosted control plane, GKE, EKS and localred on a Mac), the setup wizard, a forge on GitHub or Gitea, gitops repo hydration, and Argo CD adopting Infrared. Backups of the whole install, and the ir command-line client.
  • Orgs and access: access groups with four roles, sign-in with Google and GitHub, linked git accounts, API tokens, and cloud accounts reached through a role, never a key.
  • Workload clusters: register a cluster by kubeconfig, or build one from the gcp/gke-cluster or aws/eks-cluster cluster template, with a cluster allowlist per org.
  • Products and delivery: Products from existing repos, a template or a zip; deployments promoted zone by zone, Guarded or Fast, with Go now; environments, custom domains and per-environment variables; and releases cut from what reached Production.
  • Change management: AgentWorkflowRuns executed in the cluster, human approval gates, the backlog, Ask for a change, the Changelog, and proof of what shipped on every Change.
  • Observability: SLOs with error budgets and burn alerts, incidents, DORA metrics and status pages per Product.
  • Go to market: licensing with a 48-hour trial, and announcement drafts when a release is cut.

What is not in 0.1 yet​

We would rather tell you than have you find out. Among what the roadmap lists as not yet:

  • SSO through other OpenID Connect identity providers, and secrets moved into Infisical.
  • Org roles mapped to Kubernetes RBAC on workload clusters.
  • Secret environment variables on workload clusters.
  • AgentRole tailoring from analysis of an org's repos.
  • SLAs, DORA metrics per team, and alerts routed to teams.
  • Clouds beyond Google Cloud and AWS. Linode is next.

The roadmap has the full list for each phase.

Where to start​

We will post here again when 0.1 is out.