WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
A side-by-side editorial comparison of Dokku and inti — release velocity, themes, recent moves, and the top alternatives to consider.
Dokku is quietly turning into a k3s front-end with a JSON-first CLI.
The 0.38 patch line keeps shipping small releases with real features in them. v0.38.27 drops the local-image requirement for k3s deploys, reports Traefik DNS-provider variables as global keys, adds storage directory mode and removal flags, and introduces a vector-cron-sink so scheduled cron output has somewhere to go. It follows v0.38.26, which brought wildcard domains, custom cert issuers, and kernel sysctls to the k3s scheduler.
inti keeps compounding small statistics and publishing tools for plant-science labs.
inti bundles the tooling a plant-science lab uses end to end: the Yupana analysis app, the Tarpuy experiment planner, scihub and rticle document rendering, and helpers for ANOVA and heritability. The 0.7.x line has been dominated by one thread, a PCA sub-module in Yupana carrying variable contribution, dimension correlation, supplementary variables and per-dimension selection. Releases are cumulative: 0.7.0, 0.7.1 and 0.7.2 all restate the same PCA lines, with each tag adding a few items on top, and 0.7.0 itself is split across two tags published 35 seconds apart.
The 0.38 patch line keeps shipping small releases with real features in them. v0.38.27 drops the local-image requirement for k3s deploys, reports Traefik DNS-provider variables as global keys, adds storage directory mode and removal flags, and introduces a vector-cron-sink so scheduled cron output has somewhere to go. It follows v0.38.26, which brought wildcard domains, custom cert issuers, and kernel sysctls to the k3s scheduler.
Two threads run through almost every release: closing the gap between the k3s scheduler and the classic single-host path, and making every command machine-readable. The k3s work has moved from basic scheduling to the operational details — certificates, DNS, sysctls, and now deploys that no longer assume a local Docker image — which is the sequence a project follows when it expects the Kubernetes path to become the default rather than the alternative.
Expect the remaining k3s parity gaps to keep closing one release at a time, and expect the logging work started with vector-cron-sink to extend to other task types that currently have no sink.
inti bundles the tooling a plant-science lab uses end to end: the Yupana analysis app, the Tarpuy experiment planner, scihub and rticle document rendering, and helpers for ANOVA and heritability. The 0.7.x line has been dominated by one thread, a PCA sub-module in Yupana carrying variable contribution, dimension correlation, supplementary variables and per-dimension selection. Releases are cumulative: 0.7.0, 0.7.1 and 0.7.2 all restate the same PCA lines, with each tag adding a few items on top, and 0.7.0 itself is split across two tags published 35 seconds apart.
Two axes are moving. Analysis is deepening inside Yupana, where PCA went from a single view to a sub-module with its own contribution and correlation outputs across three tags. Publishing is widening around rticle() and scihub(), which now handle Google Docs markdown, crossrefs and page numbers, continuing the gdocs2qmd work from the 0.6 line. Neither is a change of direction; the package accretes features where the maintainer's own research workflow needs them.
Expect the next tag to extend the PCA sub-module again and add another rticle() or scihub() rendering detail, on the two-to-six-week cadence the 0.7 line has held.
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 Dokku or inti.
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
A forest plot package that keeps handing users control of one more graphical detail.
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.
Pipeline provenance for tidyverse workflows, recording what changed at each step without keeping the data.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dokku 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. Dokku 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 Dokku alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dokku alternatives" section above for the current picks, or visit /alternatives/dokku for the full list with editorial commentary on each.
Top inti alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "inti alternatives" section above for the current picks, or visit /alternatives/inti for the full list with editorial commentary on each.