Apache Druid
Druid 38 drops Java 17, recommends Java 25 and took longer to arrive than its predecessors
A side-by-side editorial comparison of Retool and runc — release velocity, themes, recent moves, and the top alternatives to consider.
Retool's app builder hits GA, generating React apps, with spend controls beside it.
Retool's app builder is generally available: it builds React apps from natural language, from MCP-compatible coding agents or from imported React code. On the same day Retool shipped limits on AI credit and token usage by user, group and model, along with credit packs by card on all paid plans. Private npm registries for Enterprise apps and GPT 6.1 Terra followed, while self-hosted stable channels took three more 4.34 updates.
runc 1.6.0-rc.1 lifts the 1024-CPU limit and refuses settings it used to quietly ignore
The 1.6.0 cycle opened on October 6 with a first release candidate that is mostly cleanup: deprecated libcontainer APIs removed, Go 1.26 now required, urfave/cli moved from v1 to v3, and the binary about 15% smaller on amd64. The changes with operational weight are that cpuAffinity and NUMA memoryPolicy no longer stop at 1024 CPUs or nodes, and that a container asking for a read-only rootfs without its own mount namespace is now refused. Eleven days earlier 1.5.2 worked around a kernel bug, present since v6.17, that corrupted memory inside runc and caused random crashes on cgroup v2. It also stopped runc exec --cgroup from escaping into a sibling cgroup.
Retool's app builder is generally available: it builds React apps from natural language, from MCP-compatible coding agents or from imported React code. On the same day Retool shipped limits on AI credit and token usage by user, group and model, along with credit packs by card on all paid plans. Private npm registries for Enterprise apps and GPT 6.1 Terra followed, while self-hosted stable channels took three more 4.34 updates.
Retool is turning AI app generation into a metered product line: the builder is the surface, and credits and spend limits are how it gets sold and governed. Private npm registries point the same way, since generated React apps need a company's own packages. Self-hosted customers stay on a separate steady cadence of Edge builds and stable patches.
Expect more Enterprise controls around app builder output and the next frontier model added soon after launch. The entries don't show how AI credits are priced.
The 1.6.0 cycle opened on October 6 with a first release candidate that is mostly cleanup: deprecated libcontainer APIs removed, Go 1.26 now required, urfave/cli moved from v1 to v3, and the binary about 15% smaller on amd64. The changes with operational weight are that cpuAffinity and NUMA memoryPolicy no longer stop at 1024 CPUs or nodes, and that a container asking for a read-only rootfs without its own mount namespace is now refused. Eleven days earlier 1.5.2 worked around a kernel bug, present since v6.17, that corrupted memory inside runc and caused random crashes on cgroup v2. It also stopped runc exec --cgroup from escaping into a sibling cgroup.
The project keeps converting silent behaviour into explicit behaviour. Read-only requests that were ignored now fail, a umask that was dropped is now honoured, and poststart hooks moved to conform to the runtime spec. The same maintainers are shrinking the surface underneath, dropping the deprecated API and the high-level cilium/ebpf path, which took roughly 7.5% off the 1.5.2 binary. Stricter behaviour plus a smaller dependency set is what a component under every container host would be expected to do between majors.
1.5.0's notes pointed to a 1.6.0 in late October 2026, and the feed so far shows only rc.1, so further release candidates or the final are the next entries to expect. The refused read-only configurations are the change most likely to surface as user reports during testing.
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 Retool or runc.
Druid 38 drops Java 17, recommends Java 25 and took longer to arrive than its predecessors
Okta adds TypeScript to its Cross App Access guides and dates the end of Classic Engine features
Harness Open Source last shipped in August 2025, on this feed at least
Payload's v4 beta ships every few days, and most of the risk sits in the breaking-change notes
Scalar is testing demand for hosting from inside localhost
Incus 7.6 fixes 18 security issues, eight critical, and adds SR-IOV NIC live migration
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 6.3 vs 2.5), with 0 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 6.3 vs 2.5), with 0 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 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.
Top runc alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "runc alternatives" section above for the current picks, or visit /alternatives/runc for the full list with editorial commentary on each.