Tigris
Tigris still ships features inside essays, and the newest one is a recycle bin.
A side-by-side editorial comparison of OceanBase and Puppet — release velocity, themes, recent moves, and the top alternatives to consider.
OceanBase is rebuilding itself as a RAG backend without giving up the HTAP story
OceanBase Community Edition runs at least five branches in parallel — 4.2.5, 4.3.5, 4.4.1, 4.4.2, 4.6.0 and now 5.0.1 — with feature releases on the newest lines and hotfix trains keeping older LTS branches alive. The centre of gravity in this window is V4.6.0, which added a native SQL hybrid-retrieval interface fusing vector, full-text and scalar predicates in one query and reworked the execution framework behind it. The hotfix branches show where that work is straining: 4.4.1 and 4.3.5 patches are dominated by vector-index bugs — HNSW memory blowups, IVF cache leaks, index rebuilds hanging, planner misjudgements that skip the vector index entirely.
Puppet Enterprise is shipping monthly point releases — but the changelog feed strips the substance.
Puppet Enterprise has dropped five PE 2025.x point releases over February and early March on a roughly weekly cadence. The captured content is page chrome (Features, Enhancements, Platform support headers) without the substance — the actual change details live behind navigation our scraper isn't following. So we can confirm cadence and version numbering, but not what shipped in each release.
OceanBase Community Edition runs at least five branches in parallel — 4.2.5, 4.3.5, 4.4.1, 4.4.2, 4.6.0 and now 5.0.1 — with feature releases on the newest lines and hotfix trains keeping older LTS branches alive. The centre of gravity in this window is V4.6.0, which added a native SQL hybrid-retrieval interface fusing vector, full-text and scalar predicates in one query and reworked the execution framework behind it. The hotfix branches show where that work is straining: 4.4.1 and 4.3.5 patches are dominated by vector-index bugs — HNSW memory blowups, IVF cache leaks, index rebuilds hanging, planner misjudgements that skip the vector index entirely.
Two threads run side by side and neither is being sacrificed. One is AI data infrastructure: hybrid search, sparse vectors, recall evaluation, Document AI and an explicitly named end-to-end RAG package, plus AI Functions that now handle images. The other is the HTAP and availability core: columnar replica routing with consistent reads, primary/standby strong sync at RPO=0 graduating from experimental to supported inside two releases, and V5.0.1 completing online conversion between row, columnar and hybrid storage formats. Note that publication dates on this feed do not match the stated release dates in the entries, so cadence read off timestamps alone will be misleading.
The volume of vector-index defect fixes across three hotfix branches suggests the next releases on the 5.0 line will spend more effort stabilising hybrid search than extending it, with the RAG packaging work more likely to be documented and productised than expanded.
Puppet Enterprise has dropped five PE 2025.x point releases over February and early March on a roughly weekly cadence. The captured content is page chrome (Features, Enhancements, Platform support headers) without the substance — the actual change details live behind navigation our scraper isn't following. So we can confirm cadence and version numbering, but not what shipped in each release.
Cadence-wise, the team is on a tight monthly point-release cycle, suggesting active investment in the platform after years of comparatively quiet drops. Without content, the direction is unreadable from this stream — needs the actual release notes to comment on whether this is bug-fix iteration, feature rollout, or platform-support work.
Until the changelog source is wired correctly, no specific prediction is possible. The cadence alone hints at a more visible 2026 roadmap than recent years, but evidence beyond version stamps is missing.
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 OceanBase or Puppet.
Tigris still ships features inside essays, and the newest one is a recycle bin.
Workato just made itself the control plane for every MCP server in the building.
Four branches on a servicing drumbeat, with 10.0 taking the only real fixes.
Laravel runs two trains in lockstep, and 13.x is still where features land.
Two trains ship the same features minutes apart while v16 absorbs the CRM stack.
Weaviate is turning the vector database into an agent runtime with tunable search effort
See all OceanBase alternatives → · See all Puppet alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OceanBase is currently shipping more aggressively (velocity 6.3 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. OceanBase is currently shipping more aggressively (velocity 6.3 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 DevOps products to evaluate alongside.
Top OceanBase alternatives in DevOps are ranked by recent ship velocity. Browse the "OceanBase alternatives" section above for the current picks, or visit /alternatives/oceanbase for the full list with editorial commentary on each.
Top Puppet alternatives in DevOps are ranked by recent ship velocity. Browse the "Puppet alternatives" section above for the current picks, or visit /alternatives/puppet for the full list with editorial commentary on each.