Compare
Hadrian vs Kaaj: Case OS vs Underwriting Point Solution
When Kaaj is the better choice
Kaaj is the stronger choice if you already have a functional LOS and your specific bottleneck is the speed and quality of credit memo creation — it converts messy borrower packages into structured analysis in under 5 minutes and has named equipment-finance customers to show for it.
When Hadrian wins
Hadrian fits teams that need a full origination case OS — not just faster credit memos, but governed intake, verification, and a tamper-evident audit ledger that keeps the record of every decision in one place you can hand to an auditor.
Hadrian vs Kaaj
| Capability | Hadrian | Kaaj |
|---|---|---|
| Scope of coverage | Full case lifecycle: intake → verify → decide → close, with audit ledger throughout | Underwriting intelligence point solution: borrower package → credit memo in <5 min; designed to layer on an existing LOS |
| Replaces or layers? | Standalone case operating system — can be the primary workflow tool | Explicitly designed NOT to replace your LOS; requires an existing origination system alongside it |
| Target ICP | 2–15 person non-bank lenders: MCA funders, equipment finance, SMB alt-lenders | SMB lenders including equipment finance and MCA; named customers include Amur Equipment Finance, Fundr; $15B+ originations processed |
| Tamper-evident audit ledger | Append-only ledger with signed integrity hashes covers all case lifecycle events | SOC 2 Type II certified; audit-trail posture for underwriting decisions not specifically described in public documentation |
| Evidence graph | First-class data model: claim → evidence → source → confidence, reconstructable on demand | Credit memo and document analysis output; evidence-graph data structure not described in public documentation |
| Operator-gated AI trust dial | Team configures AI autonomy level per workflow — from fully gated (human approves every step) to autonomous | Agentic AI converts packages to analysis; operator trust-dial or autonomy configuration not described in public documentation |
| Time to value | Operator-configured workflows; no rip-and-replace required | ~3 weeks to go-live per public claims; layers on existing stack |
| Multi-vertical case management | Single governance spine applicable across lending, equipment finance, and other case-driven verticals | Focused on SMB lending underwriting; multi-vertical scope not described |
Point solution vs operating system
Kaaj is explicit that it is not a LOS replacement — it accelerates one step of the underwriting workflow and layers on top of whatever origination stack you already use. That is a real strength if you have an existing system and the gap is purely underwriting throughput: Kaaj's claim of converting a borrower package to a credit memo in under 5 minutes, with SOC 2 Type II certification, is a meaningful offering.
The trade-off is that you still need separate systems for case intake, verification steps, decisioning workflow, and close — and the tamper-evident record of what happened across all of those steps lives nowhere specific. Hadrian treats the full origination lifecycle as a single governed case, so the audit trail covers intake through close, not just the underwriting moment.
The audit ledger gap
Kaaj's public positioning describes agentic AI converting document packages to credit analysis — a speed and accuracy story. What it does not describe is a tamper-evident audit ledger or an evidence graph that links each decision to the specific claims and documents behind it.
For a 5-person MCA funder that receives an examiner inquiry or gets a state commercial disclosure request, the question is not just 'how fast was the credit memo?' but 'can you show us exactly what was relied on and why?' That is the record Hadrian is built to produce — and the gap between a fast credit memo and a defensible decision audit.
FAQ
Common questions
Does Kaaj replace a loan origination system?
No — Kaaj is designed to layer on top of an existing LOS rather than replace it. It accelerates the underwriting step specifically (borrower package to credit memo in <5 minutes per their public claims) and requires a separate origination system for the rest of the case lifecycle.
How does Hadrian's evidence graph differ from Kaaj's credit memo output?
A credit memo is an analyst-facing document summarizing the analysis. Hadrian's evidence graph is a machine-readable data structure linking each decision outcome to specific claims, evidence sources, and confidence levels — designed to be reconstructable for an examiner on demand, not just readable by a human at decision time.
The institution around the intelligence
See Hadrian run your case lifecycle — intake to close, every decision audited.
Governance-native case processing for lenders and regulated teams.