StackMap
Subscribe
Explore / xberg
xberg-io

xberg

Rust-core extraction orchestrator with 15 language bindings: 96 formats — PDF, Office, images, audio, code, web — to clean text, tables and RAG-ready chunks. OCR and structured extraction built in.

9,417 593 Rust MITupdated today
View on GitHubDispute this mapping →
Curator's take

The polyglot pick: reach for Xberg when your stack spans Rust, Python, Node, Go, the JVM or WASM and you want ONE extraction engine instead of a per-language pipeline. Handles 96 formats — PDFs, Office, images, audio/video (Whisper), source code (306 languages, syntax-aware chunking) — and websites, dynamic pages included. OCR is built in, not bolted on: ONNX and Candle models run locally, or any VLM (Gemini, Mistral, …) through LiteLLM; on top sit structured extraction to a JSON schema and NER, keywords, classification and captioning. Think of it as a parallel extraction orchestrator with a plugin architecture — a MinerU backend or your own local VLM can sit behind it — rather than a single parser. It's the v1 successor to Kreuzberg. Don't reach for it if all you need is max-fidelity parsing of messy scanned PDFs and nothing else (a dedicated VLM like MinerU or olmocr is the shorter path, though either can also run behind Xberg), or if you're Python-only and already committed to LlamaIndex's own readers.

Mapped by ShipWithAI editors · links verified

Continue your stack

What teams reach for next — and why each earns a place beside xberg. Ranked by curator confidence.

pairs wellpairs wellalternativealternativealternativealternativealternativeChromaLlamaIndexMinerUolmocrpdf-inspectorUnlimited-OCROfficeCLIxberg
pairs wellalternativebuilt withpick a node for the why · open it from the panel
Weekly digest
README.md1 min read

Xberg

Extract clean text, tables, and structured data from documents and