Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
Comparison · Analytics
OpenCTI vs OpenHouse
A side-by-side editorial comparison of OpenCTI and OpenHouse — release velocity, themes, recent moves, and the top alternatives to consider.
OpenCTI vs OpenHouse: at a glance
What is OpenCTI?
OpenCTI is rebuilding its connector layer into a marketplace and wiring the platform to XTM Hub
OpenCTI ships on a roughly weekly date-stamped cadence, and the last six releases divide cleanly: the connector catalog was redesigned into a faceted marketplace, then the surrounding integrations experience was reworked around it, then the platform gained two-way connection with Filigran's XTM Hub. Alongside that, saved searches and saved filters became shareable and reusable across dashboards. The most recent releases are weighted toward fixes rather than new surface.
What is OpenHouse?
LinkedIn's Iceberg control plane, shipping one pull request per release.
OpenHouse is LinkedIn's open-source control plane for Iceberg tables, and it releases per merged pull request — version numbers climb several times a week with a single change each. The current work is concentrated on making the service defensible in production: a fix for CREATE OR REPLACE AS SELECT silently wiping table policies, request-ID correlation and a typed exception hierarchy in the data loader, and targeted scheduler logging for jobs observability.
OpenCTI vs OpenHouse: editorial side-by-side
OpenCTI
6.3ANALYTICS
OpenCTI is rebuilding its connector layer into a marketplace and wiring the platform to XTM Hub
◆ Current state
OpenCTI ships on a roughly weekly date-stamped cadence, and the last six releases divide cleanly: the connector catalog was redesigned into a faceted marketplace, then the surrounding integrations experience was reworked around it, then the platform gained two-way connection with Filigran's XTM Hub. Alongside that, saved searches and saved filters became shareable and reusable across dashboards. The most recent releases are weighted toward fixes rather than new surface.
◆ Where it's heading
The centre of gravity is moving from OpenCTI as a self-contained platform to OpenCTI as a client of Filigran's wider ecosystem — connectors sourced from a catalog with support tiers, custom views deployed from XTM Hub, an MCP server exposed through XTM One. The workflow engine is maturing in parallel, picking up draft approval, transition restrictions and full reset. Telemetry coverage expanded significantly in the same period, which is what makes the catalog's adoption measurable.
◆ Prediction
Expect more of the platform's configuration surface — dashboards, playbooks, mappers — to become distributable through XTM Hub the way custom views and connectors already are. The workflow approval features suggest governance controls are the next area to fill in.
OpenHouse
5.0ANALYTICS
LinkedIn's Iceberg control plane, shipping one pull request per release.
◆ Current state
OpenHouse is LinkedIn's open-source control plane for Iceberg tables, and it releases per merged pull request — version numbers climb several times a week with a single change each. The current work is concentrated on making the service defensible in production: a fix for CREATE OR REPLACE AS SELECT silently wiping table policies, request-ID correlation and a typed exception hierarchy in the data loader, and targeted scheduler logging for jobs observability.
◆ Where it's heading
The theme across these releases is treating table metadata as something that must not be lost by accident, and making failures attributable. Policies now merge rather than being rebuilt from the request. Data loader errors carry a request ID and distinguish authentication from transport failure instead of retrying auth errors as transient. Feature toggles gained self-service table overrides so server-side ramps and table-owner opt-in can coexist.
◆ Prediction
The jobs-observability plan explicitly defers OTEL gauges, a heartbeat sampler, and DLQ counters to a later phase, so those are the concrete next steps visible in these entries.
Alternatives to OpenCTI and OpenHouse
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.
Omni
Omni ships weekly, and almost every week the headline item is an AI feature
OpenDataDiscovery
Four ODD Platform releases in two weeks, and not one of them changes the product
Apache Baremaps
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Deequ
Deequ ships GitHub tags whose release notes are one commit message long
Marquez
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
See all OpenCTI alternatives → · See all OpenHouse alternatives →
Recent activity from OpenCTI and OpenHouse
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 15h agoOpenCTIMass operations can now edit relation start and stop times
- 4d agoOpenCTISaved searches and dashboard filters become shareable and reusable
- 8d agoOpenHouseCREATE OR REPLACE AS SELECT no longer silently drops table policies
- 8d agoOpenCTIData sanity operations can be stopped mid-run
- 9d agoOpenHouseAutomated iceberg-core dependency bump
- 9d agoOpenHouseScheduler log lines for jobs observability, phase 1.5
- 11d agoOpenHouseRequest-ID correlation and typed catalog exceptions in the data loader
- 11d agoOpenHouseSelf-service table overrides for feature toggles
- 12d agoOpenHouseRenovate added to track two parallel Iceberg version lines
- 13d agoOpenCTIIntegrations experience reworked around the new catalog, plus draft approval workflows
- 20d agoOpenCTIConnector catalog is rebuilt as a faceted marketplace ⚡
- 25d agoOpenCTIFix-only release across live streams, groups and dashboard widgets
Frequently asked questions
What is the difference between OpenCTI and OpenHouse?
They serve adjacent needs but don't currently overlap on shipped themes. OpenCTI is currently shipping more aggressively (velocity 6.3 vs 5.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.
Is OpenCTI better than OpenHouse?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. OpenCTI is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to OpenCTI?
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.
What are the best alternatives to OpenHouse?
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.