btm
BTM has shipped nothing but compiler and integration compliance since 2020
Comparison · ai-assistants
Docling vs ragnar
A side-by-side editorial comparison of Docling and ragnar — release velocity, themes, recent moves, and the top alternatives to consider.
Docling vs ragnar: at a glance
What is Docling?
Docling keeps swallowing new formats, and now the parsing engines behind them are swappable.
Docling converts an unusually wide set of document formats into a single structured representation, and the release train is dense: nine releases in a month, most carrying one or two new capabilities under a long tail of backend fixes. The recent work splits cleanly in two directions. Format reach keeps extending outward (Outlook .msg, EBCDIC, legacy binary Office formats, video), while the internals are being pulled apart into selectable components: v2.120.0 exposes --layout-engine and --table-structure-engine on the CLI, and the OCR layer was refactored to resolve PP-OCR languages by version and backbone. Parsing fidelity work is concentrated in docx, pptx and odf, where reading order and list structure are still being corrected release over release.
What is ragnar?
ragnar turned its RAG store into an MCP server, so coding agents can search it directly.
ragnar builds retrieval-augmented generation stores in R on DuckDB, handling document chunking, embedding, and hybrid vector plus BM25 retrieval, and registering itself as a tool for ellmer chats. Version 0.3.0 adds mcp_serve_store(), which exposes a store over MCP to local clients such as Codex CLI and Claude Code, alongside Azure AI Foundry and Snowflake Cortex embedding providers. Store version 2, introduced in 0.2.0, brought chunk deoverlapping on retrieval and automatic heading augmentation.
Docling vs ragnar: editorial side-by-side
Docling
6.3AI-ASSISTANTS
Docling keeps swallowing new formats, and now the parsing engines behind them are swappable.
◆ Current state
Docling converts an unusually wide set of document formats into a single structured representation, and the release train is dense: nine releases in a month, most carrying one or two new capabilities under a long tail of backend fixes. The recent work splits cleanly in two directions. Format reach keeps extending outward (Outlook .msg, EBCDIC, legacy binary Office formats, video), while the internals are being pulled apart into selectable components: v2.120.0 exposes --layout-engine and --table-structure-engine on the CLI, and the OCR layer was refactored to resolve PP-OCR languages by version and backbone. Parsing fidelity work is concentrated in docx, pptx and odf, where reading order and list structure are still being corrected release over release.
◆ Where it's heading
The engine layer is where the interesting movement is. Docling is shifting from one opinionated pipeline to a set of interchangeable layout, table and OCR backends the caller picks per run, which turns the library into a harness for models rather than a fixed parser. A second thread worth watching: the project shipped agent skills for itself in v2.118.0 and added uvx installation docs for them in v2.120.0, alongside a separate docling-client package, all of which point at being consumed programmatically by agents rather than only imported as a Python library. The heading-level inference from font weight, slant and case in v2.120.0 shows the other half of the strategy, extracting structure from typography rather than from markup.
◆ Prediction
Expect the --layout-engine and --table-structure-engine selection to spread from the CLI into the service API, which already gained heading-level inference and chunking options in the last two releases. The agent-skills and docling-client threads are too new across two releases to call a direction with confidence.
ragnar
0.0AI-ASSISTANTS
ragnar turned its RAG store into an MCP server, so coding agents can search it directly.
◆ Current state
ragnar builds retrieval-augmented generation stores in R on DuckDB, handling document chunking, embedding, and hybrid vector plus BM25 retrieval, and registering itself as a tool for ellmer chats. Version 0.3.0 adds mcp_serve_store(), which exposes a store over MCP to local clients such as Codex CLI and Claude Code, alongside Azure AI Foundry and Snowflake Cortex embedding providers. Store version 2, introduced in 0.2.0, brought chunk deoverlapping on retrieval and automatic heading augmentation.
◆ Where it's heading
The package keeps widening who can reach a store and how many ways they can query it. Retrieval accepts vectors of queries, the ellmer tool withholds chunks it has already returned so an agent can dig deeper across calls, and now the store is reachable from outside R entirely. Embedding providers are added steadily — LM Studio, then Azure and Snowflake — which keeps the store portable across whoever supplies the vectors. Breaking changes are accepted readily at this stage, including a renamed default tool prefix and a flipped default in ragnar_find_links().
◆ Prediction
More MCP surface is the natural next step now that serving exists, since the retrieval tool already has the multi-query and no-repeat behavior that agent-driven search depends on.
Alternatives to Docling and ragnar
Other ai-assistants products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Docling or ragnar.
word2vec
word2vec for R spent its 0.4 release proving two training paths give identical embeddings
doc2vec
doc2vec's one directional release added topic discovery to a document-embedding package
udpipe
udpipe's last six releases are entirely compiler fixes, with no NLP change among them.
nametagger
An R binding to NameTag that has not gained a feature since its 2020 debut.
sentencepiece
The R binding to Google's tokenizer has shipped nothing but compiler fixes since 2021.
See all Docling alternatives → · See all ragnar alternatives →
Recent activity from Docling and ragnar
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoDoclingRelease CI fix, no user-facing changes
- 1d agoDoclingHeading levels inferred from font weight; pluggable CLI engines
- 5d agoDoclingOutlook .msg support and Unlimited-OCR grounding
- 8d agoDoclingLayout label and PDF picture-in-table fixes
- 12d agoDoclingEBCDIC backend, docling agent skills, all PP-OCR languages
- 16d agoDoclingChunking options reach the service API
- 6mo agoragnarmcp_serve_store() exposes a RagnarStore over MCP ⚡
- 0y agoragnarRetrieval tool withholds already-returned chunks for deeper search
- 1y agoragnarStore version 2 adds chunk deoverlapping and heading augmentation
Frequently asked questions
What is the difference between Docling and ragnar?
They serve adjacent needs but don't currently overlap on shipped themes. Docling is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Docling better than ragnar?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Docling is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other ai-assistants products to evaluate alongside.
What are the best alternatives to Docling?
Top Docling alternatives in ai-assistants are ranked by recent ship velocity. Browse the "Docling alternatives" section above for the current picks, or visit /alternatives/docling for the full list with editorial commentary on each.
What are the best alternatives to ragnar?
Top ragnar alternatives in ai-assistants are ranked by recent ship velocity. Browse the "ragnar alternatives" section above for the current picks, or visit /alternatives/ragnar-r for the full list with editorial commentary on each.