Drizzle ORM
Drizzle's v1.0 release candidates land a JIT mapper rework, new codecs, and a breaking casing API
A side-by-side editorial comparison of DatoCMS and Retool — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | DatoCMS | Retool |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 2.5 | 10.0 |
| Sparks · 30d | 0 | 1 |
| Top themes | headless-cms, media-management, security, cli-dx | self-hosted, retool-4.0, rbac, enterprise-governance |
| Last editorial update | 1mo ago | 2d ago |
| Website | — | Visit → |
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.
Retool pushes self-hosted 4.0 to stable, laying RBAC and security groundwork for enterprise.
Retool's self-hosted line dominates this window: version 4.0 has reached the stable channel, carrying an automatic permissions-database migration that prepares the platform for Role-Based Access Control, with an upgrade FAQ to guide existing deployments. Around it, admins gain new controls — customizable Content Security Policy for apps — and a way to buy additional AI credit packs from organization settings. The cadence is dense and operational, centered on shipping and de-risking the 4.0 upgrade for self-hosters.
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.
Retool's self-hosted line dominates this window: version 4.0 has reached the stable channel, carrying an automatic permissions-database migration that prepares the platform for Role-Based Access Control, with an upgrade FAQ to guide existing deployments. Around it, admins gain new controls — customizable Content Security Policy for apps — and a way to buy additional AI credit packs from organization settings. The cadence is dense and operational, centered on shipping and de-risking the 4.0 upgrade for self-hosters.
Retool is advancing its self-hosted enterprise story — RBAC groundwork, CSP customization, and a managed upgrade path point to a focus on admin control and security posture for regulated, self-hosted deployments. Separately, AI usage is becoming a metered, separately-purchased resource. The platform is maturing self-hosted governance while turning AI into a billable line item.
Expect Role-Based Access Control to ship as a full feature on the back of the 4.0 permissions migration, plus continued 4.0 hardening — stable patches and more admin security controls.
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 DatoCMS or Retool.
Drizzle's v1.0 release candidates land a JIT mapper rework, new codecs, and a breaking casing API
Warp drops the terminal framing to bet on cloud software factories and agent orchestration
Unleash leans hard into AI-agent governance and self-hosting as its crawled feed fills with thought-leadership.
GitHub spends the week hardening enterprise governance and supply-chain security.
Resend keeps widening from a raw email API into agent-native tooling and audience management.
Very high-cadence sandbox infra building the primitives agents need to run code
See all DatoCMS alternatives → · See all Retool alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Retool is currently shipping more aggressively (velocity 10.0 vs 2.5), with 1 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. Retool is currently shipping more aggressively (velocity 10.0 vs 2.5), with 1 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 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.
Top Retool alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Retool alternatives" section above for the current picks, or visit /alternatives/retool for the full list with editorial commentary on each.