HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
A side-by-side editorial comparison of mize and Retool — release velocity, themes, recent moves, and the top alternatives to consider.
A numerical optimization toolkit that has been feature-complete and quiet since 2017
mize provides a configurable interface to unconstrained numerical optimization methods - line searches, gradient descent variants, quasi-Newton updates - usable both as a one-shot call and as a stepwise iterator. Its functional surface has not changed since the initial CRAN release in July 2017. Every release since has been a patch: R-devel compatibility, line search edge cases, and in 2026's 0.2.5 the removal of LazyData from DESCRIPTION plus deletion of some flaky tests.
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.
mize provides a configurable interface to unconstrained numerical optimization methods - line searches, gradient descent variants, quasi-Newton updates - usable both as a one-shot call and as a stepwise iterator. Its functional surface has not changed since the initial CRAN release in July 2017. Every release since has been a patch: R-devel compatibility, line search edge cases, and in 2026's 0.2.5 the removal of LazyData from DESCRIPTION plus deletion of some flaky tests.
The pattern is a stable library rather than an abandoned one. Fixes address real reports - a bracket_step error when the Schmidt line search exhausts its function evaluation budget, an incorrect gradient count under backtracking with a specified step_down - and the maintainer used one release note to clarify that backtracking behaviour differs depending on whether step_down is supplied, which reads as answering a recurring question. The five and a half year gap between 0.2.4 and 0.2.5 is the clearest signal: the package is maintained on demand, not developed.
Expect nothing until an R or CRAN policy change forces another compliance patch, which is what triggered the most recent release.
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 mize 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.
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 mize alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "mize alternatives" section above for the current picks, or visit /alternatives/mize 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.