Scramjet Proxy -

As we move toward edge computing, the "heavy" proxies of yesterday don't always fit. Scramjet’s modular nature makes it ideal for deployment at the edge. Whether you are running it in a Docker container on a cloud instance or a lightweight binary on a Raspberry Pi, it scales down just as well as it scales up.

| Feature | Scramjet Proxy | Envoy | HAProxy | Squid | |--------------------------|----------------|-------|---------|-------| | Stream-level transforms | ✅ (native) | ✅ (Wasm) | ❌ | ❌ | | Lightweight (<50 MB) | ✅ | ❌ | ✅ | ✅ | | JavaScript programmable | ✅ | ❌ | ❌ | ❌ | | Clustering / Hub | ✅ | ✅ | ✅ | ❌ | | WebSocket support | ✅ | ✅ | ✅ | ✅ |

One of the biggest pain points with popular reverse proxies (like Nginx or HAProxy) is configuration complexity and resource bloat when handling thousands of concurrent connections. scramjet proxy

Scramjet Proxy is lightweight. Because it is designed specifically for high-velocity data transit, it strips away much of the "bloat" found in general-purpose web servers. The result? Higher throughput with a smaller memory footprint.

Unlike a traditional proxy (which terminates connections), a Scramjet Proxy operates inline at the transport or application layer with minimal buffering. It: As we move toward edge computing, the "heavy"

The name evokes a scramjet engine: air (traffic) flows through at supersonic speed while being compressed, modified, and expelled – no stopping.

Once the instance is running, you must tell the Hub/Proxy to route traffic to it. You do this by setting a Topic for the instance. One of the biggest pain points with popular

Using the Scramjet CLI (si):

# Syntax: si topic set <instance-id> <topic-path>
si topic set instance-abc-123 my-public-api

Create proxies.txt with one proxy per line (format: http://user:pass@ip:port).