Nautobot
Nautobot 3.3 alpha adds API rate limits while 3.2.9 stops cross-user token reads.
A side-by-side editorial comparison of Databricks and SpinupWP — release velocity, themes, recent moves, and the top alternatives to consider.
Databricks lands DBR 18.2 GA on Spark 4.1; the 18.x line is the active story, older LTS pages are mostly doc refreshes.
The substantive shipping event in the window is Databricks Runtime 18.2 GA on May 4, the latest minor in a fast 18.x cadence on Spark 4.1.0 (18.0 in January, 18.1 in March, 18.2 Beta on April 8, GA on May 4). The rest of the recent feed is an April 13 documentation refresh that updated release notes for older LTS versions — 14.3, 15.4, 16.4, 17.3, 13.3 — without new shipping behind them.
SpinupWP now writes DNS records for you, starting with Cloudflare and Route 53.
SpinupWP is moving server and site work out of SSH and third-party consoles into its own dashboard and API. September completed the site-settings API, October's dashboard rebuild added bulk actions, labels and filters, and on November 3 SpinupWP began managing A records through Cloudflare and Route 53. The API now also lists and manages SSH keys for accounts and site users.
The substantive shipping event in the window is Databricks Runtime 18.2 GA on May 4, the latest minor in a fast 18.x cadence on Spark 4.1.0 (18.0 in January, 18.1 in March, 18.2 Beta on April 8, GA on May 4). The rest of the recent feed is an April 13 documentation refresh that updated release notes for older LTS versions — 14.3, 15.4, 16.4, 17.3, 13.3 — without new shipping behind them.
Databricks is pushing Spark 4.1 hard through the runtime line: JDK 21 default in 18.x, breaking changes around NULL preservation and partition columns, aggressive deprecation of older behaviors (input_file_name removal, AWS SDK v1 shading). The 18.x cadence is roughly one minor every six weeks, and 16.4 LTS is acting as the bridge for customers needing to migrate Scala 2.12 code to 2.13 before they can move to 17 or 18.
Expect an 18.x LTS designation later in 2026 once the line stabilizes, with continued behavioral hardening and more shaded dependency cleanup. Doc refreshes for older LTS versions — particularly 13.3 LTS, which is close to its August 2026 end-of-support — will likely keep landing as Databricks pushes customers up the runtime stack.
SpinupWP is moving server and site work out of SSH and third-party consoles into its own dashboard and API. September completed the site-settings API, October's dashboard rebuild added bulk actions, labels and filters, and on November 3 SpinupWP began managing A records through Cloudflare and Route 53. The API now also lists and manages SSH keys for accounts and site users.
Each release removes one more step a WordPress operator used to do elsewhere: PHP settings, software updates, disabling sites, and now DNS. The pattern points to a full site lifecycle, from creation through deletion, handled inside SpinupWP.
More DNS providers are the likely next step, since the launch says it is starting with two; whether DNS management also reaches the API is not shown in the entries.
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 Databricks or SpinupWP.
Nautobot 3.3 alpha adds API rate limits while 3.2.9 stops cross-user token reads.
One Node.js Brotli bug and a compromised CA bundle force ten patches across the Elastic Stack.
OpenMQTTGateway returns after 22 months with a security-first 1.9.0.
Parse Server 9.11.1 alphas close two beforeSave advisories, one a server crash.
GitLab sells Orbit as the evidence layer for agent pilots and AI-code rules.
Kestra's feed is design-system package releases while 2.1.0 waits past its first RC.
See all Databricks alternatives → · See all SpinupWP alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Databricks and SpinupWP are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. Databricks and SpinupWP are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Databricks alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Databricks alternatives" section above for the current picks, or visit /alternatives/databricks for the full list with editorial commentary on each.
Top SpinupWP alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "SpinupWP alternatives" section above for the current picks, or visit /alternatives/spinupwp for the full list with editorial commentary on each.