HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
A side-by-side editorial comparison of daedalus and Retool — release velocity, themes, recent moves, and the top alternatives to consider.
An epidemic-economic model teaching its interventions to react to the outbreak itself.
daedalus couples an infectious-disease model to sector-level economic costs, letting users test non-pharmaceutical interventions against both epidemic and fiscal outcomes. Over autumn 2025 the intervention layer went from a single fixed closure to sequential timed NPIs and then to closures that lift in response to the model's own instantaneous reproduction number. Alongside that, the cost functions were reworked so illness states map more carefully onto lost productivity.
Retool is fencing in its app-building agent — plan mode above, row-level data policies below.
Releases arrive several times a week and split cleanly. One line extends the app-building agent: standing building context, multiple threads per branch, and now a plan mode that shows intended changes before they land. The other tightens administration: PostgreSQL access policies in public beta, BYOK token accounting, an admin onboarding hub, plus self-hosted release and migration notices.
daedalus couples an infectious-disease model to sector-level economic costs, letting users test non-pharmaceutical interventions against both epidemic and fiscal outcomes. Over autumn 2025 the intervention layer went from a single fixed closure to sequential timed NPIs and then to closures that lift in response to the model's own instantaneous reproduction number. Alongside that, the cost functions were reworked so illness states map more carefully onto lost productivity.
The arc is toward a model that behaves like a policy simulator rather than a scenario calculator: interventions now have their own state machine, R_t is computed inside the ODE system, and event handling has been pulled out of the output object. Correction releases sit between the feature ones, including an indexing fix the maintainers flag as required for accurate projections. The versioning is patch-level but the changes are structural.
With R_t and the next-generation matrix now available in-model, the likely next step is richer response rules keyed to those quantities; the entries give no signal on when a stable 1.0 arrives.
Releases arrive several times a week and split cleanly. One line extends the app-building agent: standing building context, multiple threads per branch, and now a plan mode that shows intended changes before they land. The other tightens administration: PostgreSQL access policies in public beta, BYOK token accounting, an admin onboarding hub, plus self-hosted release and migration notices.
The two lines are the same bet. Retool is making agent-built apps acceptable to organizations that cannot let a generated app decide what data it reads, so every agent capability is paired with a constraint — instructions the agent must follow, a plan the reviewer sees, and access policies enforced at the resource rather than in app code. The self-hosted channel keeps pace, which matters for exactly the buyers those controls target.
Expect access policies to extend past PostgreSQL to other resource types as they leave beta, and further review or approval steps around the app-building agent.
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 daedalus or Retool.
France's national flood statistics, ported out of Fortran and into R.
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
Fast design-based estimators for experiments, coasting on CRAN patches.
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
IP address vectors for R that hit 1.0 and then went quiet.
A column-key toolkit for stitching decades of ecological field data into one table.
See all daedalus 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 5.0 vs 0.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. Retool is currently shipping more aggressively (velocity 5.0 vs 0.0), 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 daedalus alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "daedalus alternatives" section above for the current picks, or visit /alternatives/daedalus 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.