Mage
Feature releases every two months in 2024; one bugfix release in the last twelve.
A side-by-side editorial comparison of OpenMetadata and Basedash — release velocity, themes, recent moves, and the top alternatives to consider.
MCP servers became first-class governed assets in 1.13.0 — and 2.0 is now in release candidate.
OpenMetadata maintains two lines at once, 1.12.x and 1.13.x, and has just cut a 2.0.0 release candidate on top of them. The 1.13.0 feature release made MCP a first-class service category with service and server entities, execution logs, test-connection support, REST resources and UI pages, added usage analytics broken down by tool and user, and brought SAML SSO to MCP OAuth. Alongside it landed an RDF knowledge graph built on Apache Jena. Everything since has been maintenance on both lines, weighted heavily toward CVE patching.
Basedash turned its AI analyst into an API, then spent two weeks making it auditable
Basedash is an AI data analyst that spent July becoming two things at once: an agent that acts, and infrastructure other products build on. Actions let it write SQL and operate in Stripe, HubSpot, or anything behind an MCP connector; the developer platform exposes chat, daily insights, automations, and dashboards through the public API. The most recent releases are the counterweight to both — SCIM provisioning, then audit logs that record every query the AI itself runs.
OpenMetadata maintains two lines at once, 1.12.x and 1.13.x, and has just cut a 2.0.0 release candidate on top of them. The 1.13.0 feature release made MCP a first-class service category with service and server entities, execution logs, test-connection support, REST resources and UI pages, added usage analytics broken down by tool and user, and brought SAML SSO to MCP OAuth. Alongside it landed an RDF knowledge graph built on Apache Jena. Everything since has been maintenance on both lines, weighted heavily toward CVE patching.
The catalog is extending its governance model to cover AI tooling rather than just data assets — MCP servers get the same entity, connection-testing and usage-analytics treatment that databases and dashboards receive, and the RDF layer gives the metadata graph a standard query surface. Running underneath that is an unusually heavy security cadence: nearly every maintenance release in this window is a list of dependency CVEs across Jackson, Netty, Spring, log4j, handlebars, MLflow and PyArrow, patched in parallel on both maintained lines. The 2.0.0-rc1 tag suggests that dual-line burden is about to become a three-way one.
Expect 2.0.0 to move from rc1 through further release candidates while 1.13.x continues absorbing connector and governance fixes, and for CVE-driven patch releases to keep landing on both lines in near-lockstep.
Basedash is an AI data analyst that spent July becoming two things at once: an agent that acts, and infrastructure other products build on. Actions let it write SQL and operate in Stripe, HubSpot, or anything behind an MCP connector; the developer platform exposes chat, daily insights, automations, and dashboards through the public API. The most recent releases are the counterweight to both — SCIM provisioning, then audit logs that record every query the AI itself runs.
Two tracks are converging. The agent keeps gaining reach — write access, MCP connectors, unprompted suggestions drawn from your own data — while the surrounding controls arrive just behind it, each release answering the objection the previous one created. The MotherDuck connector marks a third track: the more the analyst is sold as an API, the more it has to speak to whatever warehouse the customer already runs.
Expect governance to extend to Actions specifically — per-connector or per-action approval policy, since audit logs now record agent writes but the entries describe approval as a case-by-case prompt. More data sources after MotherDuck are the safer bet.
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 OpenMetadata or Basedash.
Feature releases every two months in 2024; one bugfix release in the last twelve.
Every release in this window is columnstore work — compression is where TimescaleDB is spending
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
Lightdash is making the whole instance — dashboards, roles, agents — checkable into git
See all OpenMetadata alternatives → · See all Basedash alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — mcp, governance — within Analytics. OpenMetadata and Basedash 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. OpenMetadata and Basedash 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 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.
Top Basedash alternatives in Analytics are ranked by recent ship velocity. Browse the "Basedash alternatives" section above for the current picks, or visit /alternatives/basedash for the full list with editorial commentary on each.