Heroku
Runtime bumps most weeks, but a new stack, a stack deprecation and an AI model cull underneath
A side-by-side editorial comparison of Laravel and Gravity Forms — release velocity, themes, recent moves, and the top alternatives to consider.
Laravel runs two release trains at once, and 13.x is where anything interesting lands.
Releases alternate between the 12.x and 13.x branches on a roughly weekly cadence, each a flat list of merged pull requests. 12.x receives fixes almost exclusively — lost-connection detection, Postgres whereDate crashes, deprecation logging, schedule:list timezone handling. 13.x gets the additions: a monthly log driver, first-party image handling, modelKeys() on the query builder, an array_keys validation rule, and a steady stream of queue-fake testing improvements.
Gravity Forms 3.0 makes accessible forms the default, not a checkbox someone forgets
Gravity Forms shipped 3.0 in late July after a beta-then-RC run, and the release is built around two things: international phone number handling and accessibility settings that are switched on for every new form. Around that core release, the team keeps a steady add-on cadence going — Dropbox, Trello, Conversational Forms and Pipe all took point releases in the same window. The main plugin and its integration catalog move on separate clocks.
Releases alternate between the 12.x and 13.x branches on a roughly weekly cadence, each a flat list of merged pull requests. 12.x receives fixes almost exclusively — lost-connection detection, Postgres whereDate crashes, deprecation logging, schedule:list timezone handling. 13.x gets the additions: a monthly log driver, first-party image handling, modelKeys() on the query builder, an array_keys validation rule, and a steady stream of queue-fake testing improvements.
The split is doing exactly what a maintenance branch is supposed to do, which makes the framework's direction readable from 13.x alone. Two clusters dominate there: queue and job testing ergonomics (fakes that understand delays, reserved jobs, and immutable timestamps) and small ergonomic additions to Collection, Str and Storage. Route cache lookup work and worker memory reporting suggest performance attention on the runtime side.
Expect 13.x to keep accumulating small API additions between minor releases while 12.x stays fix-only, with the queue and testing surface the most likely place for the next batch given how consistently it shows up.
Gravity Forms shipped 3.0 in late July after a beta-then-RC run, and the release is built around two things: international phone number handling and accessibility settings that are switched on for every new form. Around that core release, the team keeps a steady add-on cadence going — Dropbox, Trello, Conversational Forms and Pipe all took point releases in the same window. The main plugin and its integration catalog move on separate clocks.
The 3.0 framing tells you where this is going: accessibility stops being an opt-in the form builder has to know to enable and becomes the baseline output. That is a compliance posture as much as a feature, and it targets the agencies and public-sector buyers who have to answer for WCAG conformance on every form they ship. Expect the add-on catalog to keep drip-releasing on its own schedule while the platform work concentrates on defaults, validation and input correctness.
Next moves are likely 3.0.x hardening — accessibility regressions surfaced by real-world forms, plus phone validation edge cases across locales — followed by add-ons updating for 3.0 compatibility rather than any new headline capability.
Other DevOps 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 Laravel or Gravity Forms.
Runtime bumps most weeks, but a new stack, a stack deprecation and an AI model cull underneath
HashiCorp is repositioning HCP Terraform as the accountability layer under AI agents that write infrastructure
Jenkins is shedding weight and hardening deserialization on its weekly train
Bitwarden's server releases are all plumbing right now — flags cleared, billing untangled, invites hardened.
PlanetScale is building out Postgres while making every control reachable without the dashboard.
Confluent Platform 8.2 gives Kafka native queueing, removing a standing reason to run a second broker.
See all Laravel alternatives → · See all Gravity Forms alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Gravity Forms is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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. Gravity Forms is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top Laravel alternatives in DevOps are ranked by recent ship velocity. Browse the "Laravel alternatives" section above for the current picks, or visit /alternatives/laravel for the full list with editorial commentary on each.
Top Gravity Forms alternatives in DevOps are ranked by recent ship velocity. Browse the "Gravity Forms alternatives" section above for the current picks, or visit /alternatives/gravity-forms for the full list with editorial commentary on each.