Whatagraph
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
A side-by-side editorial comparison of AgencyAnalytics and mapsf — release velocity, themes, recent moves, and the top alternatives to consider.
AgencyAI got skills three weeks ago; everything since has been making them routine.
The cadence is weekly and heavily weighted toward AgencyAI. Skills landed in early August as named, runnable agency tasks; scheduling followed, so those tasks now run on their own. Around the assistant, the reporting surface keeps widening: advanced filtering on custom metrics and KPIs, client tags, a report shares view, and a MailerLite data source that brings email campaign metrics alongside every other channel.
Thematic mapping in base R that finally got a theming system, then spent two years polishing legends.
mapsf produces thematic maps on R's base graphics device — choropleths, proportional symbols, typology maps, rasters, and their combinations, with legends, scale bars, north arrows, and insets as composable elements. Version 1.0.0 was the structural release, introducing a theming system that deprecated eight scattered styling arguments and adding mf_png() and mf_svg() export helpers plus alpha transparency across map types. The 1.1.x and 1.2.x line since then has been steady refinement: background and extent control on the drawing functions, decimal and thousands-separator control in legends, and label placement arguments.
The cadence is weekly and heavily weighted toward AgencyAI. Skills landed in early August as named, runnable agency tasks; scheduling followed, so those tasks now run on their own. Around the assistant, the reporting surface keeps widening: advanced filtering on custom metrics and KPIs, client tags, a report shares view, and a MailerLite data source that brings email campaign metrics alongside every other channel.
The assistant is being moved from something an operator invokes to something that runs on a schedule against connected client data, which changes it from a feature into part of the reporting pipeline. The integration work continues at its usual pace and serves the same end — the more channels are connected, the more a scheduled skill has to reason over. Filtering and tagging are the plumbing that lets those tasks be scoped to the right accounts.
Expect scheduled skills to gain delivery — results pushed into reports or sent to clients — rather than staying inside the assistant panel.
mapsf produces thematic maps on R's base graphics device — choropleths, proportional symbols, typology maps, rasters, and their combinations, with legends, scale bars, north arrows, and insets as composable elements. Version 1.0.0 was the structural release, introducing a theming system that deprecated eight scattered styling arguments and adding mf_png() and mf_svg() export helpers plus alpha transparency across map types. The 1.1.x and 1.2.x line since then has been steady refinement: background and extent control on the drawing functions, decimal and thousands-separator control in legends, and label placement arguments.
The package has been consolidating control into fewer, more consistent places. Legend handling moved out to the maplegend package in 0.8.0 and the per-element mf_legend_* functions were deprecated in favor of arguments on the map calls themselves; theming replaced ad-hoc style arguments in 1.0.0; and recent releases keep propagating the same argument vocabulary — bg, extent, leg_val_rnd, leg_val_dec, leg_val_big — across every function that should accept it. Determinism is a visible concern too, with 1.2.1 fixing a seed so mf_distr() point positions stop moving between runs.
The recent releases are almost entirely argument-parity work across existing functions, so expect that to continue until the vocabulary is uniform rather than any new map type appearing.
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 AgencyAnalytics or mapsf.
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 AgencyAnalytics alternatives → · See all mapsf alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. AgencyAnalytics 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. AgencyAnalytics 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.
Top AgencyAnalytics alternatives in Analytics are ranked by recent ship velocity. Browse the "AgencyAnalytics alternatives" section above for the current picks, or visit /alternatives/agencyanalytics for the full list with editorial commentary on each.
Top mapsf alternatives in Analytics are ranked by recent ship velocity. Browse the "mapsf alternatives" section above for the current picks, or visit /alternatives/mapsf for the full list with editorial commentary on each.