Meta Box
WordPress's custom-field layer is opening itself to agents and to native blocks.
A side-by-side editorial comparison of Gravity Forms and Linkerd — release velocity, themes, recent moves, and the top alternatives to consider.
Gravity Forms 3.0 bets on accessibility defaults and phone formats while the market chases AI.
Gravity Forms 3.0 shipped on 28 July after a tight beta-then-RC cycle, turning accessibility settings on by default for every new form and adding international phone formatting and validation. Around the core plugin, the add-on layer carries most of the shipping volume — Pipe 1.5 for video recording, an official AbuseIPDB add-on for screening submissions, PayPal Checkout updates, and a Choice Routing step in Gravity Flow. Notably absent across the entire window: any AI or assistant feature.
Linkerd keeps trading features for fewer operational surprises — 2.20 is tuning, not expansion.
The feed mixes release announcements with long-form engineering posts, many contributed by ambassadors and users rather than the core team. Linkerd 2.20 in June brought rate-limit-aware load balancing, lower memory use, and better inbound metrics; 2.19 before it replaced the TLS stack with post-quantum key exchange by default. The surrounding posts — native sidecar shutdown behaviour, protocol detection internals, certificate rotation, OpenTelemetry export — read as operational documentation for people already running the mesh in production.
Gravity Forms 3.0 shipped on 28 July after a tight beta-then-RC cycle, turning accessibility settings on by default for every new form and adding international phone formatting and validation. Around the core plugin, the add-on layer carries most of the shipping volume — Pipe 1.5 for video recording, an official AbuseIPDB add-on for screening submissions, PayPal Checkout updates, and a Choice Routing step in Gravity Flow. Notably absent across the entire window: any AI or assistant feature.
The core plugin is being hardened rather than expanded. The 3.0 arc ran beta to RC to GA on a fixed, narrow feature set, and post-launch the team is publishing per-feature explainers instead of moving on to the next thing. New capability is being pushed out to the add-on ecosystem, where each release lands one specific integration or workflow step. Gravity Forms is competing on compliance, internationalization, and ecosystem breadth at a moment when most WordPress tooling is competing on AI.
With 3.0 out, the near-term releases should be add-on updates bringing existing integrations onto the new accessibility baseline, plus point fixes as default-on settings meet real-world themes. Nothing in these entries suggests AI or agent features are queued.
The feed mixes release announcements with long-form engineering posts, many contributed by ambassadors and users rather than the core team. Linkerd 2.20 in June brought rate-limit-aware load balancing, lower memory use, and better inbound metrics; 2.19 before it replaced the TLS stack with post-quantum key exchange by default. The surrounding posts — native sidecar shutdown behaviour, protocol detection internals, certificate rotation, OpenTelemetry export — read as operational documentation for people already running the mesh in production.
The project is optimising for boring reliability at scale rather than adding surface, consistent with Buoyant's stated goal of a mesh that lasts and its focus on operational simplicity. Recent releases target the failure modes operators actually hit: proxies dying before the app during shutdown, memory footprint per pod, load balancing that respects downstream rate limits. Federation and multi-cluster work is the one direction that could widen scope, and it currently shows up as writing rather than shipped features.
Expect the next release to continue on data-plane efficiency and multi-cluster reliability; on the evidence here, cluster federation is the most likely candidate to move from blog post to product.
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 Linkerd.
WordPress's custom-field layer is opening itself to agents and to native blocks.
PlanetScale is giving Postgres users budgets, guardrails, and a read-only door for agents.
Vercel is building the durable-execution layer — and just learned its model catalog isn't its own.
Supabase is closing its most-exploited default: tables stop being public unless you say so.
Auth0 is rebuilding itself as the identity layer between B2B apps, their customers, and AI agents.
Sanity is spending this month on the surfaces around the editor, not the editor itself.
See all Gravity Forms alternatives → · See all Linkerd 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 Linkerd alternatives in DevOps are ranked by recent ship velocity. Browse the "Linkerd alternatives" section above for the current picks, or visit /alternatives/linkerd for the full list with editorial commentary on each.