← Back to home
Comparison · Infra & APIs

PINstimation vs Skipper

A side-by-side editorial comparison of PINstimation and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.

PINstimation vs Skipper: at a glance

FeaturePINstimationSkipper
SectorInfra & APIsInfra & APIs
Velocity score0.05.0
Sparks · 30d00
Top themesmarket-microstructure, finance, informed-trading, r-packagereverse-proxy, kubernetes, memory-footprint, zone-aware-routing
Last editorial update45m ago11h ago
WebsiteVisit →Visit →

What is PINstimation?

A market-microstructure toolkit that keeps adding estimators as the papers land.

PINstimation estimates probability-of-informed-trading models — PIN, multilayer PIN, adjusted PIN and VPIN — from trade and quote data, and handles the trade classification and aggregation that feeds them. The current 0.2.0 adds ivpin(), a maximum-likelihood variant of VPIN from Ke and Lin (2017). The package's early history is compressed into a single hour of backfilled tags in October 2022, so version order there does not track release order.

Read the full PINstimation trajectory →

What is Skipper?

Skipper trims a 4x memory regression out of routesrv, days after shipping h2c

Zalando's HTTP router ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.63, which stops routesrv holding an uncompressed route tree alongside the compressed buffer: retained memory in the release's own benchmark falls from 30.7 MB to 2.0 MB, undoing most of the 4x increase zone-aware routing had introduced. Around it sit narrow auth repairs, and an eskip parser change that finally accepts negative numeric arguments in predicates and filters.

Read the full Skipper trajectory →

PINstimation vs Skipper: editorial side-by-side

P
PINstimation
INFRA · APIS
0.0

A market-microstructure toolkit that keeps adding estimators as the papers land.

◆ Current state

PINstimation estimates probability-of-informed-trading models — PIN, multilayer PIN, adjusted PIN and VPIN — from trade and quote data, and handles the trade classification and aggregation that feeds them. The current 0.2.0 adds ivpin(), a maximum-likelihood variant of VPIN from Ke and Lin (2017). The package's early history is compressed into a single hour of backfilled tags in October 2022, so version order there does not track release order.

◆ Where it's heading

Each release tracks the literature: a Bayesian PIN estimator from Griffin et al., an improved VPIN from Ke and Lin, initial-parameter generation realigned to Ersan and Ghachem. The other steady thread is data handling — matrix inputs so the estimators compose with rolling windows, user-specified aggregation frequencies, and now quote leads as well as lags. The three-year gap between 0.1.2 and 0.2.0 makes this a slow, publication-paced package rather than an actively developed one.

◆ Prediction

On this pattern the next release adds whatever estimator the authors publish next, since two of the three feature releases here implement a specific paper. Nothing in the entries points to a change in the package's structure.

S
Skipper
INFRA · APIS
5.0

Skipper trims a 4x memory regression out of routesrv, days after shipping h2c

◆ Current state

Zalando's HTTP router ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.63, which stops routesrv holding an uncompressed route tree alongside the compressed buffer: retained memory in the release's own benchmark falls from 30.7 MB to 2.0 MB, undoing most of the 4x increase zone-aware routing had introduced. Around it sit narrow auth repairs, and an eskip parser change that finally accepts negative numeric arguments in predicates and filters.

◆ Where it's heading

Two threads run through the recent tags. The data path keeps getting real work - leastRequests balancing, then h2c end to end in v0.27.57, now the memory cost of zone-aware routing being paid back. The auth filters, by contrast, are only being maintained: token introspection, grant auth, and now the OIDC Referer handling are fixes rather than new capability, and several are follow-ups to each other rather than independent bugs.

◆ Prediction

Zone-aware routing looks like the source of the recent memory attention, so expect further tuning around route storage and the hash computation done on every pull, which the release's second benchmark already isolates. The OIDC cookie change is the second link in an auth chain that started with the grant-auth fix, and is likely to draw another follow-up.

Alternatives to PINstimation and Skipper

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 PINstimation or Skipper.

See all PINstimation alternatives → · See all Skipper alternatives →

Recent activity from PINstimation and Skipper

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoSkipperMove OIDC flow protection from Referer to cookies
  2. 1d agoSkipperv0.27.63: Store routes compressed-only, decompress on demand (#4198)
  3. 1d agoSkipperEskip predicates and filters accept negative numbers
  4. 2d agoSkipperFix token introspection handling
  5. 2d agoSkipperFix grant auth flow
  6. 2d agoSkipperUpdate outdated golang.org/x dependencies
  7. 8mo agoPINstimationPINstimation 0.2.0
  8. 3y agoPINstimationPINstimation v0.1.2
  9. 3y agoPINstimationPINstimation v0.1.1
  10. 3y agoPINstimationPINstimation v0.0.1-beta
  11. 3y agoPINstimationPINstimation v0.1.0

Frequently asked questions

What is the difference between PINstimation and Skipper?

They serve adjacent needs but don't currently overlap on shipped themes. Skipper 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 PINstimation better than Skipper?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Skipper 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 Infra & APIs products to evaluate alongside.

What are the best alternatives to PINstimation?

Top PINstimation alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "PINstimation alternatives" section above for the current picks, or visit /alternatives/pinstimation for the full list with editorial commentary on each.

What are the best alternatives to Skipper?

Top Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.