Tigris
An engineering blog making one argument: an agent's working state belongs in a forkable bucket
A side-by-side editorial comparison of Gravity Forms and Refine — release velocity, themes, recent moves, and the top alternatives to consider.
Gravity Forms ships 3.0: accessible markup by default across every form.
Gravity Forms just closed a full 3.0 release arc — beta 2 in early July, RC1 on the 20th, general availability on the 28th — carrying international phone format support and accessibility by default. Around the core plugin the add-on estate keeps moving on its own schedule: Pipe 1.5 adding video recording to forms, Gravity SMTP 2.3 with conditional email routing, a new first-party AbuseIPDB add-on, and a PayPal Checkout patch. The result is a platform release plus four satellite updates inside three weeks.
Refine's v5 majors are out; what's shipping now is the bug tail, mostly from contributors
Refine is a React framework for building internal tools and admin panels, and this window is entirely patch releases against the already-shipped v5 core and v8 MUI packages. The fixes cluster in three places: URL state parsing under syncWithLocation, access-control metadata not reaching button hooks, and CLI binary resolution inside monorepo workspaces.
Gravity Forms just closed a full 3.0 release arc — beta 2 in early July, RC1 on the 20th, general availability on the 28th — carrying international phone format support and accessibility by default. Around the core plugin the add-on estate keeps moving on its own schedule: Pipe 1.5 adding video recording to forms, Gravity SMTP 2.3 with conditional email routing, a new first-party AbuseIPDB add-on, and a PayPal Checkout patch. The result is a platform release plus four satellite updates inside three weeks.
The 3.0 headline is the tell: accessibility moves from something a site builder configures to something the plugin emits by default, which changes the baseline output of every form rather than adding an option. The add-on line is filling in the submission pipeline end to end — capture (video), defence (IP reputation), delivery (conditional SMTP routing), payment. Both tracks point at Gravity Forms competing on what works without configuration rather than on feature count.
Expect a 3.0.x patch series as the accessibility markup changes meet real themes, and continued add-on releases updated for 3.0 compatibility.
Refine is a React framework for building internal tools and admin panels, and this window is entirely patch releases against the already-shipped v5 core and v8 MUI packages. The fixes cluster in three places: URL state parsing under syncWithLocation, access-control metadata not reaching button hooks, and CLI binary resolution inside monorepo workspaces.
The pattern is a framework absorbing the edge cases that only appear once a major is in real projects. Deeply nested conditional filters were being mangled because a parser depth limit was too shallow; useDeleteButton was dropping the meta prop that custom access rules depend on; refine dev broke under workspace hoisting. Notably, most of these carry different contributor names, several first-time — the maintenance load is being spread across the community rather than driven by a single team push.
Filters, access control, and router adapters have each produced multiple fixes in a single window, so expect continued patch releases in those areas; nothing in these entries points to a new major or a change in framework direction.
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 Gravity Forms or Refine.
An engineering blog making one argument: an agent's working state belongs in a forkable bucket
Workato is packaging its agents into products — IT Support and EDI Genies launched a day apart
Lokalise is building the measurement layer around AI translation, not just more AI translation
Okta is documenting its way into agent identity, one Cross App Access guide at a time
HashiCorp is wrapping Terraform in policy and stacks for the agent-driven era.
GitHub is hardening the registry it owns while Copilot absorbs every new model.
See all Gravity Forms alternatives → · See all Refine 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 0.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 0.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 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.
Top Refine alternatives in DevOps are ranked by recent ship velocity. Browse the "Refine alternatives" section above for the current picks, or visit /alternatives/refine for the full list with editorial commentary on each.