The series

Benchmarks, numbered like they matter.

Every Boundstone benchmark is a numbered public event: announced before data exists, frozen before results, disputed by vendors before publication. Cherry-picking dies in that order. Read the full methodology →

№ 001

US phone validation

Boundstone vs 1Lookup, Trestle, Twilio Lookup and NumVerify — ~1,000-number owned dataset; validity, line type and carrier scored; abstain ≠ wrong.

Awaiting freeze
Announced · 2026-07-14 Freeze — repo tag + final checksum Collect — all vendors, same day Dispute — vendors get 14 days Publish — win or lose
METHODOLOGY V1.0-DRAFT · SHA-256
e258426c657aa196eae4331e46e1358e3f828ff1f2c8736d892f347e90dbb7ce
Final checksum posts when the repo is tagged. Until then, every edit to the draft is public in its history — the hash above is the draft you can hold us to.
№ 002 — International HLR liveness

Per-country mobile liveness via HLR — queued until № 001 publishes. Numbered now so nobody can accuse us of inventing the series after a win.

№ 003 — IP intelligence

Proxy/VPN detection and geo accuracy — queued until № 001 publishes.

The ritual

  1. AnnounceThe run gets a number and a scope — in public, before any data exists.
  2. FreezeThe methodology repo is tagged and its SHA-256 posted. Scoring rules can't move after this.
  3. CollectEvery vendor gets the same dataset on the same day, fully logged.
  4. DisputeVendors see their raw disagreement rows and get 14 days before anything publishes.
  5. PublishResults ship win or lose. Abstain ≠ wrong. The chart space is already reserved.

Be there when it drops

Pre-launch — benchmark results and early API access. One email. We validate emails for a living — we're not going to spam yours.