Mage
Feature releases every two months in 2024; one bugfix release in the last twelve.
A side-by-side editorial comparison of TimescaleDB and MotherDuck — release velocity, themes, recent moves, and the top alternatives to consider.
Every release in this window is columnstore work — compression is where TimescaleDB is spending
TimescaleDB is on a roughly two-week cadence and the releases are dominated by one subsystem. 2.28.0 made first() and last() far cheaper on compressed data by deriving the aggregates straight from columnstore batch metadata rather than decompressing. 2.29.0 added chunk exclusion for DML, so UPDATE and DELETE on hypertables take row exclusive locks only on the chunks actually being modified. The patch releases in between are almost entirely columnar correctness: wrong results from functions returning NULL in the columnar execution pipeline, sort transformation errors on negative constants, column ordering on first/last sparse indexes, incompatible smallint bloom filters, and crashes grouping by columns absent from the SELECT list under vectorized aggregation.
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.
TimescaleDB is on a roughly two-week cadence and the releases are dominated by one subsystem. 2.28.0 made first() and last() far cheaper on compressed data by deriving the aggregates straight from columnstore batch metadata rather than decompressing. 2.29.0 added chunk exclusion for DML, so UPDATE and DELETE on hypertables take row exclusive locks only on the chunks actually being modified. The patch releases in between are almost entirely columnar correctness: wrong results from functions returning NULL in the columnar execution pipeline, sort transformation errors on negative constants, column ordering on first/last sparse indexes, incompatible smallint bloom filters, and crashes grouping by columns absent from the SELECT list under vectorized aggregation.
The compression layer is no longer a storage option bolted onto hypertables — it is being turned into a full query path, with its own aggregate pushdowns, sparse indexes, bloom filters and vectorized execution. The bug pattern confirms how new that path still is: several patches fix wrong results rather than crashes, which is what a young execution engine produces as it meets real query shapes. The DML chunk-exclusion work in 2.29.0 shows the other half of the effort, reducing the lock footprint of writes so compressed hypertables stay usable under mutation, not just under read.
Given that every release in this window touches the columnstore and several fix correctness rather than performance, the next releases should continue hardening that path — more vectorized-aggregation and sparse-index fixes alongside further pushdowns. The entries give no signal of work outside compression.
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.
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 TimescaleDB or MotherDuck.
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.
The streaming engine is stable and the API is being narrowed — Polars is clearing ground for a breaking release
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 TimescaleDB alternatives → · See all MotherDuck 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 TimescaleDB alternatives in Analytics are ranked by recent ship velocity. Browse the "TimescaleDB alternatives" section above for the current picks, or visit /alternatives/timescaledb for the full list with editorial commentary on each.
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.