Skip to main content
Version: 0.1 (next)

Roadmap

Infrared is built in seven phases. Each phase ends with something a user can install and use.

Phase 1: walking skeleton​

The smallest end-to-end path: helm install to a control plane that Argo CD manages, with the AgentRole catalog in place.

  • The repos: infrared-operator, infrared-api, infrared-mcp, infrared-cli, infrared-ui, infrared-chart, infrared-gitops-template, infrared-iac-modules and infrared-docs.
  • The v1alpha1 CRDs, with the CRDs as the data store.
  • The setup wizard, from setup token to Ready.
  • GitHub connection through a GitHub App created with the manifest flow.
  • Gitops repo creation and hydration from the gitops template.
  • Argo CD install, app-of-apps sync in sync-wave order, and Argo CD adopting Infrared.
  • The AgentRole and AgentWorkflow catalog, seeded per org, viewable and editable in the UI.

Phase 2: orgs, identity and secrets​

  • Orgs and teams, with RBAC that maps Infrared roles to IAM for both humans and bots.
  • SSO for human sign-in.
  • Secrets moved out of Kubernetes Secrets into Infisical, delivered by external-secrets. The GitHub App private key moves first.
  • Model providers configured per org, referenced from AgentRoles.
  • Container registries configured per org.
  • Identity mapping between Slack users, git identities and Infrared users.

Phase 3: workload clusters​

  • Workload clusters built from cluster templates by Crossplane provider-terraform Workspaces, with SSM for node access, and Argo CD cluster secrets delivered by ExternalSecret.
  • Cluster allowlists per org, managed by the platform org.
  • Zones: a Product's running instances on allowed clusters, grouped into the Pre-release and Release environments.
  • k3s on EC2 or Linode as the low-cost path for small teams.

Phase 4: Products and delivery​

Feature parity with Konduit for running apps.

  • App registration: add a repo to a Product and get a running zone.
  • One kpack Image per app, built on the management cluster.
  • Promotion by pin PR: each zone's pin (tag@sha256) changes only through a pull request to the gitops repo.
  • Per-zone environment variables, secrets, hostnames, persistent volume claims and replicas.
  • Logs and metrics per app and zone.
  • Custom domains.

Phase 5: change management​

  • AgentWorkflowRun execution: AgentWorkflows run for real, with each step's verdict, usage and evidence recorded.
  • The change flow with dead-lettering to named humans.
  • RC verification proofs: screenshots, video and coverage reports from the rc zone, attached to the Change.
  • Approve, merge to main, and track what percentage of a Release has shipped.
  • A kanban board: Backlog, Arch reviewed, Todo (human), Todo (agent).
  • AgentRole tailoring from analysis of an org's repos.

Phase 6: observability​

  • DORA metrics per Product and team.
  • SLOs and SLAs with error budgets.
  • A status page per Product.
  • Alerts routed to teams.
  • Incident management, fed by the scheduled AgentRoles.

Phase 7: go to market​

  • Go-to-market and support tooling.
  • The rig: a reproducible environment for demos and testing.
  • Licensing.
  • GCP and Linode as supported providers alongside AWS.