Fulcrum
Fulcrum ships MCP server and AI Toolkit to let AI assistants build and query field data forms
A side-by-side editorial comparison of OpenHouse and ThingsBoard — release velocity, themes, recent moves, and the top alternatives to consider.
OpenHouse breaks ground on Iceberg views while tightening storage lifecycle and authorization
OpenHouse (LinkedIn's managed Iceberg tables service) is shipping at a rapid v0.5.x pace with multiple improvements per week. Recent work spans three areas: storage lifecycle management (native snapshot expiration with reference age defaults, orphan file reclamation), authorization hardening (routing RTAS operations through proper table privilege checks), and the first scaffolding for Iceberg view support (entityType discriminator, table-scoped HTS queries).
ThingsBoard patches aggressively across two release lines while quietly adding IoT Hub and AI model support.
ThingsBoard is in sustained patch mode across 4.2.x (LTS) and 4.3.x (current), resolving dozens of CVEs per release cycle. Beneath the security churn, the 4.3.x line has accumulated real additions since spring: IoT Hub integration, AI model structured output support for multiple providers, LZ4 Kafka compression, automatic SSL cert reload without restarts, and an HTML container widget. The dual-track model shows an enterprise customer base that demands long-term stability alongside continuous development.
OpenHouse (LinkedIn's managed Iceberg tables service) is shipping at a rapid v0.5.x pace with multiple improvements per week. Recent work spans three areas: storage lifecycle management (native snapshot expiration with reference age defaults, orphan file reclamation), authorization hardening (routing RTAS operations through proper table privilege checks), and the first scaffolding for Iceberg view support (entityType discriminator, table-scoped HTS queries).
The entityType discriminator in v0.5.490 is the most directional move in this window — it creates the data model prerequisite for treating views as first-class entities alongside tables, something OpenHouse has not supported. Storage lifecycle work is converging on Iceberg-native mechanisms, reducing custom expiration logic. The post-commit operations framework in v0.5.492 is infrastructure that will allow OpenHouse to add downstream hooks (compaction triggers, notifications) without catalog coupling.
Iceberg view read support will arrive in the next several releases, building on the discriminator and HTS scaffolding now in place. The authorization model for views will be an open question — watch whether they reuse the table ACL path or introduce a parallel model.
ThingsBoard is in sustained patch mode across 4.2.x (LTS) and 4.3.x (current), resolving dozens of CVEs per release cycle. Beneath the security churn, the 4.3.x line has accumulated real additions since spring: IoT Hub integration, AI model structured output support for multiple providers, LZ4 Kafka compression, automatic SSL cert reload without restarts, and an HTML container widget. The dual-track model shows an enterprise customer base that demands long-term stability alongside continuous development.
The parallel LTS and current release trains signal a maturing platform with paying enterprise customers who cannot absorb breaking changes. The AI model integration thread — structured outputs, Vertex AI location routing — suggests ThingsBoard is building a rule-engine layer that can route telemetry decisions through LLMs, not just static rules. This points toward an edge-to-AI data fabric positioning rather than dashboarding alone.
The next substantive release will likely deepen the AI rule-engine integration with more providers or an agent-style action node. The IoT Hub connector introduced in 4.3.1.3 will likely be backported to 4.2.x once stabilized. Security patch cadence will continue regardless.
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 OpenHouse or ThingsBoard.
Fulcrum ships MCP server and AI Toolkit to let AI assistants build and query field data forms
Holistics builds AI governance and docs-as-analytics in parallel, shipping both weekly
dbt 2.0 enters final RC with beta Snowflake interactive_table materialization and full ClickHouse MV support.
Lightdash is cutting its dbt dependency and building AI-powered authoring into every layer of its BI stack.
Keboola's Kai AI assistant hits GA, completing the pivot from data platform to AI-native pipeline orchestration layer.
Omni's Apps reach general availability, completing its embedded analytics platform pitch.
See all OpenHouse alternatives → · See all ThingsBoard alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OpenHouse 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. OpenHouse 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.
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.
Top ThingsBoard alternatives in Analytics are ranked by recent ship velocity. Browse the "ThingsBoard alternatives" section above for the current picks, or visit /alternatives/thingsboard for the full list with editorial commentary on each.