docRefinery vs Extend
Pick docRefinery if operations staff, not AI engineers, will run extraction: you name every output field, every document type returns one JSON shape, each sender's layout is learned once and remembered, long files are segmented, and it can run air-gapped on your own servers. Pick Extend if you need evaluation sets and SOC 2, HIPAA and GDPR answers now.
Updated
Two products that both get better with use
This is the closest comparison on our list, because the feature lists overlap: extraction, classification, splitting, confidence scores, human review, versioning. The difference is what improves. Extend's Studio is built for iterating on a schema, running evals and catching regressions, and its Composer agent refines schemas automatically. docRefinery keeps the sender's layout itself. Theirs tunes the question against a test set. Ours remembers the page.
Neither approach is wrong. A varied document set with a dedicated AI engineer suits the first. A finance team receiving the same few hundred layouts every month suits the second.
| docRefinery | Extend | |
|---|---|---|
| What improves | Each sender's layout, learned once and remembered | Schemas, through evals and the Composer agent |
| Measuring quality | Workflow versions, replay of past runs, field-level compare; no published benchmark | Evals and regression checks in Studio |
| Configuration | Account configuration your admin governs | Inline config per call, or a saved extractor |
| Output fields | Named by you: a plain-language instruction, a Return as alias, a type and a required flag per field | Fields defined in each extraction config |
| Output format | One shape for every document type: text, alias, field_confidence, location; tables as rows | Shaped by each extractor's config |
| Long documents | Long, multi-page files at scale, segmented into the documents inside them | Splitting is part of the product |
| Confidence | Per field, against thresholds you set | Model and OCR confidence per field |
| Review | Review queue on paid plans, every change kept | Multi-pass review agent flags likely errors |
| File types | PDFs, scans and photographs; spreadsheets on the API where enabled; presentations and wider office formats in development | 35+ file types |
| Beyond extraction | Business rules on values | Edit fills forms; Verify flags tampering |
| Getting started | API keys; a workflow from one sample; JSON, CSV and XLSX export; Chrome extension in early access that fills web forms | Studio, APIs and the Composer agent |
| Deployment | Cloud; private VPC or air-gapped on premises on Enterprise | Cloud in the US or EU, BYOC, hybrid; EU data residency on all plans |
| Compliance | SOC 2 Type II audit in progress, no report yet; SSO planned for Enterprise, not yet available; no data-residency commitments | SOC 2, HIPAA and GDPR; third-party penetration tests |
| Pricing | Free up to 100 pages a month; paid plans custom, quoted by sales | 10,000 free credits, then $0.01 per credit |
Where Extend is the better choice
- Proving quality over time. If a stated requirement is to show how a pipeline's accuracy moves release by release, Extend puts evaluation at the centre of the product. Our versions and replay help, but we have no standalone evaluation harness and no published accuracy figure.
- Regulated buyers. Extend says it is certified for SOC 2, HIPAA and GDPR and undergoes regular third-party penetration testing. A BAA is an add-on even on Pay As You Go. docRefinery's SOC 2 Type II audit is in progress with no report yet, and we make no data-residency commitments, so a buyer who needs either today should pick Extend. Ask us for the latest status.
- EU hosting and deployment choice. Extend offers EU data residency on all plans, plus bring-your-own-cloud and hybrid set-ups where documents stay in your cloud.
- Self-serve pricing. Credits are published: Extract runs at 3 credits a page in Performance mode and 0.7 in Light. You can estimate a bill without a call.
- Fraud checks. Verify flags AI-generated documents and signs of tampering. We do not offer this; forgery detection sits on our roadmap as research, which means it may not ship.
- File breadth. Extend lists 35+ file types. Presentations and wider office formats are in development at docRefinery and not yet available.
What docRefinery does that Extend does not, or does differently
docRefinery fits when the input is repetitive and the people running it are operations staff, not ML engineers. Against Extend, these are the differences that show up in daily work.
- Layout memory, not schema tuning. Each sender's layout is learned once and remembered, and re-trained when a form changes, so improvement comes from the documents you already process rather than from an eval set someone maintains.
- You define the output once. Each field has a plain-language instruction, a "Return as" name you choose as its output key, a type and a required flag, held in account configuration rather than passed in each call.
- One output format for everything. Every field returns
text,alias,field_confidenceandlocation, and every table returns rows, so one parser in your code handles every document type. - Governed fields. Owner, admin and member roles decide what may be extracted, and a caller cannot override it. Extend lets developers choose inline or saved configuration.
- Null, never a guess. A field missing from the page comes back null, and anything under its per-field threshold waits in a review queue for a person.
- Corrections that become fixes. A reviewer's correction becomes a suggested fix, tested on that layout's own documents before anyone applies it.
- A workflow from one document. Drop one sample and every printed field is found, ready to keep, relabel or switch off. Business rules, such as line items adding up to the total, run on every document, and each change is a version you can replay against past runs. See it on invoice data extraction and receipts.
- Long files, segmented. Long, multi-page files are handled at scale and separated into the documents inside them, each classified into its type.
- Air-gapped deployment. Beyond our cloud and your private VPC, docRefinery runs fully air-gapped on your own servers on Enterprise. Extend lists its cloud, bring-your-own-cloud and hybrid.
- Plug and play. API keys with expiry, revocation and an activity log, export to JSON, CSV or XLSX that always reflects corrections, a Chrome extension in early access that fills web forms from a document, and custom document types trained and hosted at no charge.
Common questions
What is the main difference between docRefinery and Extend?
Extend centres on tuning and evaluating schemas, with tooling for measuring quality. docRefinery centres on remembering each sender's layout and governing fields at organisation level. Both offer confidence scores and human review.
Does Extend need a schema on every call?
No. Extend's docs show an inline config on each call, or a config saved as an extractor and referenced by ID. This was checked on 4 November 2026.
Is docRefinery a good Extend alternative for a small team?
Yes. docRefinery returns every document type in the same JSON shape under field names you choose, with a confidence score and a page citation on each value. A workflow starts from one sample document, each vendor's layout is remembered, long files are segmented, reviewer corrections become tested fixes, and Starter is free up to 100 pages a month. If you need EU hosting commitments or a formal evaluation suite today, Extend is likely the better fit.
Sources
Related
- Invoice data extractionWhat invoice data extraction should return, why line items are the hard part, where it sits in accounts payable, and what to test in an invoice extraction API.
- Confidence scoresWhat a confidence score in document extraction means, how to set thresholds per field, when to send values to human review, and why null beats a guess.
- ReceiptRead merchant, date, tax, tip and items from receipt photos and PDFs. Faded or creased values go to a reviewer instead of straight into your books.
- docRefinery vs ReductodocRefinery vs Reducto: extraction for business processes against parsing for RAG. Long documents, governed fields, review, on-premises and pricing compared.
- docRefinery vs DocuPipedocRefinery vs DocuPipe: no-template extraction against layouts learned once. Compare confidence, visual review, ISO 27001 and HIPAA, deployment and pricing.
Run the comparison on your own documents.
Send one vendor's invoices through both. The difference shows up on the second document, not the first.
100 pages a month free. No credit card, no sales call.