artoo
artoo makes any-to-any clinical dataset conversion lossless by construction.
A side-by-side editorial comparison of campsis and Tailscale — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | campsis | Tailscale |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 3.8 | 6.3 |
| Sparks · 30d | 1 | 0 |
| Top themes | pharmacometrics, clinical-trial-simulation, breaking-changes, json-interface | networking, scale, api, kubernetes |
| Last editorial update | 2h ago | 3h ago |
| Website | Visit → | — |
Campsis breaks its API on purpose: snake_case throughout, RxODE compatibility cut loose.
Campsis runs clinical-trial simulations from pharmacometric models, sitting on mrgsolve and rxode2 as interchangeable engines, with the sibling package Campsismod supplying the model object layer. Version 1.9.0 is the release where the suite stops carrying its history: the whole API migrates to snake_case, backward compatibility with the old RxODE package is removed, and result processing is refactored into output functions that can be applied as a collection, with an NCA table the first substantial one. Campsismod made the same snake_case move a week earlier, so this is a suite-wide rename rather than one package's decision.
Tailscale is paying down scale in two dimensions: nodes per tailnet, tailnets per org.
Three threads run through this window. The tailnet management API is the newest: creation landed in alpha in late July, and the list endpoint now paginates at 100 results with limit and cursor parameters. The client releases are patch-grade but weighted toward scale — v1.102.1 made node additions and removals constant-time, and v1.102.3 fixes Tailnet Lock startup failures on large tailnets while cutting memory use on iOS and tvOS. The Kubernetes operator runs on its own track, adding in-cluster PeerRelays, workload identity federation and IPv6 egress.
Campsis runs clinical-trial simulations from pharmacometric models, sitting on mrgsolve and rxode2 as interchangeable engines, with the sibling package Campsismod supplying the model object layer. Version 1.9.0 is the release where the suite stops carrying its history: the whole API migrates to snake_case, backward compatibility with the old RxODE package is removed, and result processing is refactored into output functions that can be applied as a collection, with an NCA table the first substantial one. Campsismod made the same snake_case move a week earlier, so this is a suite-wide rename rather than one package's decision.
The 1.8 and 1.9 releases together describe a package being made drivable from outside R. JSON interfaces arrived first for models in Campsismod 1.3.0 and for datasets in Campsis 1.8.0, then extended to scenarios, settings and study replication; the output side has now been generalised the same way, from fixed result processing to a collection of output functions applied to simulated results. Renaming every function and cutting RxODE loose is the cost of that consolidation, paid in one deliberate breaking release rather than spread across several.
With the rename and the RxODE removal behind it, the next releases should restore the rxode2 engine to the test suite, which 1.9.0 removed temporarily, and continue filling out the output-function catalogue beyond NCA. The JSON surface looks like the intended entry point for driving Campsis from outside R, though the entries do not say what is meant to consume it.
Three threads run through this window. The tailnet management API is the newest: creation landed in alpha in late July, and the list endpoint now paginates at 100 results with limit and cursor parameters. The client releases are patch-grade but weighted toward scale — v1.102.1 made node additions and removals constant-time, and v1.102.3 fixes Tailnet Lock startup failures on large tailnets while cutting memory use on iOS and tvOS. The Kubernetes operator runs on its own track, adding in-cluster PeerRelays, workload identity federation and IPv6 egress.
The qualifier that keeps recurring is “large”: tailnets big enough to break Tailnet Lock at startup, node churn that pinned CPU, mobile clients running short of memory, and organizations holding more than a hundred tailnets. Tailscale is absorbing the cost of customers who outgrew the shape the product originally assumed, in two directions at once — nodes inside a tailnet, and tailnets inside an organization. The second is the more consequential, because allocating a tailnet per customer or per environment is a different product than a company network. Security work stays continuous alongside it, with TS-2026-011 closed here and a run of SSH and Serve advisories backported the month before.
The tailnet creation API should leave alpha carrying the same limit-and-cursor contract just applied to the list endpoint, with further startup and memory work aimed at large tailnets on the client side.
Other Infra & APIs 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 campsis or Tailscale.
artoo makes any-to-any clinical dataset conversion lossless by construction.
tabular went from clinical tables to complete TFL output in under two months.
usmapdata ships its 2025 shapefiles on the year-indexed model it adopted in 0.4.0.
glcdp reaches 1.0.0 with a stable schema contract behind its data explorer.
prova adds expected-utility calculation on top of its Bayesian inference core.
checkhelper grew from a check wrapper into a CRAN pre-submission auditor.
See all campsis alternatives → · See all Tailscale alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Tailscale is currently shipping more aggressively (velocity 6.3 vs 3.8), with 0 editorial sparks in the last 30 days against 1. 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. Tailscale is currently shipping more aggressively (velocity 6.3 vs 3.8), with 0 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top campsis alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "campsis alternatives" section above for the current picks, or visit /alternatives/campsis for the full list with editorial commentary on each.
Top Tailscale alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Tailscale alternatives" section above for the current picks, or visit /alternatives/tailscale for the full list with editorial commentary on each.