FixControl
Deployment governance

Deployments wait at a gate until someone on your team approves

A bad promotion is one of the most expensive mistakes a team can make. Promotion is a decision, and FixControl treats it like one: approval cards state what would change and the risk attached; where Argo and Kubernetes are connected, the approver also sees live rollout status. Approving promotes the paused rollout, and the decision lands in the audit trail.

Book a demoTalk to us
Human approval before promotionLive rollout status at the gateFailures stay visible
Deployment approval
A governed mission pausing for deployment approval — execution held until a person signs off, gated on a green CI run.
How it works

A gate between ready and promoted

A release reaches the gate, someone on your team reviews it with live status in view, and promotion happens on their verdict.

  1. 01Gate opens
    A release reaches an approval gate

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

  2. 02Status in view
    The approver sees the live rollout

    The card shows the current state of the rollout — paused, progressing or degraded — read from Argo and Kubernetes when they are connected. The approver decides on live data.

  3. 03Risk gates
    Risky promotions wait for someone on your team

    Higher-risk promotions pause until someone on your team with the right role decides. The gate is where that person chooses to proceed, hold or abort.

  4. 04Promote
    Approval promotes the paused rollout

    A canary sits paused mid-rollout at the gate. The approver checks what Argo reports and approves; FixControl promotes the paused rollout and records the decision, with abort and rollback status visible as Argo reports it.

What you get

Gates, live status and a record of every promotion

Capabilities that depend on Argo or Kubernetes are labeled that way, on this page and in the product.

Deployment approval cards

Each promotion arrives as a card stating what would change and the risk involved. The person on your team who decides has that context in front of them.

Risk gates before promotion

Risky promotions stop at a gate and wait for a human decision. Nothing about a risky promotion proceeds automatically.

Live Argo and Kubernetes status

FixControl reads rollout state from the connected providers and shows it at the gate. The approver sees the deployment as it is at the moment of decision.

Promote on approval, or read-only

Where Argo is configured for promotion, an approved decision resumes a paused rollout. Where it is not, FixControl reads and shows status, including abort and rollback state as Argo reports it.

Failed actions stay in view

A provider action that fails shows up in the operational timeline and the outbox. A stuck or failed promotion stays visible until someone deals with it.

Every promotion decision on the record

Who approved a promotion, from which channel, on what evidence and with what outcome is recorded. The decision can be reviewed after the fact.

Production stays gated

Promotion is a recorded human decision

Gates, visibility and audit
AI does not deploy to production on its own: by default, nothing is promoted without a recorded human decision, and risky promotions are held at a gate. Where Argo is connected and configured for it, an approved decision promotes the paused rollout, with abort and rollback status shown as Argo reports it. Failed provider actions stay visible in the timeline and outbox, and each decision is recorded for audit.
FAQ

Questions platform teams ask

Does the AI promote to production by itself?+
No. A promotion happens only after someone on your team approves it at a gate. AI prepares the card, the status and the evidence; the verdict belongs to a person on your team.
What does FixControl actually do at deploy time today?+
It opens deployment approval cards, holds risky promotions behind gates, and shows Argo and Kubernetes rollout status where those are connected. Where Argo is configured for promotion, approval resumes a paused rollout.
What happens if a provider action fails?+
It stays visible in the operational timeline and the outbox, with retry state and dead-letter jobs you can act on. A failed promotion is not something you discover later.
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 only what it can read, and the capability labels say so.
Is the deployment decision recorded?+
Yes. The approver, the channel, the evidence in view and the outcome are captured in the audit trail, like any other governed decision.
Can a risky promotion be forced through automatically?+
No. Risky promotions are gated for a human decision by design, and the gate is where someone on your team chooses to proceed, hold or abort.
Keep exploring
Argo integration

Rollout status and gated promotion where configured.

Support → engineering

Turn support tickets into governed engineering fixes.

AI approval ledger

The decision record behind every approval.

See a gated promotion

Book a demo and approve a paused rollout yourself: the gate, the live status, the promotion and the audit entry it leaves.

Book a demoTalk to us