Portus 0.2.3, a new Rust-based gateway for API, AI, and MCP traffic, has landed on Hacker News with a claim that should make any infrastructure engineer stop scrolling: full conformance with the Kubernetes Gateway API v1.6.2 specification. The project reports passing 130 out of 130 conformance tests without a single skip, a rarity in the ecosystem where many gateways leave experimental or edge-case features on the table. Built on the Rama networking stack, Portus positions itself as a unified data plane for Kubernetes routes, LLM providers, and MCP tool servers, all running within a single Rust process.

Performance Benchmarks Against Existing Stacks

The project’s documentation details a head-to-head comparison against agentgateway v1.5.0 using the open gateway-api-bench methodology. On a 10-vCPU Linux VM running on an Apple M4, Portus achieved a p99 latency of 0.35ms at a fixed 30,000 requests per second, compared to agentgateway’s 0.82ms. Memory usage was also significantly lower, with Portus peaking at 131Mi versus agentgateway’s 383–456 Mi. The benchmarks also highlighted resilience: when one of four backends went dark, Portus recorded a 0.025% error rate, while agentgateway hit 2.0%. The team notes that these numbers are medians from three interleaved rounds and are only comparable within the same machine context.

Why They Dropped Pingora for Rama

A key architectural decision was moving from Cloudflare’s Pingora framework to Rama. The Portus team ran the same gateway on both engines on identical hardware and found that Rama was faster on every payload rung while using 2 to 2.6 times less memory. This switch became the default in version 0.2.4. The core logic remains stack-independent, allowing the team to swap networking layers without rewriting routing or policy logic. The data plane receives configuration via mTLS gRPC streams, ensuring atomic swaps that never drop connections, while the control plane compiles CRDs directly into protobuf messages rather than using an intermediate config language.

Key Takeaways

  • Portus achieves 130/130 conformance on Gateway API v1.6.2, covering HTTPRoute, TCPRoute, UDPRoute, and experimental features like ListenerSet.
  • The project supports both Kubernetes-native deployment and standalone YAML configuration for simple reverse proxy use cases.
  • Switching from Pingora to Rama resulted in a 2-2.6x reduction in memory usage and higher throughput across all tested payload sizes.
  • The architecture separates the control plane (controller/ledger) from the data plane, ensuring no external service lookups occur on the request hot path.

The Bottom Line

Portus is a serious contender for teams frustrated by the bloat of traditional gateways, offering a rare combination of strict conformance and Rust-native efficiency. If the performance numbers hold up in production, this could be the new standard for high-throughput, low-latency Kubernetes ingress.