Cronicle
The job scheduler's release stream is now almost entirely vulnerability patching and authorization hardening.
A side-by-side editorial comparison of goodpractice and Windmill — release velocity, themes, recent moves, and the top alternatives to consider.
The R package-quality checker returns from CRAN limbo with checks you can select by category.
goodpractice runs a battery of static checks over an R package — style, complexity, test coverage, documentation, DESCRIPTION hygiene — and reports what a reviewer would flag. The package was archived on CRAN, adopted by rOpenSci in 1.0.5, and version 1.1 is the first substantive release since: every check now belongs to one of 16 named groups, discoverable via all_check_groups() and selectable via checks_by_group(), with group-level exclusion through an option or environment variable and new default_checks() and tidyverse_checks() presets.
Windmill is dismantling the paywall between itself and the data stack
Three of the last six releases are directional: dbt projects running unmodified as a first-class runtime, BigQuery and Snowflake dropping out of the Enterprise tier, and AI sessions enabled by default in beta. Around them sits careful platform work — workspace lineage as the single deployment target, arbitrary-target Compare & Deploy, schema contracts for DuckLake consumers, and in-app git-to-Windmill sync. Entries are written with migration notes and upgrade paths, which is the tone of a product being run by people who expect it in production.
goodpractice runs a battery of static checks over an R package — style, complexity, test coverage, documentation, DESCRIPTION hygiene — and reports what a reviewer would flag. The package was archived on CRAN, adopted by rOpenSci in 1.0.5, and version 1.1 is the first substantive release since: every check now belongs to one of 16 named groups, discoverable via all_check_groups() and selectable via checks_by_group(), with group-level exclusion through an option or environment variable and new default_checks() and tidyverse_checks() presets.
The direction is from a monolithic verdict toward a configurable one. Previously the practical choices were run everything or name individual checks; grouping makes partial adoption tractable, which matters because the full battery is opinionated enough that teams either accept all of it or ignore the tool. The tidyverse_checks() preset makes that explicit — the package is acknowledging that its defaults encode one house style among several. Earlier releases pointed the same way with a configurable cyclomatic complexity limit and adjustable output length.
With grouping and presets in place, the natural next step is per-project persistent configuration so exclusions live in the repository rather than in an option or environment variable.
Three of the last six releases are directional: dbt projects running unmodified as a first-class runtime, BigQuery and Snowflake dropping out of the Enterprise tier, and AI sessions enabled by default in beta. Around them sits careful platform work — workspace lineage as the single deployment target, arbitrary-target Compare & Deploy, schema contracts for DuckLake consumers, and in-app git-to-Windmill sync. Entries are written with migration notes and upgrade paths, which is the tone of a product being run by people who expect it in production.
The company is aiming squarely at data teams and removing every obstacle between them and a self-hosted trial: bring the dbt project as-is, query the warehouse on the community edition, and let the AI build scripts and flows behind the existing draft-and-diff review gate. The governance work advances at the same pace, so the free surface widens without the deployment story loosening. Enterprise is being narrowed to Oracle, MS SQL, and scale rather than to the workloads data teams actually run.
With dbt lineage and DuckLake schema contracts both landed, the likely next step is unifying them — a single asset graph spanning dbt models and materialized tables, with contract validation running across the boundary.
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 goodpractice or Windmill.
The job scheduler's release stream is now almost entirely vulnerability patching and authorization hardening.
Helm runs two release trains in lockstep while v3 walks toward end-of-life.
Quarto's editor extension is quietly becoming Positron-first while keeping VS Code parity.
Ten releases in six days, methodically porting Quarto's surface into a Rust binary.
The metadata cache under pak now speaks to authenticated and corporate repositories.
R's old dependency manager now runs on a vendored copy of its own successor.
See all goodpractice alternatives → · See all Windmill alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Windmill is currently shipping more aggressively (velocity 8.8 vs 0.0), with 3 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. Windmill is currently shipping more aggressively (velocity 8.8 vs 0.0), with 3 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 goodpractice alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "goodpractice alternatives" section above for the current picks, or visit /alternatives/goodpractice for the full list with editorial commentary on each.
Top Windmill alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Windmill alternatives" section above for the current picks, or visit /alternatives/windmill for the full list with editorial commentary on each.