What is Infrared?
The Infrared 0.1 keynote, three minutes, sound on · ⤢ Watch fullscreen
Infrared is a software factory designed for the best human experience of working with agents.
You are the software change manager. You say what should change, in a sentence. Agents plan it, build it, test it and review it, and Infrared brings you what they found: a verdict from each one in plain words, the evidence behind it, and the pull request. You decide whether it merges and whether it goes to production. Everything in between, from the branch to the build to the gitops pull request that promotes it, is done for you, and you never have to chase it.
Infrared 0.1 is free to use, with no license, through November 30, 2026 (UTC). Later releases need a license bought from darkshift. See Licensing.
How a Change reaches production
A Change is one request, followed from the moment you ask for it to the moment it runs in production. With the default AgentWorkflow, it goes like this:
The diamonds are yours. Everything else runs on its own, and each step leaves a record you can open: what the agent did, what it concluded, what it cost and the proof it captured. When an agent gets stuck, it stops and asks you instead of guessing, and you answer on the Change's page. See Your first Change for a walk through it, and Built for the person in charge for everything Infrared does to keep you informed and in control.
A tour of the app
The rail on the left of every page is the map of Infrared. Each item is a page, in this order.
| Rail item | What you do there |
|---|---|
| Products | Start here. The top of the page is the week in review, with its weekly video. Below it is a card per Product: what each environment runs, what needs attention and what shipped lately. A Product's page is where you ask for a change and follow its environments, Changes, deployments and releases. |
| Changes | Every Change in the org, newest first, with what was asked for and where each one stands. The number beside Changes on the rail counts what is waiting for you. Open a Change to see its journey, its steps, their verdicts and evidence, and to approve, triage or answer an agent. |
| Deployments | Every version on its way through its environments: built, promoted zone by zone, checked by the release guard, and rolled back if it fails. Production waits for a person to approve it. |
| Releases | The versions that reached production, gathered under one release number with notes for engineers and a post for everyone else. A Product tells you when there is enough in production to be worth a release. |
| Workforce | The people and agents who do the work: teams, people, the AgentRoles and AgentWorkflows your org runs, and the access groups that give people their roles. |
| Clusters | The management cluster Infrared runs on and the workload clusters your Products run on, registered or built from a cluster template in your own cloud. |
| Usage | What your org's agents and videos cost today and over time, against each limit. |
| Access | For platform admins: who can sign in or sign up, their roles, the git connectors, and the break-glass root user. |
| Settings | How your org works (model key, domains, Slack, summary videos and more), how the install works if you are a platform admin. |
Your own name sits at the foot of the rail and opens You, the one page about yourself: your profile, your linked accounts, your API tokens, your availability and your roles.
Where Infrared runs
Infrared runs on a Kubernetes cluster called the management cluster and manages itself, your clusters and your Products through a gitops repo that Argo CD syncs. Install it on your own GKE or EKS cluster with one helm install of its public chart, or join the private beta of darkshift's hosted environments. See Choose how to run Infrared.
Where to go next
- Your first Change takes you from a one-line request to production.
- Built for the person in charge shows each place the app is designed around you.
- Choose how to run Infrared compares the hosted control plane with an install of your own.
- Architecture explains the components, the CRDs and how an install comes up.
- AgentRoles, AgentWorkflows and AgentWorkflowRuns explains how agents do their work.
- Glossary defines every term these docs use.