GravityKit
GravityKit folds every GravityView extension into one Pro plugin.
A side-by-side editorial comparison of Payload CMS and StatusPal — release velocity, themes, recent moves, and the top alternatives to consider.
Payload's v4 beta.9 keeps every past image crop and raises the Node floor again.
Payload has tagged nine v4 betas since October 10. Beta.9 reads saved crops and focal points from the new _transforms store, serves historical upload variants when a version is restored, adds labels and device details to sessions, and exports standalone CSS tokens from the UI package. It also bumps the minimum Node version to 24.22.3, the second Node floor raise in the cycle.
StatusPal Next makes notices read the same across email, Slack and Teams.
StatusPal runs two tracks: Next gets the structural work and Classic gets reliability fixes. On 10 November Next made notice notifications consistent across email, Slack, Microsoft Teams and Google Chat, added About text, search-engine visibility, incident history limits and Reply-To addresses for status pages, and tied planned maintenance times to the page's timezone. Earlier in November Classic's Monitoring V2 began opening and closing incidents automatically, and Next added Critical incident templates.
Payload has tagged nine v4 betas since October 10. Beta.9 reads saved crops and focal points from the new _transforms store, serves historical upload variants when a version is restored, adds labels and device details to sessions, and exports standalone CSS tokens from the UI package. It also bumps the minimum Node version to 24.22.3, the second Node floor raise in the cycle.
Three betas in a row have reworked file uploads around one stored original plus replayable transforms, and two have tightened sign-in and sessions. The v4 cycle is now finishing those two systems rather than adding new surfaces, which is the usual shape of a beta nearing a release candidate.
Expect more betas that close out the transforms and session work, with a release candidate once the fix lists shrink; the entries do not show a date.
StatusPal runs two tracks: Next gets the structural work and Classic gets reliability fixes. On 10 November Next made notice notifications consistent across email, Slack, Microsoft Teams and Google Chat, added About text, search-engine visibility, incident history limits and Reply-To addresses for status pages, and tied planned maintenance times to the page's timezone. Earlier in November Classic's Monitoring V2 began opening and closing incidents automatically, and Next added Critical incident templates.
Next is collecting the page settings and notification behaviour that larger Classic customers rely on, which points to an eventual move off Classic. Recent releases favour consistency and control over new surfaces: matching labels across channels, timezone-safe maintenance and configurable page details.
Expect more Next releases covering Classic features such as monitoring-driven incidents, and continued Classic fixes around migrations.
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 Payload CMS or StatusPal.
GravityKit folds every GravityView extension into one Pro plugin.
Nautobot 3.3 alpha 2 adds test helpers and a cable location filter after 3.2.9's token-leak fix.
Clair 4.10 RC can read SBOMs to match Java vulnerabilities.
Shuffle tags builds almost daily, but the notes are empty.
KrakenD's community edition is shipping only dependency bumps.
Velociraptor's recent releases are mostly about patching CVEs.
See all Payload CMS alternatives → · See all StatusPal alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Payload CMS and StatusPal 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. Payload CMS and StatusPal 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 Payload CMS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Payload CMS alternatives" section above for the current picks, or visit /alternatives/payload for the full list with editorial commentary on each.
Top StatusPal alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "StatusPal alternatives" section above for the current picks, or visit /alternatives/statuspal for the full list with editorial commentary on each.