Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
A side-by-side editorial comparison of r2dii.analysis and Usermaven — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | r2dii.analysis | Usermaven |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 8.8 |
| Sparks · 30d | 0 | 3 |
| Top themes | climate-finance, portfolio-alignment, pacta, scenario-analysis | product-analytics, reverse-etl, mcp, crm-integration |
| Last editorial update | 3d ago | 1d ago |
| Website | Visit → | — |
The climate-alignment maths behind PACTA, now stable and maintained rather than reshaped
r2dii.analysis computes the target-setting side of PACTA: market-share and sectoral decarbonisation targets that measure a loan book or portfolio against climate scenarios. It sits downstream of the matched company data the sibling packages produce. The 0.5.0 release declared it lifecycle-stable and handed maintenance to a new lead, and releases since have been narrow corrections rather than new methods.
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
Three consecutive releases have each opened a different edge of the product. Event Sources brought conversion events in from payments, CRMs and spreadsheets without code; the MCP server let any AI client query the workspace; the newest adds a read-only Salesforce connection, Reverse ETL pushing Usermaven audiences into operational tools, external MCP connectors feeding Maven AI outside context, and configurable engagement scoring. Underneath, the analysis surfaces were consolidated earlier in the summer into Analytics Hub and a command bar.
r2dii.analysis computes the target-setting side of PACTA: market-share and sectoral decarbonisation targets that measure a loan book or portfolio against climate scenarios. It sits downstream of the matched company data the sibling packages produce. The 0.5.0 release declared it lifecycle-stable and handed maintenance to a new lead, and releases since have been narrow corrections rather than new methods.
The history is a package converging. Early releases churn the output contract of target_market_share() and target_sda() — which sectors appear, which years, how missing production is treated — and each change alters the numbers users get. The ald-to-abcd rename runs across several releases before completing, and by 0.5.0 the churn has stopped, with three older summarise functions soft-deprecated and the package marked stable. What remains is edge-case correctness in target coverage.
With the package marked stable and the terminology migration finished, the soft-deprecated summarise functions are the obvious next thing to remove outright.
Three consecutive releases have each opened a different edge of the product. Event Sources brought conversion events in from payments, CRMs and spreadsheets without code; the MCP server let any AI client query the workspace; the newest adds a read-only Salesforce connection, Reverse ETL pushing Usermaven audiences into operational tools, external MCP connectors feeding Maven AI outside context, and configurable engagement scoring. Underneath, the analysis surfaces were consolidated earlier in the summer into Analytics Hub and a command bar.
The shape is a product deliberately becoming a hub rather than a destination. Ingest, query and activation have each been generalized in turn, and the common design choice is to hand the boundary to a standard or a connector rather than build integrations one at a time. What is left proprietary is the middle — identity resolution, attribution, engagement scoring — which is where the release notes keep adding configurability. The Salesforce connection being read-only in its first cut fits the pattern: land the schema mapping, then open the write path.
Salesforce write-back is the obvious next step, since Reverse ETL already exists as the mechanism and the entry marks read-only as a first release. Expect more CRM connectors on the same template — read-only, per-org field mapping, sandbox first.
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 r2dii.analysis or Usermaven.
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio ships through release branches, and the notes are commit messages
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
See all r2dii.analysis alternatives → · See all Usermaven alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Usermaven is currently shipping more aggressively (velocity 8.8 vs 0.0), with 3 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. Usermaven is currently shipping more aggressively (velocity 8.8 vs 0.0), with 3 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 r2dii.analysis alternatives in Analytics are ranked by recent ship velocity. Browse the "r2dii.analysis alternatives" section above for the current picks, or visit /alternatives/r2dii-analysis for the full list with editorial commentary on each.
Top Usermaven alternatives in Analytics are ranked by recent ship velocity. Browse the "Usermaven alternatives" section above for the current picks, or visit /alternatives/usermaven for the full list with editorial commentary on each.