AI-powered policy enforcement and deep observability for Kubernetes - built on eBPF for Linux, WFP for Windows. Zero trust from the kernel up.
Built for security and platform teams running regulated Kubernetes workloads - in financial services, healthcare, and government.
Purpose-built for modern Kubernetes - Nyx unifies kernel-level enforcement with AI-driven observability in one platform, across Linux and Windows.
See what other tools can't. Nyx records every flow in the kernel - source workload, destination, policy decision, and verdict - across Linux and Windows, the instant it happens. No sampling, no reconstructing from logs after the fact.
Describe the policy you want in plain English. Nyx compiles it into kernel-enforced rules you can read, version, and roll out - dry-run first, enforce when ready.
eBPF on Linux, a WFP callout driver on Windows Server - one policy model, real behavioural parity. No sidecars, no proxies, one DaemonSet across the cluster.
Nyx maps every flow the moment it happens - pod to pod, namespace to namespace, and out to the internet by hostname. The traffic others flatten into an opaque IP, you see for what it is.
| Timestamp | Source IP | Dest IP | Decision | Port | Enforce | Policy | Direction | Packets | Bytes | Workload / Pod | Namespace | FQDN |
|---|
Don't write queries - ask questions. Nyx turns natural language into answers over your live flow data, with charts you can pin to a dashboard in one click.
Two ways to author. Describe the policy in plain English, or click a workload, namespace, or a connection on the map - Nyx pre-fills the ingress and egress rules from traffic it has already observed. Either way you get a NyxNetworkPolicy you can review and version, then roll out dry-run → audit → enforce.
Describe what you never want to happen. Save it once, and Nyx watches every node - firing the moment a flow matches, with events ready for your SIEM.
The architecture is the differentiator - not a list of features bolted onto someone else's data plane.
Most L7 enforcement routes traffic through an Envoy proxy on every node. Nyx parses TLS SNI in the kernel - sub-microsecond, no proxy hop, one less thing to run, patch, and audit.
The same policy model enforces on Linux (eBPF) and Windows Server (WFP callout driver). Mixed clusters get one security model, not two. The only platform built for both.
Cloud services share IP ranges across thousands of tenants. Nyx enforces on the hostname - so api.stripe.com is allowed while an attacker's bucket on the same range is blocked.
One DaemonSet and one admission webhook - versus 20+ deployments for the enterprise incumbents. Less to run, less to break, less attack surface to defend.
Create a free Scout account - personal email, immediate access. No credit card.
Run the pre-filled Helm command. One DaemonSet deploys to every node - Linux and Windows alike.
Your cluster connects automatically. Open the traffic map and watch every connection light up.
Namespaces are the unit. The agent runs everywhere; you only monitor what you choose.
On every tier, Nyx sends only anonymised traffic patterns to the AI provider - never raw flow records, pod names, or IP addresses.
Compare all features →Free Scout tier. Three namespaces. No credit card.
Upgrade when you're ready.