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

The agent your security team will approve.

Your developers want agents. Your security team wants to know exactly what they do, where they run and who signed for it. Infrared answers both.

Agents run in your account, on your model key, inside a network fence. Your platform team writes the opinions every agent follows. A person approves every merge and every promotion, and every step leaves a record.

become a design partner →book a call
the agent your security team will approve⤢ fullscreen
// your week with infrared

What it's like.

  1. week one

    You write the rules once.

    Each AgentRole's guidance is written as your org's opinions: how to test, what's off limits, what a security review must check. Your platform team edits them in the app, and every agent follows them.

  2. week one

    Access follows your directory.

    Access groups map Google Workspace groups and GitHub logins to roles. Roles follow your groups within minutes, and Infrared fails closed if it can't read them.

  3. every change

    Nothing ships unreviewed.

    Every Change runs the required steps: build, security review, end-to-end verification, a person's approval and merge. A blocking verdict stops it, whoever wrote it.

  4. every day

    The watchers watch.

    Daily security, performance and SRE audits open issues for what they find, de-duplicated so the backlog stays readable.

  5. audit day

    You show the record.

    Every run, merge, approval, deployment and rollback is in one log, with who did it, what the agent saw, what it cost and the evidence it captured.

infrared.darkshift.io
An AgentRole's opinions in Infrared: each rule editable or switched off by your platform team
// what you get

What Infrared does for you.

Your key, your accountAgents run as Jobs on your cluster, on your org's own Anthropic key, behind a network fence.
Opinions as policyEdit, switch off or add to every AgentRole's guidance and guardrails.
Required reviewSecurity review, verification and a person's approval on every Change by default.
Directory-driven accessGoogle Workspace groups, GitHub teams kept in step, and break-glass access that's recorded.
Budgets and breakersWeekly budgets and a circuit breaker per AgentWorkflow.
Read-only MCPGive Claude Code read access to runs, deployments, incidents and SLOs, with no write path.
// how you run it

Your control plane, your rules.

Run Infrared on your own GKE or EKS cluster, wired to your Google Workspace groups, your GitHub organization and your clouds.

Self-hosted on GKE or EKSWorkload Identity on Google Cloud, IAM roles on AWS: no stored keys.
Your forgeYour GitHub organization through a GitHub App the setup wizard creates, or Gitea on the cluster.
An org per teamSeparate orgs, each with its own forge connection, gitops repo, model key and cloud accounts.
// 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.Your own factory, in your own cloud.One install puts the control plane on your GKE or EKS.

Bring agents in, the right way.

Become a design partner: we'll stand Infrared up in your account with your platform team, and take a real Change through your controls.

become a design partner →book a call