
Compare3AM vs Cleric
Checked after.Proven before.
Cleric is a single-tenant cloud service that verifies recovery afterward. 3AM proves the cause and rehearses the fix before anyone is asked, inside your network.
Where a bank decides.
Eight questions a bank's security, risk and operations leads ask before anything touches production.
| Question | Cleric, Cleric0 of 8, 4 in part | 3AM8 of 8 |
|---|---|---|
| Runs entirely inside your networkEvery part, management included, on infrastructure you own | Single-tenant cloud service, hosted in the US or EU. | 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 | Not found in public docs. | 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 at runtime; stores queries, reasoning and evidence extracts. | 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 | Hypotheses tested against production, with confidence scores. | 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 | Fix pull requests that engineers approve; checks recovery for up to 14 days. | 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 | Not found in public docs. | 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 | Every action is logged. | Every step is hash-chained and signed, and exports to your SIEM. |
Inside your network
Every part, management included, on infrastructure you own
Cleric. Single-tenant cloud service, hosted in the US or EU.
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
Cleric. Not found in public docs.
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
Cleric. Queries at runtime; stores queries, reasoning and evidence extracts.
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
Cleric. Hypotheses tested against production, with confidence scores.
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
Cleric. Fix pull requests that engineers approve; checks recovery for up to 14 days.
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
Cleric. Not found in public docs.
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
Cleric. 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
Cleric. Every action is logged.
3AM. Every step is hash-chained and signed, and exports to your SIEM.
One incident, two paths.
Cleric
- Change ships
- Hypotheses tested
- Fix pull request
- Recovery checked after
3AM
- Alert
- Cause ranked
- Proven live
- Fix rehearsed
- Two people sign
- Recovery verified
Their steps are drawn from Cleric’s own documentation. Where a path ends, the rest is left to your people.
Cleric, in detail.
| Row | Cleric | 3AM |
|---|---|---|
| Where it runs | A single-tenant cloud service on Google Cloud in the US. | Wholly inside your network, air-gapped if you need. The only call out is a signed license check. |
| What happens to your data | Queries at runtime; stores queries, reasoning and evidence extracts. | Each question runs where the data lives and a small answer comes back. Nothing is copied out. |
| How it reaches a cause | LLM hypotheses tested against production, with confidence scores. | A live check on your systems that can only pass if the cause is real. |
| What it can change | Fix pull requests that engineers approve; recovery checked for up to 14 days. | Dry-runs the fix, applies it with approval, then proves the system recovered. |
| Who signs a change | No multi-person approval found. | Two different people, on one plan that cannot change after they sign. |
Where it runs
Cleric. A single-tenant cloud service on Google Cloud in the US.3AM. Wholly inside your network, air-gapped if you need. The only call out is a signed license check.What happens to your data
Cleric. Queries at runtime; stores queries, reasoning and evidence extracts.3AM. Each question runs where the data lives and a small answer comes back. Nothing is copied out.How it reaches a cause
Cleric. LLM hypotheses tested against production, with confidence scores.3AM. A live check on your systems that can only pass if the cause is real.What it can change
Cleric. Fix pull requests that engineers approve; recovery checked for up to 14 days.3AM. Dry-runs the fix, applies it with approval, then proves the system recovered.Who signs a change
Cleric. No multi-person approval found.3AM. Two different people, on one plan that cannot change after they sign.
The verdict.
Choose Cleric
If you ship often and want regressions caught early, Cleric does that well.
Choose 3AM
If nothing may run outside your network, and the cause must be proven before the fix, not checked after, choose 3AM.
- Nothing may run outside your network
- You want the cause proven before the fix, not after
- Every write needs two signatures
Sources, read November 11, 2026
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
