Cortex
Cortex 1.22 is on its fourth candidate, with sharded Parquet and years of deprecated flags removed.
A side-by-side editorial comparison of Dagster and OpenMetadata — release velocity, themes, recent moves, and the top alternatives to consider.
Dagster is untangling itself from dbt-core so dbt Fusion can run without a fight.
Dagster's six most recent 1.13 releases are dominated by two threads. dagster-dbt no longer installs dbt-core, and a new extra installs dbt v2, the Fusion engine, with clear errors if the two are combined. The UI gained a phone layout covering Home, Jobs, Automation, Timeline, the Asset Catalog and run details. Dagster+ also added capacity-based alert policies, and agents can now retry code locations that fail to start.
OpenMetadata reaches 2.1 rc1 after a month of repairing 2.0's connectors.
OpenMetadata has shipped a run of 2.0.x maintenance releases, each centered on connectors, lineage and search. 2.0.3 included a certificate-verification bypass fix and a SQL-injection fix, 2.0.5 restored metadata affected by 2.0 ingestion regressions, and 2.0.7 improved reliability for Pub/Sub, SQL Server and Unity Catalog. The 2.1.0-rc1 pre-release has now appeared, though its notes are a commit message about settings-modal styling rather than a feature list.
Dagster's six most recent 1.13 releases are dominated by two threads. dagster-dbt no longer installs dbt-core, and a new extra installs dbt v2, the Fusion engine, with clear errors if the two are combined. The UI gained a phone layout covering Home, Jobs, Automation, Timeline, the Asset Catalog and run details. Dagster+ also added capacity-based alert policies, and agents can now retry code locations that fail to start.
The dbt work is a dependency reset with real consequences, because Fusion and dbt-core claim the same import namespace and overwrite each other silently. Dagster made the safe path the default and accepted a breaking change to do it. The rest of the window is operational hardening: resuming run workers on ECS, cross-account service discovery and clearer failure reasons when a run worker dies.
Weekly-style 1.13 releases should keep extending Fusion coverage in dagster-dbt, since metadata fetching there still degrades to warnings. Declarative Automation for jobs does not appear in these entries, so its exit from preview remains unconfirmed.
OpenMetadata has shipped a run of 2.0.x maintenance releases, each centered on connectors, lineage and search. 2.0.3 included a certificate-verification bypass fix and a SQL-injection fix, 2.0.5 restored metadata affected by 2.0 ingestion regressions, and 2.0.7 improved reliability for Pub/Sub, SQL Server and Unity Catalog. The 2.1.0-rc1 pre-release has now appeared, though its notes are a commit message about settings-modal styling rather than a feature list.
The 2.0 launch is being paid for in connector repairs, and the cadence of roughly weekly maintenance suggests a large installed surface. Protecting user-managed metadata from bot ingestion, and multi-pod fixes in 2.0.6, point at production deployments rather than trials. The 2.1 candidate is the first sign of attention moving forward, but the published notes do not show its contents.
Expect a 2.1 release soon, with its real scope clearer once proper notes appear. 2.0.x maintenance should continue alongside it.
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 Dagster or OpenMetadata.
Cortex 1.22 is on its fourth candidate, with sharded Parquet and years of deprecated flags removed.
Countly's two LTS lines now get the same security fixes within a week of each other.
Stitch keeps patching connectors one replication bug at a time.
Datawrapper's October is touch tooltips, keyboard focus and small chart repairs.
Fluent Bit spends October bounding what its inputs will accept.
Axiom makes agent work checkable, and points alerts straight at coding agents
See all Dagster alternatives → · See all OpenMetadata alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dagster and OpenMetadata 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. Dagster and OpenMetadata 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 Dagster alternatives in Analytics are ranked by recent ship velocity. Browse the "Dagster alternatives" section above for the current picks, or visit /alternatives/dagster for the full list with editorial commentary on each.
Top OpenMetadata alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenMetadata alternatives" section above for the current picks, or visit /alternatives/openmetadata for the full list with editorial commentary on each.