Market-data freshness
Equivalent assets, fields, completeness rules, regions and cache states across comparable providers.
Benchmark lab / coming soon
Reproducible performance evidence is coming.
PRION is built as a competitive trading system. Public comparative numbers will follow only when the complete workload, raw attempts, exclusions and environment can be inspected and rerun.
Planned benchmark lanes
Measure the whole execution path.
Market-data freshness, transaction preparation and landing behavior need different clocks and different evidence. They will not be folded into one unsupported speed claim.
Quote and build
Equivalent markets, amounts, transaction semantics and custody boundaries across PRION and comparable routing APIs.
Send and land
Submission, inclusion, confirmation, failure rate and cost measured as separate stages under one workload.
Publication requirements
Evidence before rankings.
Equivalent work
Compare the same market, amount, fields, transaction semantics, region and timing boundary—not endpoints that merely share a name.
Complete attempts
Publish successes, failures, retries, rate limits and credential exclusions beside p50, p95 and p99 results.
Pinned environment
Bind raw rows to the code commit, provider versions, region, concurrency, cache policy and sample window.
Separated stages
Report quote, build, send, inclusion, confirmation and finality independently so one fast number cannot hide another slow stage.
Current status
No public ranking yet.
Earlier internal observations are not the reproducible evidence package and are not presented here as a provider comparison. The public devkit already supplies deterministic fixtures and exact local checks that the future benchmark harness can build upon.
Inspect the devkit evidence ↗Tell us what your trading product needs measured.
Private API discussions help prioritize markets, regions, traffic shapes and comparison lanes while the reproducible package is built.
Request API access