Gemini
Gemini is adding host surfaces faster than it documents them — Chrome, macOS, robots, video.
A side-by-side editorial comparison of Firecrawl and Docling — release velocity, themes, recent moves, and the top alternatives to consider.
Firecrawl is rebuilding web scraping as token-cheap, grounded infrastructure for agents.
Firecrawl has moved well past 'turn a page into Markdown.' Nearly every recent release optimizes for the two things agents care about: minimal tokens and provable grounding. Question and Highlights formats, an excerpt-returning /search, and the arXiv/GitHub Research Index all hand back just the relevant lines with citations instead of whole pages, repeatedly claiming benchmark wins and '10-100x fewer tokens.' A parallel security track (Lockdown Mode, PII redaction, prompt-injection hardening) and a monitoring track that watches first pages, then the whole web, round it out.
Docling is turning a document parser into a general ingestion layer — video now included.
Docling ships a tight semantic-release train, roughly weekly, where each version pairs one or two format or pipeline features with a long tail of fidelity fixes. The fixes are the real product: reading order in docx lists, section headers and footers, ODF text after inline elements, PPTX shapes in visual order, dehyphenation of hard continuations. Alongside the library, a service layer is taking shape — chunking options and targets, PDF heading-level inference, and batch connector sources are all being exposed through the service API rather than only the Python interface.
Firecrawl has moved well past 'turn a page into Markdown.' Nearly every recent release optimizes for the two things agents care about: minimal tokens and provable grounding. Question and Highlights formats, an excerpt-returning /search, and the arXiv/GitHub Research Index all hand back just the relevant lines with citations instead of whole pages, repeatedly claiming benchmark wins and '10-100x fewer tokens.' A parallel security track (Lockdown Mode, PII redaction, prompt-injection hardening) and a monitoring track that watches first pages, then the whole web, round it out.
The product is consolidating into an agent-native web-data platform where every endpoint is judged on accuracy-per-token. The benchmark-and-efficiency framing — SimpleQA, arXivQA, token counts — is now the through-line of releases, and the search, monitor, and research surfaces are converging toward a single 'give an agent a goal, get grounded results' interface.
Next moves likely extend the custom relevance model to more endpoints and broaden the Research Index past arXiv, with continued emphasis on published benchmark wins over rival search and scrape APIs.
Docling ships a tight semantic-release train, roughly weekly, where each version pairs one or two format or pipeline features with a long tail of fidelity fixes. The fixes are the real product: reading order in docx lists, section headers and footers, ODF text after inline elements, PPTX shapes in visual order, dehyphenation of hard continuations. Alongside the library, a service layer is taking shape — chunking options and targets, PDF heading-level inference, and batch connector sources are all being exposed through the service API rather than only the Python interface.
Format coverage is expanding outward from PDF and Office into anything an enterprise has lying around: legacy binary Office formats, an EBCDIC backend for mainframe data, and video as a declared input format with ASR presets behind it. The model layer is broadening in parallel — RapidOCR refactored to resolve all PP-OCR languages, a layout-driven OCR pipeline with configurable modes, and VLM output now carrying OpenAI logprobs through to predictions. Packaging is being taken seriously too, with chart extraction lazy-loaded so the slim build needs no torch, and agent skills shipped for driving Docling directly.
With VideoPipeline declared and ASR presets in place, the next step is likely fleshing out what a video actually converts into — transcript segments tied to frames — rather than adding another document format.
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 Firecrawl or Docling.
Gemini is adding host surfaces faster than it documents them — Chrome, macOS, robots, video.
LiveKit Agents keeps absorbing voice vendors while turn detection stays the real product
LangGraph's real work is happening in the checkpoint layer, not the graph runtime
Comet is annexing AI cost governance from the observability side.
Two platform rewrites in four months, then the feed went quiet.
The feed is an SEO content mill, not a changelog — no Botsify release has been published here.
See all Firecrawl 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. Firecrawl and Docling are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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. Firecrawl and Docling are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other ai-assistants products to evaluate alongside.
Top Firecrawl alternatives in ai-assistants are ranked by recent ship velocity. Browse the "Firecrawl alternatives" section above for the current picks, or visit /alternatives/firecrawl 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.