Skipper
Skipper fixes two silent data-loss bugs — body truncation on large requests and multi-value header drops.
A side-by-side editorial comparison of Fission and Retool — release velocity, themes, recent moves, and the top alternatives to consider.
Fission's release feed carries only RC tags, and none of them say what shipped
Every entry here is a release candidate — v1.22.0-rc1 and rc2, v1.23.0-rc1, v1.25.0-rc1 — with no final release appearing between them, and the version sequence skips 1.24 entirely. The bodies are whatever the tagging commit said, so what reaches this feed is a dependabot bump, a CLI tool-version refresh, a codegen sync explicitly labelled as having no functional change, and one entry that is nothing but links to an external release-highlights page. The actual release notes live on the project's documentation site, not here.
Retool ships a CLI, opening code-first app development and CI/CD pipelines
Retool has been expanding on two fronts: AI integration and developer tooling. The CLI launch lands alongside a regular cadence of self-hosted updates and model additions, signaling that Retool is building infrastructure for enterprise teams that want both AI-assisted app development and code-controlled deployment workflows. The self-hosted track (4.34 stable, 4.58 Edge) maintains a separate release cadence for on-premise customers.
Every entry here is a release candidate — v1.22.0-rc1 and rc2, v1.23.0-rc1, v1.25.0-rc1 — with no final release appearing between them, and the version sequence skips 1.24 entirely. The bodies are whatever the tagging commit said, so what reaches this feed is a dependabot bump, a CLI tool-version refresh, a codegen sync explicitly labelled as having no functional change, and one entry that is nothing but links to an external release-highlights page. The actual release notes live on the project's documentation site, not here.
What can be read from these tags is infrastructure maintenance rather than product direction: Go dependency updates, helm and kind and skaffold and cosign version refreshes, and regenerated swagger and applyconfiguration files kept in sync with CEL and webhook validation comments in the core API types. That last one is the only entry hinting at anything structural — CEL-based validation on the API types implies declarative validation moving into the CRDs — but the commit itself changes only generated output.
This feed does not carry enough to predict product direction; until final releases or their notes appear here rather than only candidate tags, any read of where Fission is heading would be guesswork.
Retool has been expanding on two fronts: AI integration and developer tooling. The CLI launch lands alongside a regular cadence of self-hosted updates and model additions, signaling that Retool is building infrastructure for enterprise teams that want both AI-assisted app development and code-controlled deployment workflows. The self-hosted track (4.34 stable, 4.58 Edge) maintains a separate release cadence for on-premise customers.
The CLI is the clearest directional signal: Retool is moving away from a browser-bound, GUI-first builder toward a tool developers can embed in existing code workflows. Iframe embedding expands where Retool apps can live; frontier model additions keep AI features current. Together these moves position Retool to compete in engineering-led organizations that previously ruled it out on tooling grounds.
Deeper git and CI/CD integration examples are likely to follow the CLI — a CLI release is usually the first piece of a code-as-infrastructure story. AI model additions will continue on the visible 2–3 week cadence, tracking the frontier model release cycle.
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 Fission or Retool.
Skipper fixes two silent data-loss bugs — body truncation on large requests and multi-value header drops.
ToolJet ships Custom Component Library and tightens enterprise controls on path to AI-native low-code.
GitHub turns Copilot into an org-wide default, adds memory to agentic security fixes.
werf's v3 dev track ships multi-namespace cleanup scanning and JSON config schemas in rapid succession
Buildkite ships a caching product with cache-poisoning controls baked in as it builds toward AI-agent-operated CI.
Jackett ships daily tracker maintenance — domain fixes, new indexers, no architectural movement.
See all Fission alternatives → · See all Retool alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Retool is currently shipping more aggressively (velocity 7.5 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. Retool is currently shipping more aggressively (velocity 7.5 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 Infra & APIs products to evaluate alongside.
Top Fission alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Fission alternatives" section above for the current picks, or visit /alternatives/fission for the full list with editorial commentary on each.
Top Retool alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Retool alternatives" section above for the current picks, or visit /alternatives/retool for the full list with editorial commentary on each.