Watch
Continuous signal across CloudWatch, GuardDuty, cost anomalies, drift detection, and your existing observability stack. Consensus knows what normal looks like for each workload.
Agentic DevOps · Private beta
Consensus.
An autonomous DevOps agent that watches your infrastructure, drafts IaC pull requests, and ships fixes through your existing approval workflow.
01
Watches CloudWatch, GuardDuty, drift detection, and cost anomalies, learning what normal looks like for each workload.
02
Drafts IaC pull requests with rationale; runs them through your policy, security, and cost gates.
03
Ships through your existing approval workflow; the human review stays where it belongs.
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 · change review
planner
change 142 touches an IAM boundary. routing to security review.
security
role is over-scoped. proposing a least-privilege patch.
executor
patched. canary at 5% is clean. promoting to 100%.
Diagnose
When signal turns into incident, Consensus correlates evidence across logs, metrics, and topology to propose the most likely root cause, with citations.
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.
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.
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.
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.
Use it on your own engagements
Run Consensus to operate the platforms you ship. Faster MTTR, fewer late-night pages.
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 complements the SRE team. It takes the high-volume routine work (drift fixes, cost-anomaly remediation, common incident playbooks) so the team can focus on the calls that need senior judgement. Think of it as an extra senior DevOps engineer who handles the routine, sitting alongside the ones who own the hard calls.
Want a seat in the Consensus beta?
Drop your email. We'll confirm and reach out as the cohort opens.