OpenObserve
OpenObserve ships v1.0.0 GA after a five-RC stabilization run, making its enterprise observability play official.
A side-by-side editorial comparison of Count and dbt Core — release velocity, themes, recent moves, and the top alternatives to consider.
Count is turning its BI canvas into a governed, agent-operated analytics platform.
Count is a data-canvas analytics tool reorganizing itself around an AI agent. In two months it shipped a full public REST API and hosted MCP server (governed agent access via OAuth and service accounts), a major agent upgrade that lets the agent read and edit the entire canvas and answer from Slack, and the ability to plug external MCP servers (Linear, HubSpot, Stripe, Slack, Drive) into the agent. Around the agent it keeps broadening warehouse support—ClickHouse, Snowflake semantic models, OSI—alongside chart and UX polish.
dbt 2.0 ships stable with an official OSS/proprietary split and agentic skill loading
dbt shipped its 2.0 stable release on September 16, the first generational version milestone in the project's history. The release formally renames the CLI: what was 'Fusion/dbt-core' becomes 'dbt' (proprietary) and 'dbt-oss' (open source)—a structural separation that existed in practice but now has an official name. New capabilities include native Databricks metric view materializations, a ClickHouse ADBC driver, and AgentSkill installation from dbt packages gated on a new ai_provider flag.
Count is a data-canvas analytics tool reorganizing itself around an AI agent. In two months it shipped a full public REST API and hosted MCP server (governed agent access via OAuth and service accounts), a major agent upgrade that lets the agent read and edit the entire canvas and answer from Slack, and the ability to plug external MCP servers (Linear, HubSpot, Stripe, Slack, Drive) into the agent. Around the agent it keeps broadening warehouse support—ClickHouse, Snowflake semantic models, OSI—alongside chart and UX polish.
Count is building toward analytics where agents are first-class operators: a governed API/MCP layer for access, an agent that drives the canvas end to end, external tool reach via MCP, and connection-level context so guidance is captured once and inherited. Governance—permissions, scopes, service accounts—is the enabling layer that makes agent access acceptable in real data stacks rather than a bolt-on.
Expect more connection- and warehouse-level context controls, a widening catalog of supported external MCP integrations, and deeper Slack-native agent workflows.
dbt shipped its 2.0 stable release on September 16, the first generational version milestone in the project's history. The release formally renames the CLI: what was 'Fusion/dbt-core' becomes 'dbt' (proprietary) and 'dbt-oss' (open source)—a structural separation that existed in practice but now has an official name. New capabilities include native Databricks metric view materializations, a ClickHouse ADBC driver, and AgentSkill installation from dbt packages gated on a new ai_provider flag.
The OSS/proprietary split is the architectural move that matters most. dbt Labs is building a commercial product on top of dbt-oss, and 2.0 makes that boundary explicit to the ecosystem. The AgentSkills integration signals that dbt sees AI-assisted data transformation as a core product direction—not an add-on. The ai_provider flag is the gating mechanism through which commercial features will increasingly be differentiated.
Expect near-term differentiation between dbt (proprietary) and dbt-oss at the feature level, with AI-native capabilities—AgentSkills, model suggestions, lineage intelligence—landing exclusively in the commercial tier first.
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 Count or dbt Core.
OpenObserve ships v1.0.0 GA after a five-RC stabilization run, making its enterprise observability play official.
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
OpenHouse breaks ground on Iceberg views while tightening storage lifecycle and authorization
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.
See all Count alternatives → · See all dbt Core alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dbt Core is currently shipping more aggressively (velocity 7.5 vs 6.3), 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. dbt Core is currently shipping more aggressively (velocity 7.5 vs 6.3), 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 Count alternatives in Analytics are ranked by recent ship velocity. Browse the "Count alternatives" section above for the current picks, or visit /alternatives/count for the full list with editorial commentary on each.
Top dbt Core alternatives in Analytics are ranked by recent ship velocity. Browse the "dbt Core alternatives" section above for the current picks, or visit /alternatives/dbt-core for the full list with editorial commentary on each.