Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
Comparison · Analytics
Omni vs TwoSampleMR
A side-by-side editorial comparison of Omni and TwoSampleMR — release velocity, themes, recent moves, and the top alternatives to consider.
Omni vs TwoSampleMR: at a glance
What is Omni?
Omni ships weekly, and almost every week the headline item is an AI feature.
Omni publishes a dated weekly digest whose body is a single line listing that week's items, so each entry compresses several releases into a sentence. Across the window the pattern is unmistakable: AI-powered semantic model generation reaching general availability, AI Routines creatable from chat and deliverable to Slack, AI model suggestion endpoints, AI credit controls scoped to embed entity groups and individual users, AI Evals on Azure, and MCP surfaces appearing both in-app and as a searchDashboards tool. The most recent week breaks that streak — default filters on composite topics, stopping a running dashboard query, full-screen preview editing — the first digest in two months led by conventional BI work.
What is TwoSampleMR?
The flagship Mendelian randomization package is auditing its own estimators, one bootstrap at a time.
TwoSampleMR is the MRC-IEU package for two-sample Mendelian randomization against OpenGWAS. Its 2026 releases are a sustained correctness review rather than feature work: 0.7.9 fixed bootstrap standard errors in mr_mode() and mr_rucker_bootstrap() that had been inflated since v0.6.30, and repaired two Rucker functions that were returning malformed objects. Point estimates were not affected by the bootstrap bug.
Omni vs TwoSampleMR: editorial side-by-side
Omni
6.3ANALYTICS
Omni ships weekly, and almost every week the headline item is an AI feature.
◆ Current state
Omni publishes a dated weekly digest whose body is a single line listing that week's items, so each entry compresses several releases into a sentence. Across the window the pattern is unmistakable: AI-powered semantic model generation reaching general availability, AI Routines creatable from chat and deliverable to Slack, AI model suggestion endpoints, AI credit controls scoped to embed entity groups and individual users, AI Evals on Azure, and MCP surfaces appearing both in-app and as a searchDashboards tool. The most recent week breaks that streak — default filters on composite topics, stopping a running dashboard query, full-screen preview editing — the first digest in two months led by conventional BI work.
◆ Where it's heading
Two things have been happening in parallel and they are related. Omni pushed AI into the modelling layer rather than only the query layer, which is what semantic model generation reaching GA signified, then built the commercial and access controls those features require — credit limits per user and per embed entity group arrived within weeks of the capabilities that consume them. The MCP work points at a third direction, exposing Omni's content to external agents rather than only serving its own chat. The latest week's return to filters and query controls suggests the AI surface has reached the point where the surrounding product has to catch up to it.
◆ Prediction
With searchDashboards already shipped as an MCP tool, more of Omni's catalog is the obvious next thing to expose that way, and credit controls should keep extending to cover newer AI surfaces. Whether the non-AI week is a pause or a genuine rebalancing is not something one digest can settle.
TwoSampleMR
0.0ANALYTICS
The flagship Mendelian randomization package is auditing its own estimators, one bootstrap at a time.
◆ Current state
TwoSampleMR is the MRC-IEU package for two-sample Mendelian randomization against OpenGWAS. Its 2026 releases are a sustained correctness review rather than feature work: 0.7.9 fixed bootstrap standard errors in mr_mode() and mr_rucker_bootstrap() that had been inflated since v0.6.30, and repaired two Rucker functions that were returning malformed objects. Point estimates were not affected by the bootstrap bug.
◆ Where it's heading
The pattern across these releases is a package being read line by line — a copy-paste weight vector in ldsc_rg(), chunking that produced zero splits for short SNP lists, penalisation recycled across the wrong SNPs, dead code paths removed, and regression tests added behind each fix. Alongside it runs a mechanical modernization pass: seq_len() for loop indices, tidyr in place of reshape2, current ggplot2 idioms, and the OpenGWAS URL migration. Feature work is limited to forest plot presentation.
◆ Prediction
Expect the audit to continue through the remaining bootstrap and jackknife routines, with releases staying in the 0.7.x patch range and each fix arriving with its own regression test.
Alternatives to Omni and TwoSampleMR
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 Omni or TwoSampleMR.
RStudio
RStudio ships through release branches, and the notes are commit messages
dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Fulcrum
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Holistics
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
See all Omni alternatives → · See all TwoSampleMR alternatives →
Recent activity from Omni and TwoSampleMR
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoOmniOmni adds default filters on composite topics and query stopping
- 9d agoOmniOmni adds presentation mode and a searchDashboards MCP tool
- 16d agoOmniOmni adds AI credit controls per user and embed entity group
- 23d agoOmniAI semantic model generation goes generally available in Omni ⚡
- 1mo agoOmniOmni adds AI suggestion endpoints and OAuth for database connections
- 1mo agoOmniOmni brings AI routines to Slack and adds in-app MCP settings
- 1mo agoTwoSampleMRBootstrap standard errors corrected in mode and Rucker estimators
- 2mo agoTwoSampleMRWrong weight vector and chunking fixes across the estimator set
- 2mo agoTwoSampleMRDeprecated ggplot2 idioms and dead code removed
- 3mo agoTwoSampleMROpenGWAS URLs migrated and Wald ratio warnings quieted
- 4mo agoTwoSampleMRCategorized forest plots aligned with the published figures
- 4mo agoTwoSampleMRFurther internal code optimizations
Frequently asked questions
What is the difference between Omni and TwoSampleMR?
They serve adjacent needs but don't currently overlap on shipped themes. Omni is currently shipping more aggressively (velocity 6.3 vs 0.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.
Is Omni better than TwoSampleMR?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Omni is currently shipping more aggressively (velocity 6.3 vs 0.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.
What are the best alternatives to Omni?
Top Omni alternatives in Analytics are ranked by recent ship velocity. Browse the "Omni alternatives" section above for the current picks, or visit /alternatives/omni for the full list with editorial commentary on each.
What are the best alternatives to TwoSampleMR?
Top TwoSampleMR alternatives in Analytics are ranked by recent ship velocity. Browse the "TwoSampleMR alternatives" section above for the current picks, or visit /alternatives/twosamplemr for the full list with editorial commentary on each.