OPEN SOURCE DOCUMENT PROCESSING
Many arms.
One API.¶
Your documents, ready for what’s next.
Turn PDFs, Office files, and scans into structured, LLM-ready data. One self-hosted gateway. The right engine for the job.
A SMALLER STACK
Everything you need.
Less to wire together.¶
01 / ROUTING
The right engine, explained.¶
Start with lightweight Xberg. Add engines as you need them. The router selects by format, mode, and available memory, and records why.
02 / STRUCTURE
Different inputs. Same shape.¶
Get Markdown, text, tables, and structured blocks through one versioned schema. Export heading-aware chunks that keep tables intact.
03 / CONTROL
Your infrastructure. Your call.¶
Run locally or deploy with Docker. Choose your engines and connect through Python, the command line, REST, or an MCP client.
FITS YOUR WORKFLOW
Start small.
Build from here.¶
Install the package, parse a document, and put the output to work. Use the same gateway from your terminal, application, or agent.
OCR and layout engines may download model weights on first use.
UNDER THE HOOD
A clear path from file to data.¶
- 01Inspect
Read the format, size, and available resources.
- 02Route
Choose an available engine for the job.
- 03Extract
Parse content, with at most one fallback when needed.
- 04Build
Return a document with content and processing details.
Make your first document useful.¶
A couple of commands is a good place to start.
Doctopus is MIT licensed. Backend packages and model weights have their own licenses.