Zero-copy applications
The future of I/O is here.
Less memory. Lower latency. Post-quantum by default.
DApps were 2020. Cloud apps were 2010. ZApps are now.
Why ZApps
Three reasons to build different.
Less memory
Pointer + arena.
Zero-copy parse: messages live in L1 cache where Protobuf forces a heap round-trip. O(1) field access. No marshal/unmarshal allocations.
Lower latency
Tail to floor.
Cap'n Proto–derived wire + per-stream FEC + post-quantum KEM amortized. Tail latency converges to link latency. p99 disappears.
Future-proof
PQ by default.
X-Wing and Z-Wing hybrid post-quantum from byte zero. Harvest-now-decrypt-later? Nothing useful to harvest. Mutual auth at the wire.
ZApps in the wild
What you can build.
AI agent meshes
Mutual auth, non-repudiation, signed provenance per call. MCP / A2A / ACP over ZAP.
Real-time markets
Sub-microsecond p99 for FIX 4.4 / 5.0 trading channels. Compliance-grade timestamps.
Sovereign rollups
L1/L2 nodes talking PQ-safe across the public internet. No TLS supply chain.
Edge inference
Tiny binaries, mmap-friendly messages, no JSON marshal at the inference boundary.
Service mesh
ZAP-RNS for naming, zap-http for RPC, zap-ws for streaming. One wire end-to-end.
Sensor fanout
Multi-stream pubsub with FEC for lossy networks. p99 independent of stream count.
Ready?
One protocol. Many sub-protocols. All composable.