AgencyAnalytics
AgencyAI got skills three weeks ago; everything since has been making them routine.
A side-by-side editorial comparison of Dovetail and tulpa — release velocity, themes, recent moves, and the top alternatives to consider.
Dovetail spent July opening doors to other tools; August is spent making its own rooms easier to enter.
Dovetail is a customer-research workspace whose center of gravity has moved to chat and agents. July was an integration run — Snowflake into Channels, a Microsoft Copilot connector, MCP tools inside chat, and a one-click menu for sending work out to Linear or Notion. August contains no new reach at all: every release this month files down the chat and Digital Twin surface that those integrations feed.
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
tulpa is the C++/R Bayesian spatial inference engine sitting under gcol33's family of ecological occupancy packages, tagging 0.0.x releases several times a week. 0.1.0 is its first CRAN release, and the notes state outright that the engine surface is unchanged from 0.0.198 — the work is packaging discipline: local T bindings rebound to n_t/n_times, OpenMP teams capped under R CMD check, the pkgdown deploy narrowed, an aspell dictionary added. The window behind it splits between the S3 generics conversion and numerical-correctness work in the nested-Laplace grid.
Dovetail is a customer-research workspace whose center of gravity has moved to chat and agents. July was an integration run — Snowflake into Channels, a Microsoft Copilot connector, MCP tools inside chat, and a one-click menu for sending work out to Linear or Notion. August contains no new reach at all: every release this month files down the chat and Digital Twin surface that those integrations feed.
The pattern across the last five releases is access, not capability. Digital Twins went from a two-step workaround — make a generic agent, then change its type — to a first-class create option, then gained a share link that lands a recipient in a conversation rather than a configure page. Chat is being simplified along the same line, with a thinner footer and scoped context that survives the jump to fullscreen. Dovetail is preparing these agents for people who will never build one.
Expect the sharing path to keep widening — permissions, guest access, or an embed for a twin link — since a link that opens straight into chat only pays off if it can safely leave the workspace.
tulpa is the C++/R Bayesian spatial inference engine sitting under gcol33's family of ecological occupancy packages, tagging 0.0.x releases several times a week. 0.1.0 is its first CRAN release, and the notes state outright that the engine surface is unchanged from 0.0.198 — the work is packaging discipline: local T bindings rebound to n_t/n_times, OpenMP teams capped under R CMD check, the pkgdown deploy narrowed, an aspell dictionary added. The window behind it splits between the S3 generics conversion and numerical-correctness work in the nested-Laplace grid.
Two moves in nine days point at the same destination: the generics conversion made tulpa extensible by downstream packages, and CRAN admission makes it installable by them. The current cadence — several tags a week, some existing only to record a measurement that produced no code change — does not survive CRAN's submission overhead, so the release rhythm has to slow whether or not the project intends it. The correctness work still clusters on the joint nested-Laplace driver, and 0.1.0 extends the same diagnostics habit with .NL_AXIS_SD_REASONS, a closed vocabulary for an outer axis whose grid does not contain its own posterior mode.
Expect tulpaObs to follow tulpa onto CRAN, since it is the consumer whose registrations the engine has spent this window unblocking, and expect the version line to move in larger, less frequent steps now that each one carries a submission.
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 Dovetail or tulpa.
AgencyAI got skills three weeks ago; everything since has been making them routine.
Interfaces gets the permissions layer it needed, one release after launching.
RecoveryManager Plus keeps widening its backup coverage across the Microsoft identity estate.
Omni ships weekly, and almost every week the headline item is an AI feature.
silx settles into maintenance a release after its PySide6 migration
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
See all Dovetail alternatives → · See all tulpa alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. tulpa is currently shipping more aggressively (velocity 7.5 vs 5.0), with 2 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. tulpa is currently shipping more aggressively (velocity 7.5 vs 5.0), with 2 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 Dovetail alternatives in Analytics are ranked by recent ship velocity. Browse the "Dovetail alternatives" section above for the current picks, or visit /alternatives/dovetail for the full list with editorial commentary on each.
Top tulpa alternatives in Analytics are ranked by recent ship velocity. Browse the "tulpa alternatives" section above for the current picks, or visit /alternatives/tulpa for the full list with editorial commentary on each.