FixControl
Deployment governance

Approve deployments with evidence, gates and rollout-aware visibility

Deployment approval cards, risk gates and live rollout status where Argo and Kubernetes are configured. Failed provider actions stay visible in the timeline and outbox. AI does not deploy to production on its own — promotion happens only after human approval.

Book a deployment governance demoTalk to us
Human approval before promotionStatus where configuredFailures stay visible
How it works

A gate between ready and promoted

The AI surfaces the status and the proposal; a person decides whether to promote.

  1. 01Gate opens
    A deployment reaches an approval gate

    When a change is ready to promote, a deployment approval card opens — surfacing what would be promoted and the risk attached to it.

  2. 02Status in view
    Rollout status, where it is configured

    Where Argo and Kubernetes are connected, FixControl shows rollout status so the approver decides with the live picture, not a guess.

  3. 03Risk gates
    Risk gates hold the risky promotions

    Higher-risk promotions pause for an explicit human decision. The gate is the point where a person — not the AI — chooses to proceed.

  4. 04Promote / status
    Promote on approval; abort-aware status

    Where Argo is configured for it, an approved decision promotes a paused rollout. Abort and rollback status stays visible where Argo reports it — reading status and acting on it stay distinct.

What you get

Promotion you can govern and audit

Each capability is described honestly — what's available depends on what's configured.

Deployment approval cards

Promotions surface as approval cards that state what would change and the risk involved, so the person deciding has the context in front of them.

Risk gates before promotion

Risky promotions pause at a gate for an explicit human decision, rather than flowing through automatically.

Argo / Kubernetes status where configured

Where those providers are connected, FixControl reads and shows rollout status — so the gate reflects the real state of the deployment.

Promote or read status — where configured

Where Argo is configured for it, an approved decision promotes a paused rollout; otherwise FixControl reads and surfaces status, including abort and rollback status where Argo reports it. What's available is shown honestly per capability.

Failed provider actions stay visible

A provider action that fails surfaces in the operational timeline and the outbox, instead of disappearing — so a stuck or failed promotion is visible, not silent.

Audit trail of the decision

Who approved a promotion, from which channel, on what evidence and with what consequence is recorded — the deployment decision is auditable after the fact.

Governed by design

No production promotion without a human

Gates, visibility and audit
AI does not deploy to production on its own. A promotion happens only after a human approves it at a gate, and risky promotions are held for an explicit decision. Where Argo and Kubernetes are configured, FixControl reads rollout status and — where Argo is configured for it — can promote a paused rollout after approval, with abort and rollback status visible where Argo reports it. Failed provider actions remain visible in the operational timeline and outbox, and each decision is recorded for audit.
FAQ

Common questions

Does the AI deploy to production by itself?+
No. AI does not deploy to production on its own. A deployment promotion happens only after a human approves it at a gate. The AI surfaces status and proposals; the decision to promote is a person's.
What does FixControl actually do at deploy time today?+
It opens deployment approval cards, holds risky promotions behind gates, shows Argo and Kubernetes rollout status where those are configured, and — where Argo is configured for it — can promote a paused rollout after approval. Abort and rollback status is surfaced where Argo reports it.
What happens if a provider action fails?+
A failed provider action stays visible in the operational timeline and the outbox rather than vanishing, so a stuck or failed promotion is something you can see and act on.
Is Argo or Kubernetes required?+
Live rollout status and approved promotion depend on Argo and Kubernetes being connected and configured. Where they are not, FixControl shows what it can rather than implying a capability it doesn't have.
Is the deployment decision recorded?+
Yes. The approval — who decided, from which channel, on what evidence and the consequence — is captured in the audit trail, so a promotion can be reviewed later.
Can a risky promotion be forced through automatically?+
No. Risky promotions are gated for a human decision by design. The gate is the deliberate point where a person chooses to proceed, abort, or hold.
Keep exploring
Argo integration

Read rollout status and gate promotions where configured.

Support → engineering

Turn support tickets into governed engineering fixes.

AI approval ledger

Every AI-assisted action carries a decision record.

See deployment governance in action

Walk through approval cards, risk gates and rollout status on a live demo.

Book a deployment governance demoTalk to us