Proxy & Gateway
Virtual hosts, prefix and header routing, reverse proxying, load balancing, health probes and circuit breaking.
Toron is an event-driven, high-performance web server, reverse proxy, API gateway and edge security engine—built from the ground up in Go.
Toron brings traffic management, protocol termination, security enforcement and service connectivity into the same gateway.
Virtual hosts, prefix and header routing, reverse proxying, load balancing, health probes and circuit breaking.
HTTP/1.1, h2c, HTTP/3 over QUIC, WebSockets, gRPC and native L4 TCP/UDP forwarding.
Event-driven concurrency, pooled buffers, bounded work, streaming responses and explicit connection deadlines.
TLS 1.2/1.3, development certificates, ACME issuance and renewal for production deployments.
Native Kubernetes Ingress and lightweight sidecar mode for pod-to-pod mTLS and weighted traffic splitting.
Transcode JSON REST calls into binary gRPC requests with bounded bodies and protocol-safe header handling.
Toron separates server infrastructure from application routes, keeping operational tuning and service topology independently readable.
routes: - type: "upstream" host: "api.example.com" prefix: "/v1" algorithm: "round_robin" health_check_path: "/health" targets: - "http://api-1:8080" - "http://api-2:8080" rate_limit: "100/min" waf: enabled: true mode: "enforce"
Protection is not a separate appliance in the Toron model. It sits directly in the request path, alongside routing and transport controls.
Toron includes a Docker-based comparison harness for Toron, NGINX, Traefik, Caddy and HAProxy, using the same backend services and collecting throughput, tail latency, CPU and memory telemetry.
Actual throughput against a 5,000 RPS target at 100 concurrent connections.
Median latency (p50) in the recorded 5-second quick run.
p99 latency in the same recorded run; p99.9 was 2.677 ms.
13.8 cycles/sec with 0.0% reported GC CPU overhead and 1 MB peak live heap.
Source:
benchmarks/results/benchmark_c100_r5000.json and `.raw.txt`. This particular run used a 0%
adversarial-injection ratio; the security figures are therefore not presented as attack-traffic results.
✓ indicates a documented capability in the respective product family; * indicates capability may depend on edition, plugin/module, configuration, or external integration. The matrix is intentionally descriptive, not a vendor ranking.
Use the same gateway for a simple application, a container estate, Kubernetes ingress, or pod-local service traffic.
Build and run Toron directly on Linux, macOS or Windows.
Discover services from Docker and Podman using Toron labels.
Operate as a native networking.k8s.io/v1 Ingress controller.
Run alongside workloads for mTLS, canaries and pod-level traffic control.
Toron exposes a built-in management surface, Prometheus metrics, structured audit logs and W3C trace context propagation for distributed systems.
$ git clone https://github.com/SayantanSaha/toron $ cd toron_v3 $ go run ./cmd/toron [TORON] Loaded configuration from config.yaml [TORON] Routes loaded from routes.yaml [TORON] Server listening on :8080 $ curl http://localhost:8080/health {"status":"ok"}
For architecture discussions, security review, benchmarking collaboration, enterprise deployment questions or commercial licensing, get in touch directly.
Project author and maintainer
sayantan.somu@gmail.comOne Go binary. Declarative routing. Security controls. Modern protocols. A gateway that can grow with the system behind it.