rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
Comparison · Analytics
Countly vs rotl
A side-by-side editorial comparison of Countly and rotl — release velocity, themes, recent moves, and the top alternatives to consider.
Countly vs rotl: at a glance
What is Countly?
Countly's LTS line is spending its releases on hardening the surfaces customers extend.
The 25.03 LTS and 24.05 branches are moving together, and the recent content is dominated by security and scoping work rather than features. The latest LTS rebuilds the api and frontend Docker images as multi-stage builds on Debian 13 with Node 24 so compilers and build tooling no longer ship, overrides fourteen vulnerable transitive dependencies, and replaces the unmaintained v8-sandbox behind custom code with isolated-vm. Earlier releases scoped internal event hooks to their own apps, fixed the consents table returning fields beyond the consent columns, and stopped dashboard widgets being copied by users without access to the referenced apps.
What is rotl?
rotl's whole release history is keeping name matching honest against a moving taxonomy.
Nearly every entry concerns `tnrs_match_names()`, the function that maps user-supplied names onto Open Tree taxonomy ids. 3.1.0 changed which taxon wins a multi-way match — highest matching score rather than lowest OTT id, reversing the rule 3.0.4 introduced. 3.0.12 defaulted `context_name` to 'All life' so a context inferred from the first name could not silently skew later ones. 3.0.11 made a total failure to match return an empty tibble with a warning instead of an error. The rest are small fixes tracking Open Tree API changes.
Countly vs rotl: editorial side-by-side
Countly
5.0ANALYTICS
Countly's LTS line is spending its releases on hardening the surfaces customers extend.
◆ Current state
The 25.03 LTS and 24.05 branches are moving together, and the recent content is dominated by security and scoping work rather than features. The latest LTS rebuilds the api and frontend Docker images as multi-stage builds on Debian 13 with Node 24 so compilers and build tooling no longer ship, overrides fourteen vulnerable transitive dependencies, and replaces the unmaintained v8-sandbox behind custom code with isolated-vm. Earlier releases scoped internal event hooks to their own apps, fixed the consents table returning fields beyond the consent columns, and stopped dashboard widgets being copied by users without access to the referenced apps.
◆ Where it's heading
The pattern across these releases is closing the gaps where a customer-supplied artefact — custom hook code, a copied widget, a projection on a request — could reach further than intended. That work is now touching the runtime itself, and the isolated-vm swap is a breaking change: custom code relying on setTimeout, setInterval or async completion fails with a logged error instead of running. The journey engine is the only place shipping genuinely new capability, and it is enterprise-only.
◆ Prediction
Expect follow-up releases to soften the custom-code migration, since the isolated-vm switch silently breaks any hook that awaited a timer, and further ab-testing work now that pystan has been replaced with compiled Stan executables.
rotl
0.0ANALYTICS
rotl's whole release history is keeping name matching honest against a moving taxonomy.
◆ Current state
Nearly every entry concerns `tnrs_match_names()`, the function that maps user-supplied names onto Open Tree taxonomy ids. 3.1.0 changed which taxon wins a multi-way match — highest matching score rather than lowest OTT id, reversing the rule 3.0.4 introduced. 3.0.12 defaulted `context_name` to 'All life' so a context inferred from the first name could not silently skew later ones. 3.0.11 made a total failure to match return an empty tibble with a warning instead of an error. The rest are small fixes tracking Open Tree API changes.
◆ Where it's heading
The recurring problem is ambiguity: names match several taxa, and the package has changed its tie-breaking rule twice while making failures and edge cases return predictable objects rather than errors. Nothing here expands what rotl can retrieve; it makes what it retrieves reproducible. The feed also stops in mid-2023, so the package appears dormant.
◆ Prediction
Nothing in the window suggests new capability. If a release comes, the pattern says it will follow an Open Tree API change or another matching-behaviour correction.
Alternatives to Countly and rotl
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 Countly or rotl.
writexl
writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.
rgbif
rgbif is steadily pushing users off paged searching and onto real downloads.
rstanarm
rstanarm is community-maintained now, tracking Stan and lme4 rather than adding models.
taxa
taxa started a ground-up rewrite in 2021 and has published almost nothing since.
taxize
taxize spends its releases absorbing other people's API changes, one dead source at a time.
See all Countly alternatives → · See all rotl alternatives →
Recent activity from Countly and rotl
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoCountlyCustom-code sandbox swapped to isolated-vm; images rebuilt on Node 24
- 10d agoCountlyFixes for event keys containing special characters
- 10d agoCountlyJourney deeplinks take dynamic parameters; hooks validated on save
- 21d agoCountlyStar-rating logo path and data-manager transformation fixes
- 22d agoCountlyLTS backport: data-manager transformation fix
- 1mo agoCountlyJourneys survive user merges; SDK-provided asset paths
- 3y agorotlrotl 3.1.0 matches on score instead of lowest OTT id
- 4y agorotlrotl 3.0.12 defaults matching context to All life
- 5y agorotlrotl 3.0.11 returns empty tibble when no names match
- 6y agorotlrotl 3.0.10 tracks Open Tree API updates
- 7y agorotlrotl 3.0.9 tracks Open Tree API updates
- 7y agorotlrotl 3.0.7 updates vignette for TNRS endpoint change
Frequently asked questions
What is the difference between Countly and rotl?
They serve adjacent needs but don't currently overlap on shipped themes. Countly is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 Countly better than rotl?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Countly is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 Countly?
Top Countly alternatives in Analytics are ranked by recent ship velocity. Browse the "Countly alternatives" section above for the current picks, or visit /alternatives/countly for the full list with editorial commentary on each.
What are the best alternatives to rotl?
Top rotl alternatives in Analytics are ranked by recent ship velocity. Browse the "rotl alternatives" section above for the current picks, or visit /alternatives/rotl for the full list with editorial commentary on each.