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 Tinybird — 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).
Tinybird makes JSON native by default and sets September 15 as Classic sunset for free plans
Tinybird is executing a deliberate migration from Classic to Forward, its newer platform architecture. September 15 marks the Classic sunset for Free and Developer plans — a real deadline. On the Forward side, the JSON data type is now enabled by default for all workspaces with no opt-in required, the Forward CLI gained job retry support, and the platform added persistent quarantine data and workspace usage trends. Deployment performance improved: changing a joined table in a Materialized View no longer triggers a full downstream rebuild.
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.
Tinybird is executing a deliberate migration from Classic to Forward, its newer platform architecture. September 15 marks the Classic sunset for Free and Developer plans — a real deadline. On the Forward side, the JSON data type is now enabled by default for all workspaces with no opt-in required, the Forward CLI gained job retry support, and the platform added persistent quarantine data and workspace usage trends. Deployment performance improved: changing a joined table in a Materialized View no longer triggers a full downstream rebuild.
The Classic→Forward migration is the overriding strategic thread. Every release either adds Forward capabilities or removes Classic parity gaps. The Forward CLI is maturing into the primary developer interface: job retries, live deployment progress tracking, conditional TTLs, and updated agent skills all landed in recent weeks. Separately, Query API timeout tiering by paid plan and TypeScript SDK improvements point toward a product API push — making Tinybird more accessible to front-end developers embedding analytics directly into products.
The September 15 Classic sunset for free/developer plans will likely trigger a follow-on announcement targeting the Enterprise tier migration. Beyond that, the TypeScript SDK and Query API timeout work suggest Tinybird is positioning for a developer-first API product push, possibly with a richer client SDK story.
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 Tinybird.
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 Tinybird alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OpenHouse and Tinybird are shipping at a similar cadence (velocity 6.3 vs 6.3, 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. OpenHouse and Tinybird are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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 Tinybird alternatives in Analytics are ranked by recent ship velocity. Browse the "Tinybird alternatives" section above for the current picks, or visit /alternatives/tinybird for the full list with editorial commentary on each.