Scramjet Proxy May 2026

listen: :443
tls:
  cert: /etc/ssl/cert.pem
  key: /etc/ssl/key.pem
backends:
  - name: api
    urls: ["http://10.0.0.5:8080","http://10.0.0.6:8080"]
    pool_size: 100
routes:
  - path: /api/
    backend: api
    timeout: 15s
metrics:
  prometheus: :9090

When running applications (Sequences) within the Scramjet environment, each application runs in an isolated container with its own internal context. To make specific endpoints of these applications accessible to the outside world (via HTTP), Scramjet uses a Reverse Proxy.

This guide covers how the routing works and how to expose your applications. scramjet proxy

To understand the Scramjet Proxy, we must first appreciate the metaphor. listen: :443 tls: cert: /etc/ssl/cert

In short: A Scramjet Proxy is a lightweight, event-driven, zero-copy proxying engine optimized for hypersonic data rates and sub-millisecond latency. In short: A Scramjet Proxy is a lightweight,


| Feature | Traditional Proxy (HTTP/SOCKS5) | Scramjet Proxy | | :--- | :--- | :--- | | Latency (p99) | 5–50 ms (including software overhead) | <100 µs (microseconds) overhead | | Throughput per core | ~1–5 Gbps | ~10–40 Gbps | | Memory footprint | ~2-10 MB per 1k connections | ~200 KB per 1k connections | | Concurrent connections | 10k–50k (with tuning) | 500k–1M+ | | Encryption model | TLS termination at proxy | Optional QUIC + WireGuard in kernel | | Packet processing | Per-byte in userspace | Zero-copy, batch processing | | Best suited for | Web browsing, API gateways | Real-time data feeds, high-frequency trading, mass scraping |