Sheaf
Sheaf vs LandingAI ADE
LandingAI gives you document operations to compose. Sheaf gives you the finished operations desk — and an API, so you are not trading one for the other.
The short answer
ADE is a set of primitives. Sheaf is a product: an unsorted bundle becomes a filed, approved, provably complete application, with no integration project in between. Sheaf also exposes a REST API and webhooks, so choosing the finished desk costs you no programmability.
Sheaf vs LandingAI ADE at a glance
| Requirement | Sheaf | LandingAI ADE |
|---|---|---|
| Split a mixed bundle | Determined boundaries that tile the file end to end | Split, consuming parse output |
| Setup before first result | None — upload and go | Zero-shot, no training step |
| Order of operations | Preview boundaries, approve scope, then pay to parse | Parse first, then Split reads the parse |
| Grounding | File, page and span, supplied by the reader | Page number and bounding box |
| Missing documents | Named by requirement, recomputed live | Per-document operations |
| Portfolio completeness | One dashboard across every open application | Yours to build |
| Cross-document consistency | Names, dates and amounts checked automatically | Per-document operations |
| Straight-through processing | Per-requirement thresholds you control | Yours to build |
| Filing and approval | Ships as the product | Composable APIs |
| Audit trail | Every outcome walks back to a page and a person | Yours to build |
| API and webhooks | Full REST API, outbound webhooks | API only — no desk to drive |
Where Sheaf wins
- You approve the scope before you pay for it ADE’s Split consumes parse output, so the whole file is parsed before you learn where the documents were. Sheaf inverts it: boundaries are previewed first and you approve what gets read. On a 104-page bundle where four documents mattered, that is the difference between paying for 104 pages and paying for four.
- The desk arrives assembled An application that accumulates documents over months, a filing decision that can be approved and withdrawn, live coverage, an exception queue with SLA tracking, and an audit trail that survives all of it. With primitives, that layer is the project on the other side of the purchase — typically two quarters of engineering before anyone in operations can use it.
- Judgement, not just facts ADE returns what a document contains. Sheaf decides: whether this document satisfies that requirement, whether the borrower’s name matches across all six documents, whether the file is complete, and whether a reviewer’s disagreement should change what happens next time.
- Completeness across the portfolio Sheaf names the requirement nothing satisfied, and rolls that up across every open application into one live number. A per-document API is not positioned to answer either question.
- You keep the API anyway Sheaf’s REST API and outbound webhooks mean the usual trade — product convenience against programmatic control — does not apply. You get the desk and the endpoints.
Where LandingAI ADE is strong
- Grounding Every element carries a page number and a bounding box. It is the right design, and Sheaf holds itself to the same standard.
- Composability Parse, Extract, Classify, Split and Section are cleanly separable. If you are embedding document processing deep inside your own product, that separation is useful.
- Zero-shot from the start No class list, no training cycle. ADE and Sheaf agree here, and both are ahead of the classifier-based platforms.
Two of those three are things Sheaf already matches. The third is only an advantage if you were planning to build a review application from scratch anyway.
Choose Sheaf if
- You want document review finished, not enabled.
- Completeness against a requirement set is what holds your files up.
- You need approval, exception handling and an audit trail an examiner will accept.
- You want an API and a desk, rather than an API and a roadmap.
Choose LandingAI ADE if
- Document processing is a component inside a product you are shipping, and no human ever opens a review screen.
- You have engineering capacity you specifically want to spend on document infrastructure.
The bottom line
ADE sells operations you compose. Sheaf sells the outcome those operations are usually composed toward — and now exposes the same programmability underneath. For any team whose end user is a person reviewing a file, Sheaf is the shorter path by a wide margin.