ASM is not dead. Performance is not optional. Security is not a feature.

Infrastructure software written in Rust — SIMD hot paths, AF/XDP kernel-bypass, and single static binaries. Every performance claim is measured at the NIC hardware counters, never asserted.

Rust · SIMD · AF_XDPDrop-in compatibleAGPL-3.0 + Commercial

The products

Runbound

A drop-in Unbound replacement: DNS server with an AF_XDP fast path, DNSSEC validation, a REST API, and a web dashboard.

Not yet public

RunAlexDB

A MariaDB/MySQL-wire-compatible SQL engine: in-memory-first storage, AVX2/SIMD row processing, WAL durability, and Raft-based replication.

Other projects

Earlier-stage server products and the benchmark tools used to measure everything above — source on GitHub, no dedicated page yet.

RunNginxHTTP servernginx-compatible — SIMD parser, AF/XDP, io_uring, built-in SSH/SFTP, dashboard.
RunX540Proxmox NICNative XDP for Proxmox VM guests on the stock vmxnet3 — no SR-IOV, no passthrough.
dnsmarkDNS benchmarkAF_XDP line-rate generation, wire-validated latency, compare mode, JSON output.
RunPerfNetwork benchmarkiperf3-style, scales per-CPU, AF_XDP datapath, match-the-model-to-the-metric.
httpmarkHTTP benchmarkHTTP/HTTPS, QPS control, HTTP/2, compare mode, JSON output.
dbmarkSQL benchmarkMySQL wire protocol, latency percentiles, compare mode.

Engineering principles

Measured, not asserted

Throughput is read at the NIC counters (ethtool -S), latency is validated against a wire capture. Reports are reproducible, with baselines included.

Down to the metal

SIMD dispatch at startup (AVX2 → SSE2 → scalar), AF/XDP kernel-bypass where the NIC supports it, lockless hot paths.

Drop-in

Existing unbound.conf / nginx.conf configuration works as-is. Migrate by dropping in a single static binary.

Structured security

Every release goes through a structured audit cycle. Signed releases (minisign), published checksums, honest finding tracking.

Status

The server projects are under active development and have not yet undergone an external human security audit. Benchmarks are reproducible and rig-specific — the numbers are a function of the hardware, recorded in each report, not asserted as universal claims. Not recommended for production handling sensitive traffic until v1.0.

About

RunASM is built and maintained by a single developer. No stock photos, no "our team" page pretending otherwise — just the software, the source, and the numbers behind it.