Marqo
Marqo split its inference layer into services and is now tuning hybrid-search relevance knob by knob.
A side-by-side editorial comparison of ClearML and Docling — release velocity, themes, recent moves, and the top alternatives to consider.
ClearML is hardening the SDK against the artifacts it loads — pickles included.
Recent releases pair hyperdataset work with a steady security pass over the SDK's own inputs. 2.1.7 added an opt-out that blocks processing of pickled artifacts, via a call argument, a config key or CLEARML_BLOCK_PICKLED_ARTIFACTS, and a path-traversal check when import_offline_session extracts a zip; 2.1.6 added integrity-hash verification for pickled DataFrame artifacts; 2.1.8 added a path-traversal check in dataset merging. Alongside that, hyperdatasets gained tagging, version snapshots, single-call publishing and a DataView get method, and 2.1.11 added in-memory data streaming to the storage manager with a 100 MB cap on registration payloads.
Docling keeps widening what counts as a document — now video, charts, and agent skills.
Docling ships roughly weekly, and each release adds input surface rather than polish. In six versions it picked up a video pipeline and InputFormat.VIDEO, legacy binary Office formats, an EBCDIC backend, a BoxNote backend, and native chart parsing across Word, Excel and PowerPoint that keeps the underlying data instead of a rendered image. Fix lists are long and concentrated in the DOCX, ODF and PDF backends, which is where format edge cases actually live.
Recent releases pair hyperdataset work with a steady security pass over the SDK's own inputs. 2.1.7 added an opt-out that blocks processing of pickled artifacts, via a call argument, a config key or CLEARML_BLOCK_PICKLED_ARTIFACTS, and a path-traversal check when import_offline_session extracts a zip; 2.1.6 added integrity-hash verification for pickled DataFrame artifacts; 2.1.8 added a path-traversal check in dataset merging. Alongside that, hyperdatasets gained tagging, version snapshots, single-call publishing and a DataView get method, and 2.1.11 added in-memory data streaming to the storage manager with a 100 MB cap on registration payloads.
Two things are converging. The hyperdataset API is filling in the lifecycle operations a dataset abstraction needs to be usable — snapshot, tag, publish, retrieve — which is the boring work that decides whether people build on it. Meanwhile the SDK is being treated as something that consumes untrusted input, because in a shared experiment tracker it does: an artifact is a file another user uploaded, and Python's default answer to a pickle is to execute it. Blocking that by configuration rather than by default keeps existing pipelines working while giving security-conscious deployments a switch.
Pickle blocking is opt-out today, and the notes give no timeline for flipping the default. The clearer near-term thread is Python 2 removal and the f-string migration, both described as work in progress across several releases.
Docling ships roughly weekly, and each release adds input surface rather than polish. In six versions it picked up a video pipeline and InputFormat.VIDEO, legacy binary Office formats, an EBCDIC backend, a BoxNote backend, and native chart parsing across Word, Excel and PowerPoint that keeps the underlying data instead of a rendered image. Fix lists are long and concentrated in the DOCX, ODF and PDF backends, which is where format edge cases actually live.
Two arcs run in parallel. The conversion core is becoming format-omnivorous — charts, video, mainframe encodings, archive formats — while the service layer grows the plumbing to run it at scale: chunking options and targets, generic batch connector sources, GCS, Azure Blob and Google Drive as both source and target. The agent skills in v2.118.0 point at a third arc: making Docling something an agent drives directly rather than a library a developer wires up.
Expect the video pipeline to fill out using the ASR presets already in the tree, and the service layer to keep absorbing storage backends. The agent-skills entry suggests more agent-facing packaging is next.
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 ClearML or Docling.
Marqo split its inference layer into services and is now tuning hybrid-search relevance knob by knob.
Determined's release feed stops in March 2025, and its last entries are release plumbing.
Pushing the same assistant into every surface it can reach: browser, desktop, robots.
Ships a frontier model roughly monthly, then adds the admin controls weeks later.
Semantic Kernel is in orderly maintenance while Microsoft Agent Framework takes over.
Pictory publishes comparison content daily and product news never.
See all ClearML alternatives → · See all Docling 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 7.5 vs 5.0), with 2 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 7.5 vs 5.0), with 2 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 ClearML alternatives in ai-assistants are ranked by recent ship velocity. Browse the "ClearML alternatives" section above for the current picks, or visit /alternatives/clearml for the full list with editorial commentary on each.
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.