Divy reads the ingress documentation of four platforms and concludes that the interesting question is not which layer each one picked but how much of the reasoning each one publishes. E2B and Daytona both run host-based L7 routing and differ mainly in how they resolve where a sandbox currently lives. Fly Sprites get no sandbox-specific path at all: anycast, WireGuard and a gossip catalog that already carried every other workload on the platform. He is precise about the scope of our own numbers, keeping the throughput won by dropping a redundant L7 hop separate from the roughly 20 percent that kernel TLS and splice added on top, and noting that a single-connection loopback transfer says nothing about a short handshake-bound tool call. The note we appreciated most is that our forwarder refuses to start when the kernel cannot attach the TLS module, instead of quietly falling back.
We didn’t write this one — it’s Divy Yadav’s piece, published on Towards AI. The note above is ours; the full article is theirs.