Architecture First
We start with the packet path—not feature lists or buzzwords.
Built for engineers who demand more than plugins. No buzzwords. No black boxes. Just architecture, performance, and control.
We start with the packet path—not feature lists or buzzwords.
Throughput and latency are design constraints, never afterthoughts.
How it works, what it inspects, and where it fails is fully documented.
Why We Exist
Open-source firewalls are powerful, but bolted-on security features often trade performance for visibility. We built a security engine that integrates with the packet path instead of fighting it.
Meet the team behind Zedmos →Inline capabilities
Every control runs inside the same inspection pipeline—no bolted-on daemons, no policy gaps, no extra hops.
Decrypts HTTPS, SMTPS, FTPS, and other TLS flows inline so malware and exfiltration attempts are caught where they start.
Identifies thousands of applications (BitTorrent, WhatsApp, Tor, YouTube) regardless of port using nDPI.
Blocks malicious domains, botnet C2s, and phishing sites instantly with feeds from USOM, URLhaus, OpenPhish, and ThreatFox.
Scans HTTP/S, FTP, SMTP, and SMB transfers with ClamAV before payloads land, keeping endpoints clean.
Enforces URL and DNS policies, including DoH/DoQ controls, so acceptable use policies stick.
Applies policy per user, device type, or geography and isolates compromised assets automatically.
Architecture Overview
This is not a feature collection; it is a security engine. Packets enter via netmap, stay in shared memory through DPI + TLS analysis, and exit only after synchronous policy evaluation. Storage and control-plane hooks are fed via writerd, not by bolting on scripts.
Zero-copy RX/TX rings, per-queue workers, takeover-aware interfaces.
nDPI classification, TCP reassembly, JA3/JA4 fingerprints, TLS MITM.
Suffix tries, TI cache, identity selectors, synchronous enforcement.
Allow/block, tls_bump/bypass, shadow/quarantine, StartTLS handling.
Writer daemon → SQLite/Elastic/Mongo via zero-copy ring & batching.
UNIX socket RPC, hot reload worker, metrics/export knobs.
Architecture is the product. Traffic never leaves this pipeline.
Performance Is a Feature
Real security maintains throughput, keeps latency predictable, and avoids CPU thrash even when inspection is fully enabled.
Comparison
Plugin chains chase features after traffic leaves the NIC. Zedmos stays inline—from netmap capture through policy runtime—so latency, CPU, and telemetry stay deterministic.
| Dimension | Plugin stack | Zedmos engine |
|---|---|---|
| Model | Security plugin chain | Zedmos inline engine |
| Architecture focus | Feature backlog & UI | Packet-path & determinism |
| Inspection path | Add-on detour after routing | Integrated netmap → policy |
| Performance priority | Shared CPU budget | Primary design goal (line-rate) |
| Policy execution | Per-plugin hooks | Single runtime w/ suffix tries |
| Telemetry | Syslog/export scripts | Writerd log plane (SQLite / ES / Mongo) |