ToolJet
ToolJet runs two release trains at once, and neither has changed direction in months
A side-by-side editorial comparison of Biome and DatoCMS — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Biome | DatoCMS |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 5.0 | 2.5 |
| Sparks · 30d | 0 | 0 |
| Top themes | lint-rules, markdown-support, framework-coverage, css-formatter | headless-cms, media-management, security, cli-dx |
| Last editorial update | 5h ago | 3mo ago |
| Website | Visit → | — |
Biome's patch train keeps adding rules — and is quietly growing a Markdown linter.
Six patch releases since mid-June, each mixing new nursery rules with parser and formatter fixes. 2.5.8 adds useReactCompiler, which surfaces React Compiler's own lint diagnostics through Biome, and makes HTML style attribute values parse as CSS so every CSS rule applies inside them. Framework coverage keeps deepening — Svelte legacy {@const} tags, Vue instance properties, Tailwind arbitrary values — and the JavaScript API package reached 6.0.0 with a byte-to-UTF-16 span helper.
Headless CMS spends April hardening the developer surface and adding antivirus to the media pipeline.
DatoCMS is a headless CMS. April brought a security upgrade (automatic antivirus scanning across every Media Area upload, with CDN purge on detection), three coordinated CLI/DX improvements (unscoped npm package, OAuth-based project linking, plugin scaffolds in Astro and Next.js starters), and a Developer Plan API limit bump. Earlier in the window: in-CMS video editing alongside the existing image editor, permissions for Asset Collections, and pre-filtered linked record menus.
Six patch releases since mid-June, each mixing new nursery rules with parser and formatter fixes. 2.5.8 adds useReactCompiler, which surfaces React Compiler's own lint diagnostics through Biome, and makes HTML style attribute values parse as CSS so every CSS rule applies inside them. Framework coverage keeps deepening — Svelte legacy {@const} tags, Vue instance properties, Tailwind arbitrary values — and the JavaScript API package reached 6.0.0 with a byte-to-UTF-16 span helper.
The rule set is widening along two axes at once: frameworks and file types. Framework rules are now specific enough to argue about Svelte runes rather than generic JavaScript, and CSS handling has pushed into HTML attributes and registered custom properties. The larger move sits in 2.5.8's PR list rather than its changelog — a markdown linter, a markdown rule generator, a markdownlint rule source, a two-phase markdown parser, and a first rule in useTopLevelHeading, none of it documented for users yet.
Markdown linting looks close enough to ready that it should appear in the changelog proper rather than the PR list, most likely as nursery rules in the next minor.
DatoCMS is a headless CMS. April brought a security upgrade (automatic antivirus scanning across every Media Area upload, with CDN purge on detection), three coordinated CLI/DX improvements (unscoped npm package, OAuth-based project linking, plugin scaffolds in Astro and Next.js starters), and a Developer Plan API limit bump. Earlier in the window: in-CMS video editing alongside the existing image editor, permissions for Asset Collections, and pre-filtered linked record menus.
Two parallel threads — cleaner developer onboarding (OAuth CLI replacing copy-paste tokens, plugin scaffolds shipped with starters, npx that just works) and treating the Media Area as a more hardened surface (in-CMS editing, asset permissions, antivirus). The CLI work reads as DatoCMS investing in becoming the type of CMS a developer can integrate without three copy-paste rituals.
Expect the OAuth CLI to become the only documented path within a few releases, more antivirus-style trust features (likely SOC-2 attested workflows or content-policy scanning), and starter-kit ecosystem investment that widens framework support beyond Astro and Next.js.
Other Infra & APIs 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 Biome or DatoCMS.
ToolJet runs two release trains at once, and neither has changed direction in months
Honeycomb bets that the agent, not the engineer, should notice the anomaly first
Jenkins is shrinking its own war file and rebuilding its UI, one weekly release at a time
Copilot's model roster churns weekly while GitHub quietly rewires policy and billing plumbing
Nexus does the diagnosis; the rest is on-call plumbing
Four channels, one fix stream — werf's releases are mostly concurrency repairs.
See all Biome alternatives → · See all DatoCMS alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Biome is currently shipping more aggressively (velocity 5.0 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Biome is currently shipping more aggressively (velocity 5.0 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 Infra & APIs products to evaluate alongside.
Top Biome alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Biome alternatives" section above for the current picks, or visit /alternatives/biome for the full list with editorial commentary on each.
Top DatoCMS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "DatoCMS alternatives" section above for the current picks, or visit /alternatives/datocms for the full list with editorial commentary on each.