Scramjet Proxy !!install!! -

Client → [NIC] → Scramjet Engine → [Modify/Inspect] → [NIC] → Server │ │ └─── State Table ────────┘

Scramjet uses a concept called to handle HTTP routing. When you start a Sequence (an instance), you can assign it a specific HTTP "Topic" (or path). scramjet proxy

To achieve maximum RPM (Requests Per Minute) with a Scramjet Proxy: Client → [NIC] → Scramjet Engine → [Modify/Inspect]

| Feature | Traditional Proxy (HTTP/SOCKS5) | Scramjet Proxy | | :--- | :--- | :--- | | | 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 | API gateways | Real-time data feeds

const proxy = new Proxy( port: 8080, upstream: 'https://api.example.com' );