xin

Friends don't let friends C the socket

Bring your config.
Serve faster and safer.

Performance

Serve faster.

21% more requests per second over TLS, at 0.70× the CPU each.

+21% TLS throughput
Safety

Serve safer.

Written in Rust. The bug class behind 40 of the 62 advisories in nginx's own list cannot be written here.

40 memory CVEs designed out
Compatibility

Change nothing.

Bring the config you already run. Same directives, same precedence, same edge cases.

0 config changes
Reach

Run anywhere.

Signed apt and rpm packages across seven architectures, from Raspberry Pi to IBM Z.

7 architectures
curl -fsSL https://xinproxy.com/install.sh | sh

Enrols the signed apt or rpm repository, installs, and reads your existing config. Starts nothing on its own. Read the script · Getting started

xin is an HTTP web server, reverse proxy, load balancer and Kubernetes Gateway controller, written in Rust. It reads the configuration format you already use, and ships as one static binary with no module ABI to patch.

Why xin

Five reasons, and the evidence for each.

Ease of use

One command, then your own config

Install with a single line. Point it at the config file you already have — no converter, no migration project, no new language to learn.

Platform compatibility

Seven architectures, two package feeds

Signed apt and rpm repositories covering amd64, arm64, i686, ARMv6/v7, ppc64le and s390x — verified back to CentOS 7 and Debian 8. Static musl builds for Alpine and distroless.

Performance

Faster on TLS, parity elsewhere

21% more TLS requests per second on 30% less CPU each, measured against nginx 1.26.3 on pinned cores. Cleartext and static serving hold parity.

Safety

A parser that cannot overflow

The HTTP engine, config engine and resolver contain no unsafe code, enforced by the compiler. Buffer overflows and use-after-frees are not bugs you can write here.

Enterprise support

Commercial licences, direct engineering

Free for non-commercial use. Running it in production at a company? We offer commercial licensing and support straight from the people who wrote it.

Performance

Measured head to head.

Against nginx 1.26.3 on the same machine: physical cores pinned, three interleaved rounds, counterbalanced order. Each panel has its own scale — the four workloads span 632 to 367,961 per second.

TLS 1.2, keepalive +21%
requests/sec
246,011
202,781
CPU per request — xin 10.3µs · nginx 14.7µs
TLS 1.2, full handshake +17%
connections/sec
632
542
Cleartext, return 200 −1.5%
requests/sec
367,961
373,518
CPU per request — xin 7.7µs · nginx 7.9µs
Static file, 1 MiB −0.4%
requests/sec
9,745
9,789
CPU per request — xin 140µs · nginx 127µs

Safety

40 of 62 advisories are memory-safety bugs.

That is nginx's own published list: buffer overflows, use-after-frees, memory disclosure — seventeen years of them, still arriving in 2026. It is the defect class Rust removes as a category, and the reason xin exists.

See all 62 advisories How xin avoids them

40 of 62

nginx security advisories that are memory-safety defects

Enterprise

Commercial licensing & support.

xin is free for non-commercial use. If you are running it in production at a company, we offer commercial licences and direct engineering support from the people who wrote it.

Bring your config.

curl -fsSL https://xinproxy.com/install.sh | sh