vLLM
vLLM's release candidates are where the hardware and speculative-decoding seams get sewn.
A side-by-side editorial comparison of Docling and Ollama — release velocity, themes, recent moves, and the top alternatives to consider.
Docling keeps widening the funnel: every release adds another format the parser can swallow.
Docling ships roughly weekly, and the shape of each release is consistent — one or two new input formats or model paths, then a dense list of parser corrections for DOCX, ODF, PDF and PPTX. The latest window adds Outlook .msg with optional attachment listing, an EBCDIC backend, VLM grounding output from Unlimited-OCR, and OpenAI logprobs exposed as generated tokens. Underneath, the OCR layer was restructured into a layout-driven pipeline with configurable modes and a RapidOCR refactor that resolves all PP-OCR languages by version and backbone.
Quantization plumbing, not headline features — Ollama is tuning the runtime it already won on.
The last ten releases are almost entirely runtime and backend work: NVFP4 kernel fusion for faster prefill, a repeat_penalty default change to match other engines, Laguna model support built on MLX and then handed back to upstream llama.cpp, CUDA compute-capability coverage for B200-class cards, and iGPU projector offload. Nearly every entry arrives as a release candidate; finals are rare enough that the v0.32.10 tag is the exception. User-facing surface area has barely moved.
Docling ships roughly weekly, and the shape of each release is consistent — one or two new input formats or model paths, then a dense list of parser corrections for DOCX, ODF, PDF and PPTX. The latest window adds Outlook .msg with optional attachment listing, an EBCDIC backend, VLM grounding output from Unlimited-OCR, and OpenAI logprobs exposed as generated tokens. Underneath, the OCR layer was restructured into a layout-driven pipeline with configurable modes and a RapidOCR refactor that resolves all PP-OCR languages by version and backbone.
Two things are being built at once. The conversion surface keeps broadening toward whatever a document actually arrives as — email, mainframe encodings, scanned pages, audio via Whisper — while the service datamodel grows the knobs a hosted pipeline needs: chunking options and targets, PDF heading-level inference, batch connector sources, configurable stage shutdown timeouts. The steady drip of DOCX and ODF reading-order fixes says fidelity, not throughput, is where the hard problems still are.
Expect the format list to keep extending and the VLM and OCR paths to gain more configurability, with reading-order and list-numbering corrections continuing at the same rate. The agent-skills addition suggests more packaging for agent callers, though the entries show only a first step.
The last ten releases are almost entirely runtime and backend work: NVFP4 kernel fusion for faster prefill, a repeat_penalty default change to match other engines, Laguna model support built on MLX and then handed back to upstream llama.cpp, CUDA compute-capability coverage for B200-class cards, and iGPU projector offload. Nearly every entry arrives as a release candidate; finals are rare enough that the v0.32.10 tag is the exception. User-facing surface area has barely moved.
Ollama is settling into a maintenance posture on the engine and pushing model-specific work upstream rather than carrying local forks — the Laguna implementation was added in one release and removed in favor of llama.cpp two days later. The remaining local investment is in Apple MLX quantization and hardware coverage, where being first to run a checkpoint on consumer silicon is the differentiator. Performance claims are now benchmarked and A/B verified in the notes, which is a change in rigor if not direction.
Expect the next releases to keep chasing new model families on MLX and to keep folding them upstream once llama.cpp catches up. The repeat_penalty default change is the kind of behavior shift that usually generates a follow-up fix once older models start repeating themselves in the wild.
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 Ollama.
vLLM's release candidates are where the hardware and speculative-decoding seams get sewn.
Writer publishes marketing-org strategy; the product changelog stays out of view.
OpenRouter is turning the routing decision itself into the product.
Provider compatibility is where opencode spends its releases now, not features.
Every post is a comparison page, and Pictory is always the answer.
Gemini is widening what it can reach into, while its feed mostly talks scale.
See all Docling alternatives → · See all Ollama alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Docling is currently shipping more aggressively (velocity 6.3 vs 5.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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Docling is currently shipping more aggressively (velocity 6.3 vs 5.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.
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.
Top Ollama alternatives in ai-assistants are ranked by recent ship velocity. Browse the "Ollama alternatives" section above for the current picks, or visit /alternatives/ollama for the full list with editorial commentary on each.