← Back to home
Comparison · ai-assistants

Docling vs ellmer

A side-by-side editorial comparison of Docling and ellmer — release velocity, themes, recent moves, and the top alternatives to consider.

Docling vs ellmer: at a glance

FeatureDoclingellmer
Sectorai-assistantsai-assistants
Velocity score6.32.5
Sparks · 30d00
Top themesdocument-parsing, format-coverage, pluggable-engines, ocrllm, r, observability, agentic tools
Last editorial update10h ago1h ago
WebsiteVisit →Visit →

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.

Read the full Docling trajectory →

What is ellmer?

ellmer stopped being a chat wrapper and started shipping the parts production LLM code needs

ellmer is R's provider-agnostic LLM client, covering Anthropic, OpenAI, Gemini, Bedrock, Databricks, Snowflake, Ollama, Groq and more behind one Chat object with structured output, tool calling and streaming. The last year moved it well past request plumbing: API keys are now fetched through a credentials function rather than stored in the object, provider-native web search and fetch are first-class tools, and every call emits OpenTelemetry spans when a tracer is active. Releases land roughly every six to ten weeks with meaningful content each time.

Read the full ellmer trajectory →

Docling vs ellmer: editorial side-by-side

D
Docling
AI-ASSISTANTS
6.3

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.

E
ellmer
AI-ASSISTANTS
2.5

ellmer stopped being a chat wrapper and started shipping the parts production LLM code needs

◆ Current state

ellmer is R's provider-agnostic LLM client, covering Anthropic, OpenAI, Gemini, Bedrock, Databricks, Snowflake, Ollama, Groq and more behind one Chat object with structured output, tool calling and streaming. The last year moved it well past request plumbing: API keys are now fetched through a credentials function rather than stored in the object, provider-native web search and fetch are first-class tools, and every call emits OpenTelemetry spans when a tracer is active. Releases land roughly every six to ten weeks with meaningful content each time.

◆ Where it's heading

The arc runs from breadth to depth. Early releases raced to add providers; recent ones assume you already picked one and are trying to run it in production — tracing with the gen_ai semantic conventions, prompt caching on by default, parallel and batch chat graduating out of experimental with configurable error handling, and truncated or filtered responses raising warnings instead of passing silently. The credentials rework and automatic key redaction on save show the same instinct applied to secrets.

◆ Prediction

Batch processing has been picking up one provider per release — Gemini and Groq most recently — so the next releases likely continue filling in batch and built-in-tool coverage across the provider list rather than adding new provider integrations.

Alternatives to Docling and ellmer

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 ellmer.

See all Docling alternatives → · See all ellmer alternatives →

Recent activity from Docling and ellmer

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoDoclingRelease CI fix, no user-facing changes
  2. 1d agoDoclingHeading levels inferred from font weight; pluggable CLI engines
  3. 5d agoDoclingOutlook .msg support and Unlimited-OCR grounding
  4. 8d agoDoclingLayout label and PDF picture-in-table fixes
  5. 11d agoDoclingEBCDIC backend, docling agent skills, all PP-OCR languages
  6. 16d agoDoclingChunking options reach the service API
  7. 29d agoellmerellmer 0.4.2
  8. 3mo agoellmerellmer emits OpenTelemetry traces for every chat and tool call
  9. 9mo agoellmerellmer 0.4.0 adds provider-native web search and stops storing API keys
  10. 11mo agoellmerellmer 0.3.2
  11. 11mo agoellmerellmer 0.3.1
  12. 1y agoellmerellmer 0.3.0 adds a universal chat() and rewrites tool specification

Frequently asked questions

What is the difference between Docling and ellmer?

They serve adjacent needs but don't currently overlap on shipped themes. Docling is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 ellmer?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Docling is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 ellmer?

Top ellmer alternatives in ai-assistants are ranked by recent ship velocity. Browse the "ellmer alternatives" section above for the current picks, or visit /alternatives/ellmer-r for the full list with editorial commentary on each.