pr2database
The protist reference database keeps widening past the rRNA gene it was built on.
Comparison · Infra & APIs
states vs Tailscale
A side-by-side editorial comparison of states and Tailscale — release velocity, themes, recent moves, and the top alternatives to consider.
states vs Tailscale: at a glance
| Feature | states | Tailscale |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 0 |
| Top themes | political-science, panel-data, country-codes, datasets | networking, scale, api, kubernetes |
| Last editorial update | 44m ago | 7h ago |
| Website | Visit → | — |
What is states?
State-panel tooling holding steady since its 2020 data and ergonomics release.
states supplies the Gleditsch & Ward and Correlates of War state lists and the tooling to turn them into country-year or country-month panels, with plot_missing() for coverage checks. The substantive work landed in 2020; the releases since are compatibility fixes against ggplot2, dplyr, readr and testthat. The most recent entry is a single test repair.
What is Tailscale?
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.
states vs Tailscale: editorial side-by-side
states
0.0INFRA · APIS
State-panel tooling holding steady since its 2020 data and ergonomics release.
◆ Current state
states supplies the Gleditsch & Ward and Correlates of War state lists and the tooling to turn them into country-year or country-month panels, with plot_missing() for coverage checks. The substantive work landed in 2020; the releases since are compatibility fixes against ggplot2, dplyr, readr and testthat. The most recent entry is a single test repair.
◆ Where it's heading
The package has reached the point where its own data and API are settled and the release trigger is upstream churn in the tidyverse. What movement there is goes toward making the two state lists interchangeable, with the microstates coding carried from G&W onto the COW data as the clearest example, rather than toward new datasets.
◆ Prediction
The next release is most likely another compatibility pass; a data refresh would be the signal that the package is active again.
Tailscale
6.3INFRA · APIS
Tailscale is paying down scale in two dimensions: nodes per tailnet, tailnets per org.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to states and Tailscale
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 states or Tailscale.
ggalign
Composable aligned layouts, rebuilt on S7 while ggplot2 4.0 lands underneath.
prioritizr
Conservation planning absorbs the literature's target-setting rules as code.
jSDM
Joint species distribution models in Gibbs-sampled C++, quiet since 2023.
rsofun
An ecosystem model starts tracking carbon isotopes and land-use change.
usmap
Ten years in, US mapping splits its data out and finally adds Puerto Rico.
See all states alternatives → · See all Tailscale alternatives →
Recent activity from states and Tailscale
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoTailscalev1.102.3 patches a 4via6 routing flaw and large-tailnet startups
- 2d agoTailscaleTailnet list API pagination
- 9d agoTailscaleOperator adds in-cluster PeerRelays and workload identity federation
- 13d agoTailscaleContainer image v1.102.2: library updates only
- 16d agoTailscalev1.102.2 fixes a Funnel incoming-connection regression
- 17d agoTailscalev1.102.1 adds Services CLI and constant-time node churn
- 0y agostatesplot_missing() test fixed for the next ggplot2
- 2y agostatesggplot2 and dplyr deprecation cleanup
- 2y agostatesBundled state data stripped to plain data frames
- 5y agostatesMicrostate coding for COW data and state_panel() shortcuts
- 7y agostatesSimpler defaults for state_panel() and plot_missing()
Frequently asked questions
What is the difference between states and Tailscale?
They serve adjacent needs but don't currently overlap on shipped themes. Tailscale is currently shipping more aggressively (velocity 6.3 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 states better than Tailscale?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Tailscale is currently shipping more aggressively (velocity 6.3 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to states?
Top states alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "states alternatives" section above for the current picks, or visit /alternatives/states for the full list with editorial commentary on each.
What are the best alternatives to Tailscale?
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.