WeWeb
WeWeb is adding AI model integrations and pre-rendering — expanding from no-code builder to AI-native app platform.
A side-by-side editorial comparison of Exoscale and immudb — release velocity, themes, recent moves, and the top alternatives to consider.
Exoscale keeps SKS on the upstream release train while the platform play sits elsewhere
Exoscale's changelog interleaves three streams: managed Kubernetes tracking upstream, a marketplace and partner directory that grows most weeks, and the occasional new managed service. Kubernetes 1.37 is now selectable on SKS for new and existing clusters, with Metrics API, Pod Certificates and ClusterTrustBundles, and Node Declared Features all arriving Stable from upstream. Upgrades stay a customer decision — existing clusters are not moved automatically, and minor versions must be stepped through in sequence.
immudb 1.11.0 added PostgreSQL compatibility — tamper-evident storage now accessible to ORM-based stacks.
immudb is in a 1.11.x maintenance cycle after the substantial 1.11.0 release, which added PostgreSQL ORM compatibility (pg_catalog, information_schema), structured audit logging with tamper-proof JSON events, and a new --audit-verif flag. The 1.11.2 maintenance release fixes a transaction survival issue when a statement fails before execution — a correctness fix for edge cases in transaction handling. The v2.0.0-RC1 from early 2025 introduced a different architecture (new indexing layer, simplified API), but 1.11.x appears to be the active production track.
Exoscale's changelog interleaves three streams: managed Kubernetes tracking upstream, a marketplace and partner directory that grows most weeks, and the occasional new managed service. Kubernetes 1.37 is now selectable on SKS for new and existing clusters, with Metrics API, Pod Certificates and ClusterTrustBundles, and Node Declared Features all arriving Stable from upstream. Upgrades stay a customer decision — existing clusters are not moved automatically, and minor versions must be stepped through in sequence.
The SKS entries read as a European provider keeping pace rather than differentiating: version availability, container registry mirroring for Karpenter nodes, CPU Manager policies. Where Exoscale is actually moving is in what runs beside the clusters — Managed ClickHouse in August put an analytics engine on the same estate as the object storage — while the partner and marketplace posts fill the cadence between. Expect the Kubernetes entries to keep reporting upstream rather than making an argument of their own.
The next SKS entries are likely to be operational — node pool and upgrade tooling around 1.37 — with any directional move coming from another managed service rather than from the Kubernetes track.
immudb is in a 1.11.x maintenance cycle after the substantial 1.11.0 release, which added PostgreSQL ORM compatibility (pg_catalog, information_schema), structured audit logging with tamper-proof JSON events, and a new --audit-verif flag. The 1.11.2 maintenance release fixes a transaction survival issue when a statement fails before execution — a correctness fix for edge cases in transaction handling. The v2.0.0-RC1 from early 2025 introduced a different architecture (new indexing layer, simplified API), but 1.11.x appears to be the active production track.
The PostgreSQL compatibility push is the clearest directional signal: immudb is trying to become accessible to developers using standard ORMs without learning immudb's native API. Combined with the structured audit logging, the pitch is a tamper-evident backend that behaves like PostgreSQL for existing toolchains. The v2.0.0 architecture rework remains an open question — whether it reaches GA or gets merged back into the 1.x line is unclear from the releases shown.
A stable v2.0.0 release or clear abandonment of the v2 branch in favor of continued 1.x enhancements is the next decision point. The PostgreSQL compatibility work will likely expand to cover more pg_catalog views needed by common ORMs.
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 Exoscale or immudb.
WeWeb is adding AI model integrations and pre-rendering — expanding from no-code builder to AI-native app platform.
CodeRabbit is building the API layer that lets enterprises manage AI code review at scale.
Gravity Forms shipped an MCP server — WordPress forms are now queryable by AI coding assistants.
Manticore Search in active patch mode — German morphology improvements and distributed query crash fixes.
Rollbar's Resolve agent reads your codebase and opens a fix PR automatically — error tracker becomes error fixer.
Workato Genies now run 30-minute tasks and deploy anywhere via Headless API — enterprise autonomous agents at scale.
See all Exoscale alternatives → · See all immudb alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Exoscale is currently shipping more aggressively (velocity 6.3 vs 2.5), 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. Exoscale is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 Exoscale alternatives in DevOps are ranked by recent ship velocity. Browse the "Exoscale alternatives" section above for the current picks, or visit /alternatives/exoscale for the full list with editorial commentary on each.
Top immudb alternatives in DevOps are ranked by recent ship velocity. Browse the "immudb alternatives" section above for the current picks, or visit /alternatives/immudb for the full list with editorial commentary on each.