MIZANIC
Agentic DevOps AWS-native Human-in-the-loop Private beta

Consensus

An autonomous DevOps agent that watches your infrastructure, diagnoses issues, drafts changes, and ships fixes — with the right human approval gates in place. The DevOps engineer you don't have to hire.

Join waitlist See how it works

How it works

Five-step loop, with humans where they matter.

Consensus is built on the principle that autonomy belongs inside the loop, with humans holding the keys at every gate. Approval gates are configurable per environment and per change class.

Consensus — five-step agentic DevOps loop with human-in-loop gate CONSENSUS AGENTIC DEVOPS LOOP AWS-NATIVE 01 / WATCH Continuous signal CloudWatch · GuardDuty cost · drift 02 / DIAGNOSE Root-cause + citations Logs · metrics · topology Evidence-backed 03 / DRAFT IaC change in PR Terraform · CloudFormation Kubernetes manifests 04 / GATE Policy + human approval OPA · Conftest · scanners Human approval where it counts 05 / SHIP Deploy + verify Through your pipeline Annotate · close loop HUMAN IN THE LOOP approvals · overrides · audits
01

Watch

Continuous signal across CloudWatch, GuardDuty, cost anomalies, drift detection, and your existing observability stack. Consensus knows what normal looks like for each workload.

02

Diagnose

When signal turns into incident, Consensus correlates evidence across logs, metrics, and topology to propose the most likely root cause — with citations.

03

Draft

The change comes back as a pull request in your IaC repo. Real Terraform, real CloudFormation, real Kubernetes manifests — the same files your team already ships.

04

Gate

Policy checks (OPA/Conftest), security scans, and human approval where the change class requires it. Consensus respects your guardrails. It does not invent its own.

05

Ship

Deploy through your existing pipeline. Verify the fix landed. Annotate the incident. Close the loop. Next watch starts.

How to deploy

Three ways to deploy Consensus.

Self-deployed

Run Consensus in your AWS

Deploy Consensus into your own AWS account using our deployment guide. Your engineers stay in control of the approval gates and your IaC repo.

Internal

Use it on your own engagements

Run Consensus to operate the platforms you ship. Faster MTTR, fewer late-night pages.

Co-deploy

Bundle with our cloud services

Deliver an AWS engagement that comes with continuous operations baked in. Less cycle time between build and stable production.

Private beta

Status

Currently in private beta.

Consensus runs in production with a small set of clients. We're opening up the beta cohort throughout 2026 — direct engagements only, no resellers in between.

If you run managed AWS in production and want continuous improvement without expanding the on-call rotation, drop your email below.

— Where Consensus fits
your AWS account
your IaC repo · pipeline
your existing approval flow
consensus watch · draft · gate
your team approve · ship

Consensus FAQ

Common questions about agentic DevOps.

What does Consensus actually do, in one sentence?
Consensus watches your AWS infrastructure, drafts the change as a real pull request in your IaC repo when something needs fixing, and ships through your existing approval gates — autonomously where it's safe to, with human approval where the change class requires it.
Does Consensus run in our AWS account or yours?
Yours. Consensus deploys into your AWS account, watches your workloads, and writes to your IaC repo. We don't take a copy of your infrastructure state, your secrets, or your logs. The agent runs where the work happens.
What approval gates can we configure?
Policy checks via OPA/Conftest, security scans, cost-impact thresholds, and human approval on the change classes you specify. Approval gates are configurable per environment (prod vs stage vs dev) and per change class (network change vs IAM change vs cost-tagged change). Consensus respects the gates; it does not invent its own.
Is Consensus generally available?
Currently in private beta with a small cohort of customers. We're opening up the cohort throughout 2026 — direct engagements only, no resellers in between. If you run managed AWS in production and want continuous improvement without expanding the on-call rotation, get in touch.
How does Consensus compare to a traditional SRE team?
Consensus doesn't replace the SRE team — it removes the high-volume, low-leverage work (drift fixes, cost-anomaly remediation, common incident playbooks) so the team can focus on the work that actually needs senior judgement. Think of it as the DevOps engineer you don't have to hire, sitting alongside the ones you do.

Want a seat in the Consensus beta?

Drop your email. We'll confirm and reach out as the cohort opens.

Join waitlist