Mage
Feature releases every two months in 2024; one bugfix release in the last twelve.
A side-by-side editorial comparison of MotherDuck and Polars — release velocity, themes, recent moves, and the top alternatives to consider.
DuckDB in the cloud is turning into an agent's workspace, not just a query engine.
MotherDuck runs DuckDB as a managed service with hybrid local/cloud execution, and its release notes read as weekly batches rather than headline launches. The past two months added the pieces an analytics platform needs to be bought rather than tried: RBAC, SCIM, regional coverage in Dublin, Sydney, and Tokyo, and a Postgres wire endpoint that lets Looker, dbt Cloud, DBeaver, and DataGrip connect without a custom driver. Alongside that, Dives (shareable data apps) went GA and Flights (Python data pipelines) went from Preview to available on every plan.
The streaming engine is stable and the API is being narrowed — Polars is clearing ground for a breaking release
Polars publishes two trains into one feed: Python releases roughly weekly through 1.42.0 to 1.43.2, and Rust releases on their own numbering, with 0.54.4 carrying the milestone that the streaming engine is stabilized. The dominant thread across the Python releases is deprecation — casts from string to temporal types, numeric-to-categorical and categorical-to-integer casts, casts from non-nested dtypes into lists, bitwise ops between integers and booleans, cat.get_categories(), cat.to_local(), LazyFrame.profile(), and to_struct() calls without field names. Alongside it, cloud IO keeps getting attention: bytes-based concurrency control, callback sinks on cloud, and non-blocking path expansion.
MotherDuck runs DuckDB as a managed service with hybrid local/cloud execution, and its release notes read as weekly batches rather than headline launches. The past two months added the pieces an analytics platform needs to be bought rather than tried: RBAC, SCIM, regional coverage in Dublin, Sydney, and Tokyo, and a Postgres wire endpoint that lets Looker, dbt Cloud, DBeaver, and DataGrip connect without a custom driver. Alongside that, Dives (shareable data apps) went GA and Flights (Python data pipelines) went from Preview to available on every plan.
The clearer arc is that every new surface is built to be driven by an agent as well as a human. Flights are creatable via SQL, UI, or any MCP client; Dives carry statuses that the MCP tools filter on; MCP responses moved to a token-efficient encoding; and the newest release adds Guides, where an organization's metric definitions and join rules live in MotherDuck and get read automatically by agents through MCP. In parallel, the storage story keeps opening outward — Databricks-managed Iceberg writes, Cloudflare R2 as a persisted Iceberg catalog, server-side attach of external Iceberg REST catalogs — so MotherDuck queries data it does not own.
Guides is the piece to watch: expect it to leave Preview with governance attached — versioning, ownership, and the ability to require a guide before an agent writes SQL — since a shared definition layer is only trustworthy if someone controls it.
Polars publishes two trains into one feed: Python releases roughly weekly through 1.42.0 to 1.43.2, and Rust releases on their own numbering, with 0.54.4 carrying the milestone that the streaming engine is stabilized. The dominant thread across the Python releases is deprecation — casts from string to temporal types, numeric-to-categorical and categorical-to-integer casts, casts from non-nested dtypes into lists, bitwise ops between integers and booleans, cat.get_categories(), cat.to_local(), LazyFrame.profile(), and to_struct() calls without field names. Alongside it, cloud IO keeps getting attention: bytes-based concurrency control, callback sinks on cloud, and non-blocking path expansion.
A deprecation batch this size is not routine tidying — it is the removal list for a future major, and the common theme is closing implicit conversions that silently change semantics. The performance and correctness work points the same way, toward the streaming engine as the default execution path rather than a mode: nested common subplan elimination, streaming grouped AsOf joins, hand-written Thrift for parquet metadata decode, and repeated fixes to sortedness and chunking on the streaming path. Cloud is the third leg, with the engine being taught to run against object storage without materializing.
With the streaming engine marked stable and this many APIs deprecated in a single wave, the deprecations are the visible countdown to a release that removes them. The entries do not say when, so the safer read is that the next Python releases keep pairing streaming-path fixes with further deprecation notices rather than breaking anything yet.
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 MotherDuck or Polars.
Feature releases every two months in 2024; one bugfix release in the last twelve.
MCP servers became first-class governed assets in 1.13.0 — and 2.0 is now in release candidate.
Every release in this window is columnstore work — compression is where TimescaleDB is spending
Six releases, all patches — this window shows DuckDB's maintenance machine, not its roadmap
Two engines in one repo: the Python 1.x line tightens while Fusion 2.0 goes lakehouse-catalog native
Basedash turned its AI analyst into an API, then spent two weeks making it auditable
See all MotherDuck alternatives → · See all Polars alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. MotherDuck 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. MotherDuck 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 MotherDuck alternatives in Analytics are ranked by recent ship velocity. Browse the "MotherDuck alternatives" section above for the current picks, or visit /alternatives/motherduck for the full list with editorial commentary on each.
Top Polars alternatives in Analytics are ranked by recent ship velocity. Browse the "Polars alternatives" section above for the current picks, or visit /alternatives/polars for the full list with editorial commentary on each.