Skip to main content
Version: 0.2 (next)

Roadmap

Infrared 0.1 is the first release, offered as an open beta that is free through November 30, 2026. It is built in seven phases, and every one of them has shipped work in 0.1. For each phase, this page says briefly what you can use today and then what comes next. The last section names larger pieces of work that come later.

Nothing on this page has a date. Work moves up or down as people use 0.1 and tell us what matters to them.

Phase 1: walking skeleton​

In 0.1. One helm install of the public chart takes a cluster to a control plane that Argo CD manages, with the setup wizard walking you from the setup token to Ready. Infrared creates your gitops repo, fills it from the gitops template, installs Argo CD, and then manages itself through pull requests. Every org gets the AgentRole and AgentWorkflow catalog and a set of default Teams. Backups go to object storage outside the cluster, encrypted to keys you hold, and ir restore brings an install back on new servers. See Architecture, Back up and restore, the ir command reference and the API reference.

Next. Nothing is planned here beyond keeping the install, upgrade and restore paths dependable as the rest grows.

Phase 2: orgs, identity and secrets​

In 0.1. People sign in with Google from the domains you allow, or with GitHub when they have no Google account. An install can open sign-up, so anyone with a Google account gets an org of their own within the limits you set. The root user's password lives only in your own vault. Access groups give each person a role per org, from Google Workspace groups or GitHub logins, and Infrared keeps a GitHub team in step with each one. People link their GitHub, GitLab and Gitea accounts. Platform admins create more orgs, each with its own forge connection, gitops repo, model key and cloud accounts. See Access groups and access and Organizations.

Next:

  • GitLab and Gitea teams kept in step with access groups, as GitHub teams are.
  • Sign-in through other OpenID Connect identity providers.
  • Infrared's own secrets moved out of Kubernetes Secrets into Infisical, delivered by external-secrets. The gitops template already installs both.
  • Org roles mapped to Kubernetes RBAC on workload clusters, and to cloud IAM for agents.

Phase 3: workload clusters​

In 0.1. You register a workload cluster by kubeconfig, or build one on GKE or EKS from a cluster template through one of your cloud accounts, and Infrared adds it to Argo CD and your gitops repo. Clusters shows every cluster with its sync waves, health, nodes and zones. Platform admins decide which clusters each org may use, and can let an org bring its own. Deleting a cluster shows what it will remove before it starts. See Workload clusters and Cloud accounts and registries.

Next:

  • Linode as the next cloud. Today a Linode cluster registers by kubeconfig, and backups can go to Linode Object Storage. See Linode.
  • More clouds after that.
  • Node access through the cloud's own tools, and Argo CD cluster credentials delivered by external-secrets.

Phase 4: Products and delivery​

In 0.1. You create a Product from existing repos, a new repo, a template or a zip. Each merged Change becomes a deployment that is built, tagged and promoted zone by zone, with a pull request per zone, a smoke check, and a release guard that holds, reads error budgets and rolls back a zone that fails. Production waits for your approval by default, and Go now ends a hold when you are sure. Each environment has its own page with its address, resource use, pods, logs and settings, including domains, variables and secrets. When enough has reached production, Infrared nudges you to cut a release with notes for engineers and a post for everyone else. See Products, Deployments and Cut a release.

Next:

  • Secret environment variables on workload clusters. Plain variables already work there.

Phase 5: change management​

In 0.1. You ask for a change in a sentence, and the architect plans it. You decide whether agents or a person builds it, agents build and review it, and you approve from the evidence: verdict cards in plain words, screenshots, reports and a short summary video of each Change. When an agent stops and asks, the Change waits for you with its question, and you answer by retrying the step with guidance. Changes lists what was asked for and where each request stands, and the rail counts what waits for you. Workforce shows your Teams, people and AgentRoles together. What each run cost is on its record and on Usage. See Run a Change, Follow a change and Models and costs.

Next:

  • AgentRoles tailored to your org from analysis of its repos.

Phase 6: observability​

In 0.1. Every Product has SLOs with error budgets and burn alerts, incidents that alerts or people open, DORA metrics, and a status page you can keep private or make public. Products opens on the week in review: what reached production across every Product, the people behind it, and a weekly video. See SLOs, incidents and DORA.

Next:

  • SLAs.
  • DORA metrics per Team.
  • Alerts routed to Teams.
  • Incidents opened from scheduled AgentRoles' findings. Today those findings open issues on the forge.

Phase 7: go to market​

In 0.1. Infrared 0.1 is free, with no license needed, through November 30, 2026. Licenses, grace after a license expires, and org and cluster limits are built in, and you can install a license from Settings, the chart or ir. Later releases need a license bought from darkshift. See Licensing.

Next:

  • Org and cluster limits counted for resources written straight to the cluster or the gitops repo. Today they are checked when the API creates an org or cluster.
  • A reproducible environment for demos and testing.
  • Support tooling.

Later​

These are larger pieces of work that are not part of 0.1 and come in later releases:

  • localred. A whole Infrared running on your Mac, for trying it out and for running agent steps on your own machine.
  • Knowledge. A page where people and agents search and ask questions of your code and its history, built on the code index.
  • Socials. Drafts and posts about what shipped, for the places your users follow, with a person approving each one.
  • Front Office. Customer relationships managed alongside the Products you ship to them.
  • Back Office. Accounts, seats and costs tracked in one place.
  • Org summaries. Daily and custom summaries of an org's work, beside the weekly video.