What is the Jitter Tax?

The Jitter Tax is the cumulative alpha loss caused by execution variance in non-deterministic signing environments. ZeroCopy is a sovereign protocol that eliminates this tax by providing highly predictable, 42µs signing latencies.

How do Nitro Enclaves protect my keys?

AWS Nitro Enclaves are isolated compute environments that have no persistent storage, no interactive access, and no external networking. ZeroCopy is an enclave-native runtime that ensures private keys never leave the hardware boundary.

P99: 42µs

The fastest transaction signer on the planet.

Stop bleeding alpha to latency variance.

42µs signing inside AWS Nitro Enclaves. 40+ Rust crates. Battle-tested infrastructure for trading firms and AI agent platforms. Deployed and operated in your VPC.

$curl -fsSL https://zerocopy.systems/zcp/install.sh | sh

Free CLI · Linux + macOS · No signup · 30s install

Or book a free 30-min call

42µsP99 Signing Latency

99.99%Uptime SLA

2,500+Tests Passing

Trusted Infrastructure

SOC 2 Type IIAudit Scheduled Q3 2026

AWS Nitro EnclavesHardware-Isolated Signing

SEC 17a-4Designed-For Audit Storage

Designed For

For CTOs & Engineering Leads

Deploy sovereign infrastructure in your own AWS VPC. No vendor key custody. Full control over your signing stack.

For Traders & Bot Operators

42µs deterministic signing eliminates the Jitter Tax — latency variance that erodes alpha on every trade.

For CISOs & Compliance Teams

Zero operator access. Cryptographic attestation. Keys never leave the enclave hardware boundary.

Why most teams switch to ZeroCopy

The standard stack adds latency, counterparty risk, and engineering overhead. ZeroCopy collapses all three into a deployable product.

Status Quo

KMS, HSMs & Internal Stacks

150ms+ signing latency for AWS KMS
1.2–14ms variance for soft-HSMs
Keys reside with vendor or cloud provider
Months of engineering to get to production
Unknown failure behavior under load

The Gap

What That Costs You

Jitter Tax: missed fills, worse prices
Counterparty custody risk on every key
$300k–$800k/yr building equivalent infra
Compliance posture gaps for SEC 17a-4
No per-signature cryptographic proof

ZeroCopy

Deterministic. Isolated. Yours.

42µs p99 signing — deterministic, no variance
Keys never leave your AWS Nitro Enclave
Self-serve: < 1 hour. Guided: 2-3 weeks.
SOC 2 Type II — Examination Scheduled Q3 2026
Per-signature cryptographic attestation

See the full benchmark methodology →

Benchmark

42µs vs. 130ms

Measured under sustained 10k TPS workload, AWS us-east-1, secp256k1 ECDSA. Every bar is P99 latency.

AWS KMS~130ms

Managed service round-trip

Soft-HSM (network-attached)1.2–14ms

High variance, jitter-prone

ZeroCopy Nitro Enclave42µs

Deterministic P99, in-VPC

Methodology: All measurements are P99 latency at sustained 10,000 TPS using secp256k1 ECDSA signing on AWS us-east-1 (c6i.4xlarge). AWS KMS reflects SDK round-trip. ZeroCopy reflects in-process vsock call to the Nitro Enclave. HSM reflects network-attached soft-HSM (OpenDNSSEC baseline).

Full benchmark report Comparison table →

How It Works

Go Live in Minutes

From signup to production-grade sovereign signing. Optional architecture review. Self-serve or guided — your choice. No credit card required.

01Step

Enter Email

30 seconds. Zero friction.

Enter your email and AWS Account ID. Optional architecture review. Self-serve or guided — your choice. Your enclave starts provisioning immediately.

$curl -X POST api.zerocopy.systems/v1/enclave/provision

02Step

Deploy to Your AWS

Your VPC. Your keys. < 1 hour.

ZeroCopy deploys a secure pod inside your own AWS Nitro Enclave. Keys never leave your hardware boundary.

$zcp deploy --region us-east-1

03Step

Trade in 10 Minutes

Deterministic 42µs signing. Live.

Connect your exchange feed, configure risk guards, and start signing. P99 latency verified on first transaction.

$Output: ✓ Signing Live · P99: 42µs

Get Your Free Jitter Tax Report

Quantify the cost of latency variance on your trading strategy. Sent instantly to your inbox.

Latency Cost Calculator

Every millisecond of signing variance costs you alpha. Quantify your exposure below.

Latency Cost Calculator

Quantify how much signing latency costs your firm annually in missed alpha and jitter losses.

Asset Class

Volatility Term

Daily Volume (USD)

$100M~1,000,000 trades/day

$1M$100M$1B$2B

Current Infrastructure

Latency Comparison3095x slower

AWS KMS130.0ms

ZeroCopy42µs

3,095x faster

Estimated Annual Latency Cost

$2.5M

Estimated cost vs. $2.5M cost with AWS KMS

Physics of Variance

Latency Gap129.96ms

Volatility Mul.2.5x

Loss / Trade~$0.01

Methodology & Assumptions

The Cost Formula

Daily Loss = (V ÷ T) × L × S × σ × R

VDaily Volume (USD)

TAvg Trade Size ($100)

LLatency (microseconds)

SSlippage Coeff. ($0.0000015/µs)

σVolatility Multiplier (1x-5x)

RVulnerability Rate (2% of trades)

Key Assumptions

✓AWS KMS RTT: 150ms (Signing + Network)

✓ZeroCopy RTT: 42µs (Co-located Enclave)

✓Trading Days: 252 (equities), 365 (crypto)

✓Logic Source: ZeroCopy jitter tax model

Sources: AWS Re:Post Benchmarks, Fireblocks Perf Docs, BIS Working Paper 955.

We use a high-fidelity slippage model: (Volume / TradeSize) * Latency * Volatility.

Read the benchmark methodology →

Common Objections

The hard questions we get from security teams and CISOs.

Mathematically impossible. Your keys exist only inside AWS Nitro Enclaves — isolated compute environments with no persistent storage, no SSH access, and no operator visibility. Even ZeroCopy engineers cannot extract keys. This is enforced by hardware, not policy.

The enclave auto-recovers within seconds. Your keys are regenerated from encrypted backups stored in AWS KMS. For mission-critical deployments, we recommend running multiple enclaves across availability zones. Downtime measured in seconds, not minutes.

We measure it continuously. The zcp trace command lets you verify latency yourself. Our benchmarks are reproducible: libsecp256k1 signing takes ~35µs, VSock overhead adds ~7µs. If you measure higher, something is misconfigured — and we'll help you fix it.

Your keys remain sovereign. The enclave runs in YOUR AWS VPC, not ours. You control the Terraform, the IAM roles, and the key ceremony. If we vanish, you fork the open-source CLI and continue operating. Zero lock-in.

View all 17 frequently asked questions →

Ready to stop bleeding alpha?

Free 30-minute infrastructure review. See exactly where latency is costing you alpha.

Book a Call

42µs signing · 40+ Rust crates · 2,500+ tests