Benchmarks

We publish signing latency benchmarks with methodology, not marketing numbers. An updated benchmark series on the current release is in progress. Until it is published, this page documents how we measure and how we report.

What we measure

For an increasing number of virtual users (concurrent threads sending one request every 0.5 to 1 second) over 30 minutes:

• Requests per second: total signing requests handled per second.
• HTTP request duration: full roundtrip time for one signature request, including external network latency.
• Signing service latency: time from a sign request arriving at the API until it exits, covering cryptographic operations plus internal processing such as database access. Excludes external network latency.

The first signing request for a wallet is always the slowest, because the private key must be loaded into the enclave. Once cached, subsequent signatures are significantly faster.

How we report

Every published figure ships with its methodology: the release it was measured on, the workload, and whether it includes external network latency. We do not publish a single headline number in isolation, and we label the measurement boundary every time.

Definitions

When Fortkey materials reference signing speed, the figure refers to the end-to-end vault path (decode, policy check, and signature) for the measured series, not the full network roundtrip to a venue. Full roundtrip time depends on where your bot runs relative to the signing region. Multi-region replicas exist precisely to minimize that distance.