OpenMetadata
OpenMetadata 2.0.8 widens Hex, Sigma and BigQuery coverage while 2.1 waits in release candidates.
A side-by-side editorial comparison of OpenCTI and OpenHouse — release velocity, themes, recent moves, and the top alternatives to consider.
OpenCTI lets analysts run enrichment connectors straight from the investigation graph.
OpenCTI 7.261106.0 added custom fields and templates to Cases and Incidents, and LTS lines received matching security backports the same week. 7.261109.0 adds a right-click option to run an enrichment connector from the investigation graph, prepares ingestion health reporting, exports and imports labels in config presets, and fixes a cache race that could stop a started playbook from running. 7.261109.3 is a bare backend release tag.
OpenHouse adds time-zone-aware retention and per-database table caps.
OpenHouse ships small versioned releases straight from merged pull requests. On November 13 it shipped five: retention policies on string date columns can now take a time zone, operators can cap live tables per database with metrics on usage and rejections, view requests and operations are now audited in full, and two fixes make view property SET/UNSET and REPLACE behave. Earlier in November failed Spark maintenance jobs began exiting as failed.
OpenCTI 7.261106.0 added custom fields and templates to Cases and Incidents, and LTS lines received matching security backports the same week. 7.261109.0 adds a right-click option to run an enrichment connector from the investigation graph, prepares ingestion health reporting, exports and imports labels in config presets, and fixes a cache race that could stop a started playbook from running. 7.261109.3 is a bare backend release tag.
Filigran keeps a near-weekly cadence that mixes small analyst workflow additions with platform reliability: playbook triggers, cache consistency, stream compatibility and ingestion health. Two LTS branches are maintained alongside the main line.
Expect ingestion health to surface as a visible feature in an upcoming release, given this one calls the work 'preparation', plus further LTS backports.
OpenHouse ships small versioned releases straight from merged pull requests. On November 13 it shipped five: retention policies on string date columns can now take a time zone, operators can cap live tables per database with metrics on usage and rejections, view requests and operations are now audited in full, and two fixes make view property SET/UNSET and REPLACE behave. Earlier in November failed Spark maintenance jobs began exiting as failed.
OpenHouse is adding the controls a shared lakehouse needs at scale: quotas, audit trails and retention that matches business calendars. Views are getting the same governance tables already had.
Expect more views milestones after audit (the release is labeled Views M1), and further operator controls for quotas and maintenance.
Other Analytics 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 OpenCTI or OpenHouse.
OpenMetadata 2.0.8 widens Hex, Sigma and BigQuery coverage while 2.1 waits in release candidates.
Dovetail lets admins choose which connectors members can plug into the workspace.
Dagster drops Python 3.10 and lets agents run schedules and sensors through MCP.
Countly 25.03.59 defaults to Node 26, supports MongoDB 9 and tightens app scoping.
Kubecost cuts three 3.3.2 release candidates in two days, still without notes.
RStudio opens the 2026.11 train with another NOTICE file update.
See all OpenCTI alternatives → · See all OpenHouse alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OpenCTI and OpenHouse 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. OpenCTI and OpenHouse 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 Analytics products to evaluate alongside.
Top OpenCTI alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenCTI alternatives" section above for the current picks, or visit /alternatives/opencti for the full list with editorial commentary on each.
Top OpenHouse alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenHouse alternatives" section above for the current picks, or visit /alternatives/openhouse for the full list with editorial commentary on each.