
Compare3AM vs Resolve AI
Their cloud.Your network.
Resolve runs as a cloud service with an agent in your cluster. 3AM runs wholly inside your network, proves the cause, and needs two people before it writes.
Where Resolve AI is strong.
Rigor in the cloud
Many agents argue competing causes, and a separate verifier checks them.
resolve.aiTelemetry not kept
Queried live and not retained; results are redacted before they leave.
docs.resolve.ai
Where a bank decides.
Eight questions a bank's security, risk and operations leads ask before anything touches production.
| Question | Resolve AI, Resolve AI0 of 8, 3 in part | 3AM8 of 8 |
|---|---|---|
| Runs entirely inside your networkEvery part, management included, on infrastructure you own | Cloud service, with an in-cluster Satellite holding an always-on connection out. | Every part runs in your network. The only call to us is a signed license check; air-gapped, it verifies offline. |
| Runs air-gappedNo connection out at all | No self-hosted or air-gapped option found. | An air-gap bundle ships the images and models together. The license verifies offline. |
| Never copies your telemetryNo ingest, no index, no cached results outside your systems | Queries live. Results go to Resolve's cloud after redaction; summaries may be cached. | Each question runs where the data lives and a small answer comes back. Nothing is copied out. |
| Proves the cause before actingA live check that confirms it, not a confidence score | Competing hypotheses checked by a verifier agent. | A live check confirms the cause. Only a confirmed cause can authorize a fix. |
| Applies the fix and verifies itRehearsed first, then checked after it runs | Alert silencing, pull requests and GitHub Actions (preview). | Every fix is dry-run first, applied with approval, then checked against the live system. |
| Two people approve every writeNot one person, and never switched off by an admin | One person approves. Admins can switch actions to run on their own. | Two different people approve one plan, and the plan cannot change after they sign. |
| Holds no key to the booksA hard line around ledgers, journals and balances | Not found in public docs. | No key to the books at any setting. A person runs a signed package with their own key. |
| Tamper-evident audit trailHash-chained and signed, verifiable by your auditors | Not found in public docs. | Every step is hash-chained and signed, and exports to your SIEM. |
Inside your network
Every part, management included, on infrastructure you own
Resolve AI. Cloud service, with an in-cluster Satellite holding an always-on connection out.
3AM. Every part runs in your network. The only call to us is a signed license check; air-gapped, it verifies offline.
Air-gapped
No connection out at all
Resolve AI. No self-hosted or air-gapped option found.
3AM. An air-gap bundle ships the images and models together. The license verifies offline.
No telemetry copied
No ingest, no index, no cached results outside your systems
Resolve AI. Queries live. Results go to Resolve's cloud after redaction; summaries may be cached.
3AM. Each question runs where the data lives and a small answer comes back. Nothing is copied out.
Proves the cause
A live check that confirms it, not a confidence score
Resolve AI. Competing hypotheses checked by a verifier agent.
3AM. A live check confirms the cause. Only a confirmed cause can authorize a fix.
Fixes, then verifies
Rehearsed first, then checked after it runs
Resolve AI. Alert silencing, pull requests and GitHub Actions (preview).
3AM. Every fix is dry-run first, applied with approval, then checked against the live system.
Two people approve
Not one person, and never switched off by an admin
Resolve AI. One person approves. Admins can switch actions to run on their own.
3AM. Two different people approve one plan, and the plan cannot change after they sign.
No key to the books
A hard line around ledgers, journals and balances
Resolve AI. Not found in public docs.
3AM. No key to the books at any setting. A person runs a signed package with their own key.
Tamper-evident audit
Hash-chained and signed, verifiable by your auditors
Resolve AI. Not found in public docs.
3AM. Every step is hash-chained and signed, and exports to your SIEM.
One incident, two paths.
Resolve AI
- Alert
- Results to Resolve's cloud
- Verified hypothesis
- One approval
- Pull request or action
3AM
- Alert
- Cause ranked
- Proven live
- Fix rehearsed
- Two people sign
- Recovery verified
Their steps are drawn from Resolve AI’s own documentation. Where a path ends, the rest is left to your people.
Resolve AI, in detail.
| Row | Resolve AI | 3AM |
|---|---|---|
| Where it runs | Resolve's cloud, with a Satellite agent in your cluster holding a long-lived connection out. | Wholly inside your network, air-gapped if you need. The only call out is a signed license check. |
| What happens to your data | Queried live. Results go to Resolve's cloud after redaction; summaries and metadata may be cached. | Each question runs where the data lives and a small answer comes back. Nothing is copied out. |
| How it reaches a cause | Many agents raise competing hypotheses; a verifier agent checks them. | A live check on your systems that can only pass if the cause is real. |
| What it can change | Alert silencing, pull requests and GitHub Actions (preview). | Dry-runs the fix, applies it with approval, then proves the system recovered. |
| Who signs a change | One person approves each proposal. Admins can set actions to run on their own. | Two different people, on one plan that cannot change after they sign. |
Where it runs
Resolve AI. Resolve's cloud, with a Satellite agent in your cluster holding a long-lived connection out.3AM. Wholly inside your network, air-gapped if you need. The only call out is a signed license check.What happens to your data
Resolve AI. Queried live. Results go to Resolve's cloud after redaction; summaries and metadata may be cached.3AM. Each question runs where the data lives and a small answer comes back. Nothing is copied out.How it reaches a cause
Resolve AI. Many agents raise competing hypotheses; a verifier agent checks them.3AM. A live check on your systems that can only pass if the cause is real.What it can change
Resolve AI. Alert silencing, pull requests and GitHub Actions (preview).3AM. Dry-runs the fix, applies it with approval, then proves the system recovered.Who signs a change
Resolve AI. One person approves each proposal. Admins can set actions to run on their own.3AM. Two different people, on one plan that cannot change after they sign.
The verdict.
Choose Resolve AI
If a cloud service is acceptable for your incident data and one approver is enough, Resolve AI is one of the most capable in the field.
Choose 3AM
If incident data may not leave the bank, and no admin may turn two signatures into none, choose 3AM.
- Your incident data may not leave your network
- Every write must carry two signatures, with no admin override
- You need a fix proven before it is applied
Sources, read November 11, 2026
- Resolve AI docs, Billing and credit controls
- Resolve AI, homepage
- Resolve AI docs, Security and administration
- Resolve AI docs, Satellite
- Resolve AI docs, Mitigation actions
Compared on November 11, 2026 from each vendor's public website and documentation, linked on every page. Products change; if something here is out of date, write to [email protected] and we will correct it. All product names and trademarks belong to their owners and are used only to identify them. No affiliation or endorsement is implied.
Put us side by side on your own incidents.
- Stays in your network
- Humans hold the keys
- Tamper-evident
- Shadow first
