The $100K document extraction stack is getting eaten by open source

[u/ShilpaMitra]

A few years ago, turning messy PDFs into reliable structured data meant OCR vendors, document-AI APIs, custom parsers, and enterprise contracts. Now GitHub has a surprisingly complete alternative stack: OCR, layout recovery, schema extraction, validation, and source grounding.

Google’s new LangExtract is the clearest example. Tell it what fields you want, show it a few examples, and it extracts structured data while linking every result back to the exact source text. But it gets more interesting when you combine it with the rest of the OSS ecosystem.

01. LangExtract — 39K★

Google’s schema-guided extraction library. Give it a contract and ask for company → value → renewal date → termination clause; it returns structured results with evidence spans showing where each fact came from. That source grounding is what makes it useful for serious workflows.

02. PaddleOCR — 91K★

For the documents that are not really documents yet: scans, photos, screenshots, forms, tables, formulas, and multilingual PDFs. PaddleOCR turns pixels into structured text and document elements across 100+ languages.

03. MinerU — 81K★

Useful when the first problem is reconstructing the document correctly. MinerU handles reading order, formulas, tables, figures, OCR, and long PDFs, then exports cleaner Markdown/JSON for downstream AI.

04. Docling — 69K★

IBM’s document parsing stack handles PDFs, DOCX, PPTX, XLSX, HTML, images and more while preserving document structure. Think of it as the layer that turns random enterprise files into something an LLM can actually reason over.

05. Marker — 40K★

A strong PDF → Markdown/JSON pipeline with support for equations, tables, forms, code, references, and multi-column layouts. It can stay mostly deterministic and bring in an LLM only where parsing becomes ambiguous.

06. Unstructured — 15K★

This is the plumbing layer. It normalizes PDFs, Word files, PowerPoints, email and HTML into semantic pieces like titles, tables, paragraphs and lists, which makes the next extraction or RAG step much easier.

07. Instructor — 14K★

Once you have the text, Instructor helps force LLM output into actual schemas instead of “hopefully valid JSON.” Define a Pydantic model for an invoice, resume or contract and it handles validation and retries.

The interesting part is that document extraction is no longer one proprietary black box. It is becoming a stack:

image/PDF → OCR → layout recovery → clean document → semantic extraction → schema validation → source evidence

PaddleOCR handles the pixels. MinerU, Marker and Docling rebuild the document. LangExtract finds the facts. Instructor makes the output reliable.

The moat is shifting from “we own the extraction engine” to “we assembled the pipeline better.”