Whatagraph
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
A side-by-side editorial comparison of omock and Usermaven — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | omock | Usermaven |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 8.8 |
| Sparks · 30d | 0 | 3 |
| Top themes | omop-cdm, synthetic-data, test-fixtures, health-data | product-analytics, reverse-etl, mcp, crm-integration |
| Last editorial update | 5d ago | 1d ago |
| Website | Visit → | — |
A mock-data generator for OMOP studies that keeps widening what it can fake.
omock builds synthetic OMOP Common Data Model tables so packages in the darwin-eu and OHDSI ecosystem can be tested without touching patient data. The 0.7.0 release adds concept set subsetting with its own vignette, unit and value support in mockMeasurement, observation date validation and cohort attrition initialization, while deprecating mockConcepts. Releases arrive as PR digests rather than written notes.
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.
omock builds synthetic OMOP Common Data Model tables so packages in the darwin-eu and OHDSI ecosystem can be tested without touching patient data. The 0.7.0 release adds concept set subsetting with its own vignette, unit and value support in mockMeasurement, observation date validation and cohort attrition initialization, while deprecating mockConcepts. Releases arrive as PR digests rather than written notes.
The package has been moving from generating tables to shipping and managing reference datasets — mockDatasets arrived in 0.4.0, mockCdmFromDataset gained a source argument in 0.5.0, and 0.6.1 added download retry handling plus an internal GiBleed dataset after the hosted files moved. The recent work is filling in CDM fidelity: type concepts, measurement units, attrition, and guards for degenerate cases like an empty person table.
Expect coverage to keep extending table by table toward the parts of the CDM that omock still cannot mock, with mockConcepts removed outright once the concept set subsetting path settles.
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 omock or Usermaven.
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
Lightdash keeps handing authoring to outside agents and keeping the governed layer for itself.
A 4.4.0 tag appears, but the feed carries only its release plumbing
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
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
See all omock 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 omock alternatives in Analytics are ranked by recent ship velocity. Browse the "omock alternatives" section above for the current picks, or visit /alternatives/omock-r 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.