Verdict
Investigates. Predicts. Fixes. Proves the fix shipped.
Digital Care’s next-generation autonomous SRE platform. Verdict recalls similar past incidents, predicts failures before they fire, continuously reviews your security posture, and closes the loop: it proposes the GitOps fix, then machine-checks that it actually shipped.
More than incident investigation: it closes the loop.
Closed-loop remediation
Verdict proposes the GitOps fix as a pull request. A human approves it, then an independent verifier machine-checks that the fix actually shipped. The loop doesn’t close until the change is proven.
Investigations with memory
Recalls similar past incidents and surfaces them on a live incident graph, so every investigation stands on everything you’ve seen before.
Incident prediction
Spots failures before they fire: capacity, certificate expiries and disk trends flagged while there’s still time to act.
Continuous security review
Continuously reviews your security posture with ongoing CVE triage, prioritising what actually matters in your environment.
Daily digest
Posts a daily digest to Slack: incidents, predictions and security findings summarised for the whole team, every morning.
A loop that only closes when the fix is proven.
A signal arrives
An alert fires, or a prediction flags a failure before it does. Either way, Verdict starts the loop.
Investigation with recall
It investigates using 30+ read-only diagnostic tools and recalls similar past incidents from memory.
Root cause, cited
Verdict lands a root cause with cited evidence, every conclusion linked to the signal that supports it.
Fix as a pull request
It proposes the GitOps fix as a pull request. A human reviews and approves; nothing ships without sign-off.
The verifier proves it
An independent verifier machine-checks that the fix shipped; only then does the loop close.
Watch Verdict close the loop on a real incident.
Book a demoFrequently asked questions
How is Verdict different from Metatron?
Metatron is the read-only control plane: it investigates every alert and reports root causes. Verdict goes further and closes the loop: it proposes the fix as a pull request, and after a human approves it, an independent verifier machine-checks that the fix actually shipped.
Does Verdict change production on its own?
No. Every fix is a GitOps pull request that a human reviews and approves. Nothing ships without sign-off; autonomy applies to investigation and verification, not to unsupervised changes.
What does the post-merge verifier check?
That CI is green, the security rescan shows no new vulnerabilities, and the GitOps sync landed in the cluster. The loop closes only when the change is proven in production.
What kinds of failures can Verdict predict?
Capacity exhaustion, certificate expiries and disk trends: failures that build up gradually. Verdict flags them while there is still time to act, alongside a daily digest of incidents and security findings.