Compare · Resolve AI
CHA vs. Resolve AI
Resolve raised $190M at $1.5B and calls closed-loop 'the next funding milestone.' We ship it today. They're SaaS-only with no FedRAMP / sovereign story; we run inside your cluster including air-gap.
| Dimension | CHA | Resolve AI |
|---|---|---|
| Where it runs | In your cluster — operator + CronJob + Deployment | Resolve SaaS + thin in-cluster Satellite gateway |
| Closed-loop remediation | Yes — shipped today, default behavior | No — Resolve calls it "the next funding milestone" |
| Air-gap / sovereign / FedRAMP | Yes — runs entirely in customer env | No — SaaS-only |
| Pricing transparency | Published list prices for OSS / Team / Enterprise | Contact sales only |
| Open source | Apache-2.0 — full OSS feature set | Proprietary |
We compete on architecture, not on funding-round PR.
Resolve's funding announcement explicitly named closed-loop as a future milestone. We respect that — it's an honest engineering statement. But the difference between "shipped" and "next milestone" is the difference between being able to retire your on-call rotation and just being a fancier investigation copilot.
Verify our claims: clone the repo, run helm install, watch a DriftReport go from open to resolved without a human in the loop. We publish the code.