docRefinery vs Reducto

docRefinery is a next-generation extraction system for business processes: each sender's layout is learned once and remembered, fields are governed, and long files are handled at scale, on premises if you need it. Reducto is a parsing platform whose 30+ file types serve retrieval and AI applications, with security paperwork ready today. Pick by what your output does next.

Updated

What each product is for

Both turn PDFs into structured data through an API, so the shortlist is reasonable. The orientation differs. Reducto is a document platform built around parsing: Parse, Extract, Split, Classify and Edit APIs, plus Studio for building pipelines without code. Its breadth of file types follows from that focus on preparing documents for retrieval and AI. docRefinery is built for extraction into business processes. It returns checked, structured data, and each vendor's layout is learned once and remembered. Both handle long documents, and both run inside your own network.

docRefinery and Reducto side by side, checked 4 November 2026
docRefineryReducto
Main jobChecked field data for business processesParsing and extraction APIs for complex documents
Long documentsLong, multi-page files at scale, segmented into the documents inside them; up to 100 MB a fileLong, complex documents; a Split API separates them
File typesPDFs, scans and photographs; spreadsheets (.xlsx, .ods, .csv) on the API where enabled; presentations and wider office formats in development30+ file types, including spreadsheets and slides
Repeat layoutsEach layout learned once, then rememberedPriced per page; no repeat-layout rate on its price list
Output fieldsNamed by you: a plain-language instruction, a Return as alias, a type and a required flag per fieldDefined in the schema you send
Output formatOne shape for every document type: text, alias, field_confidence, location; tables as rowsShaped by the schema in each request
Who sets the fieldsYour organisation, as account configurationExtract docs show the schema sent in each request
CitationsPage and box for every field and table cell, on by defaultPage, box and source text when citations are enabled
ConfidencePer field, against thresholds you set0 to 1 score, available with citations enabled
Human reviewReview queue on paid plans; every change kept and turned into a tested fixStudio citation viewer; a built-in correction queue was not verified
Getting startedREST API with API keys; a workflow from one sample; JSON, CSV and XLSX export; Chrome extension in early accessAPIs, plus Studio for pipelines without code
DeploymentCloud; private VPC or air-gapped on premises on EnterpriseCloud, customer VPC, on premises, air-gapped
ComplianceSOC 2 Type II audit in progress, no report yet; SSO planned for Enterprise, not yet available; no data-residency commitmentsSOC 2 Type II audited; HIPAA with BAAs
PricingFree up to 100 pages a month; paid plans custom, quoted by sales$150 free usage; Extract $20 per 1,000 pages at list

What docRefinery does that Reducto does not, or does differently

docRefinery suits flows where a few hundred layouts cover tens of thousands of documents: invoices from regular vendors, bank statements, purchase orders, loan and claims packets. Ten differences matter most against Reducto.

  • Layout memory. Each sender's layout is learned once and remembered, and re-trained when a form changes, so a supplier's hundredth invoice is recognised on sight and a redesigned template is caught as new.
  • You define the output. Each field has a plain-language instruction, a "Return as" name you choose as its output key, a type and a required flag, so results land in your system under your names, not ours.
  • One output format for every document. Every field returns text, alias, field_confidence and location, and every table returns rows, so one parser handles invoices, statements and IDs alike.
  • Long files, segmented. Long, multi-page files are handled at scale and segmented into the documents inside them, each classified into its type, so a loan packet arrives as separate, typed documents.
  • Governed fields. Owner, admin and member roles decide what may be extracted, from 20 document types and 785 field definitions, and a caller cannot widen that.
  • Null, never a guess. A field that is not on the page comes back null, and a value below the threshold you set per field waits in a review queue for a person.
  • Evidence on by default. By default, every field and table cell carries a confidence score and its page and box unless you turn scoring off for a layout, so nobody has to remember to ask for it.
  • Learns from corrections. A reviewer's correction becomes a suggested fix, tested on that layout's own documents before anyone applies it.
  • Plug and play. API keys with expiry, revocation and an activity log; a workflow designed from one sample document; export to JSON, CSV or XLSX that always reflects corrections; and a Chrome extension, in early access and not yet in the Chrome Web Store, that runs a document and fills the web form in the open tab.
  • Custom types at no charge, inside your network. Document types outside the catalogue are trained, hosted and re-trained for you at no charge, in our cloud, your private VPC or air-gapped on your own servers.

Where Reducto leads today

Reducto is more mature, and it is ahead on several things that decide deals. Where we are building the answer, we say so; none of it ships yet.

  • File coverage. Reducto reads 30+ file types, slides included, a breadth that follows from its focus on parsing. If presentations or a long tail of office formats are a primary input today, pick Reducto. Wider office formats, presentations among them, are in development at docRefinery.
  • Retrieval output. Reducto's parsing output is designed for language-model and agent pipelines. Our retrieval pipeline, Parse, is planned and not yet available; the roadmap shows where it stands.
  • Parsing track record. Parsing is Reducto's core product. We publish no accuracy benchmark of our own, so we will not claim to beat it on parsing quality.
  • Security review. Reducto says it is SOC 2 Type II audited, with the report on request, and signs BAAs for HIPAA workloads on Growth and Enterprise plans. It describes zero data retention options too. docRefinery's SOC 2 Type II audit is in progress and there is no report yet, so a buyer who needs a report today should pick Reducto. Ask us for the latest status.
  • Published list prices. You can model a budget from its pricing page without talking to anyone. Past our free Starter plan, our rate comes from sales.
  • Writing back to documents. Its Edit API fills finished PDF and DOCX files. We do not offer an equivalent.

How the pricing differs

Reducto charges by the page, per operation. Its list rates are $10 per 1,000 pages for Parse, $20 for Extract and $40 for Deep Extract, with parsing included in Extract, and a 20% discount on batch Parse and Extract jobs. Its docs add that dense extractions of over 100 fields a page may incur a per-field surcharge. Contracted customers may have different rates. docRefinery is free up to 100 pages a month, and paid plans are custom, quoted to your volume.

Common questions

Is docRefinery a good Reducto alternative?

Yes, when the output feeds a business process. 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. It segments long multi-page files into the documents inside them, remembers each vendor's layout, learns from reviewer corrections, and runs in your own VPC or fully air-gapped. Reducto is the better pick today if you need presentations or a long tail of office formats, which is in development here, or if the output feeds a retrieval system.

Does docRefinery handle long documents like Reducto?

Yes. docRefinery handles long, multi-page files at scale and segments a long file into the documents inside it, then extracts each against its own fields. Files up to 100 MB are accepted. Reducto also handles long documents and offers a Split API, so test both on your own longest files.

Does Reducto charge per field?

Reducto's pricing page says usage is charged per page. Its documentation adds that dense extractions of over 100 fields a page may incur a per-field surcharge. This was checked on 4 November 2026.

Can both run inside my own network?

Yes. Reducto describes customer VPC, on-premises and air-gapped deployment. docRefinery offers private VPC and air-gapped on-premises deployment on its Enterprise plan.

Which is more accurate?

We cannot say. docRefinery publishes no accuracy benchmark, so the fair test is to run a sample of your own documents through both and compare the results field by field.

Sources

  1. Reducto pricing
  2. Reducto home page
  3. Reducto usage and pricing docs
  4. Reducto Extract docs
  5. Reducto docs overview
  6. Reducto security, compliance and deployment

Related

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.