Nothing goes unseen.

Vardex keeps a constant sonar sweep over your network — naming every device on it and telling you, in plain language, the moment something looks wrong. Built for people who run their own network and don't have a SOC on call.

No cloud dependency for detection. Captured packet content never leaves your machine.
Linux (Ubuntu, Debian): in development.
The Watch — Scanning
11 detections · packet content stays on this machine
Capture
Live
Classify
11
Enrich
2
Log
All
Review
You
Resolve
Manual

Everything you'd see on a Tuesday night.

A quiet interface until it isn't. Click through what each screen actually shows — recreated from the real app.

Dashboard

Every category of trouble, counted live, since the app started watching. (Example numbers.)

0
Blocked
22
Port scan
13
SQLi
19
DNS tunnel
1
Brute force
0
Anomaly

Threat detail

Click any event and Vardex explains exactly why it was flagged — then lets you block it on the spot.

SQL Injection Critical
Source203.0.113.42 · example
Pattern matchedUNION SELECT tautology
AbuseIPDB confidence92%
ActionBlock available

Devices

MAC addresses don't change when DHCP hands out a new IP — so neither does Vardex's memory of who's on your network. Your own computer is marked, and a device with a randomised address says so instead of guessing. (Example devices.)

LAPTOP-7SRJBK9J
192.168.1.106 · AzureWave Technology Inc.
Kitchen speaker
192.168.1.114 · Sonos, Inc.

Geo map

Where an alert's address is located, from the free GeoLite2 database you install yourself. Nearby alerts share one marker, and addresses on your own network are never drawn. (Example places.)

AI incident report

One click turns a night of raw events into a plain-English summary — using your own Anthropic key, never ours.

"Between 01:16–01:31, 203.0.113.42 attempted 9 SQL injection payloads against your exposed web service, escalating from tautology checks to UNION-based extraction. AbuseIPDB lists this address at 92% confidence. Recommended: block the source and review logs for the targeted endpoint."

Every way in, one watch kept over all of them.

Every detection is entered under its own instrument — nothing lumped into a generic "alert."

Brute force & SYN floods

Rate-based detection on login and connection attempts before they succeed.

Port scans

Both loud and stealth scans, TCP and UDP, across your exposed surface.

SQL injection

Spots injection text in plain HTTP requests, including forms disguised with URL encoding.

DNS tunneling

Catches exfiltration hiding inside what looks like ordinary DNS traffic.

Data exfiltration

Flags abnormally large outbound transfers before they finish.

ML anomaly detection

An Isolation Forest model learns your network's normal — and flags what isn't.

C2 beaconing

Regular, quiet check-ins that look nothing like a person clicking around.

ICMP floods & ping sweeps

A flood of pings, or a sweep asking every address whether anything is alive.

Suspicious ports

New connections to ports that backdoors and anonymising tools favour.

Connection Intelligence — new in 5.3

Which program made each connection, whether its code signature checks out, and the server name it contacted. Catches a program wearing a trusted name from the wrong place, and unsigned programs connecting out. Encrypted content is never read.

New device alerts

Know the moment something joins your network — by MAC, not just IP.

Real enforcement

Block an IP straight from the detail card. A real Windows Firewall rule, not just a log line (run Vardex as Administrator to use it).

Agent & bot honeytoken — optional

A fake internal endpoint no person would ever find. Anything that crawls and calls it is an automated agent, not a visitor — caught without waiting on a pattern to match.

Nothing about this needs to trust the cloud.

A network monitor that phones home is a strange thing to trust. Vardex doesn't.

Detection runs entirely on your machine

Packet capture, analysis, and storage happen locally. Nothing about your traffic is uploaded for Vardex to work.

Secrets encrypted at rest

API keys and credentials are protected with Windows DPAPI, tied to your own Windows login.

You bring your own third-party keys

AbuseIPDB, GreyNoise, and Anthropic integrations are optional and use your own free-tier accounts — never a proxy run by us.

Manual, human-reviewed blocking

Vardex never blocks anything on its own judgement. You see the evidence, you decide, you click Block.

Open about its open source

Every third-party component and its license is listed in full — no obscured dependencies.

Honest about its limits

Vardex never reads encrypted content, does not detect bare-ACK scans, and can miss traffic on very busy networks. The known limits are written down, not buried.

Built for networks you own

Vardex is for monitoring what's yours — your home, your own business network — clearly, not quietly.

Test strip — what happens if you continue
STATUS: Not yet available for download.
Nothing will be charged, installed, or activated today.

Put a watch-light on your network.

One licence key activates one machine at a time. Vardex isn't available to download just yet; read the user guide in the meantime.

Windows 10 or 11, 64-bit · Npcap for packet capture (separate download, own licence) · Linux (Ubuntu, Debian) is in development