Bitbucket
Bitbucket is rebuilding Pipelines as a place where agents run, not just where builds run.
A side-by-side editorial comparison of Parse Server and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
Parse Server's alpha channel has become a steady stream of access-control security fixes.
Recent Parse Server releases are almost entirely security and permission fixes on the 9.10.x alpha line. Several close advisories where callers without read access could learn whether a field exists or receive data from internal classes, including a LiveQuery leak of installation objects. The newest alpha moves the Docker image from Node.js 20 to 24.
Skipper now serves zone-filtered routes only when its own ingress is balanced across zones.
Skipper, Zalando's HTTP router and Kubernetes ingress, tags a release for nearly every merge, so most entries are dependency bumps. The substantive ones this autumn are about zone-aware routing: v0.28.56 made routesrv recompress only zones whose routes changed, and v0.28.60 on November 2 serves zone-filtered routes only when skipper-ingress is balanced across zones, falling back to the global table otherwise.
Recent Parse Server releases are almost entirely security and permission fixes on the 9.10.x alpha line. Several close advisories where callers without read access could learn whether a field exists or receive data from internal classes, including a LiveQuery leak of installation objects. The newest alpha moves the Docker image from Node.js 20 to 24.
The project is working through a systematic audit of how read permissions are enforced across save, create, dot-notation and LiveQuery paths, shipping one fix per alpha. Small performance work, such as dropping an extra database read on save, appears alongside. Feature work is not visible in this window.
More permission-boundary advisories are likely in the next few alphas, followed by a stable 9.10.x release that bundles them. The entries don't indicate when the audit will end.
Skipper, Zalando's HTTP router and Kubernetes ingress, tags a release for nearly every merge, so most entries are dependency bumps. The substantive ones this autumn are about zone-aware routing: v0.28.56 made routesrv recompress only zones whose routes changed, and v0.28.60 on November 2 serves zone-filtered routes only when skipper-ingress is balanced across zones, falling back to the global table otherwise.
Zone-aware routing is being made safe for production, with guards against skew and fixes for a data race and silent misconfiguration. It currently works only in the routesrv mode, and the release notes say the direct Kubernetes mode needs the same filtering.
Expect zone filtering to be extended to the skipper-to-Kubernetes mode in a coming tag, as the v0.28.60 notes say is needed.
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 Parse Server or Skipper.
Bitbucket is rebuilding Pipelines as a place where agents run, not just where builds run.
GitLab is turning its platform into the context layer agents and security teams query, not just a code host.
Testomat.io is wiring its test management into AI chat clients and turning screenshots into test cases.
Tolgee ships near-daily patches, mostly fixes and security bumps around its branching feature.
Infisical is shipping weekly, with batched secret edits and an agent credential vault as the real threads.
AppSignal is turning distributed tracing into the default way to debug, one link at a time.
See all Parse Server alternatives → · See all Skipper alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Parse Server and Skipper 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. Parse Server and Skipper 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 Parse Server alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Parse Server alternatives" section above for the current picks, or visit /alternatives/parse-server for the full list with editorial commentary on each.
Top Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.