Free beta · 90 days · every feature

See your whole network.
Touch nothing.

Sentry Lens finds every device on your network, draws the map, shows who talks to what and watches your servers and applications. It does it by listening only: it never signs in to your firewall and never keeps an admin password.

  • Self-hostedYour data stays on your server
  • 10 minutesFrom an empty server to the first devices
  • Docker, Linux, WindowsOne installer each
Sentry Lens · Home
142devices
11servers up
38applications
2alerts
nas-01Storage · 6.2 TB free
pve-2Hypervisor · 14 guests
printer-2fToner low · 4%
office-ap-3Access point · 23 clients
Illustration with example data.

Everything on your network, in one place

Built for small offices, IT consultants and home labs that want Auvik-style visibility on their own hardware. The pictures below use example data.

Devices and the map

Every device, and where it plugs in

Found by sweeps, flows, ARP and DHCP, and named by what each device says about itself. Switches that answer SNMP place every device on its port, so the map draws itself.

  • New devices flagged the moment they appear
  • Vendor, addresses, open ports and history for each one
  • Tags to group devices and give them logins
Network · Map
firewall core-switch ap-office nas-01 pve-2 ap-lobby laptop-7 phone-ana vm-web vm-db new: tv-4 port 12port 3

Traffic and applications

Who talks to what, and how much

Internet and LAN traffic, live throughput and every flow, with drill-down from any chart to the device and the conversation. The traffic sensor names the application behind each flow.

  • NetFlow, IPFIX and sFlow from your firewall
  • Applications named from a copy of the traffic
  • Any chart opens the flows behind it
Network · Traffic · last 24 h
InternetLANPeak 412 Mb/s
Microsoft 36538 GB
YouTube29 GB
Zoom18 GB
Backups (SMB)15 GB
Windows Update7.4 GB

Websites and countries

Which device looked up which website

Every lookup the sensor sees, with the site's category. See the countries your traffic goes to, and whether anything got through from a country on your block list.

  • Categories for millions of domains
  • Per-device history of what it reached
  • Countries by traffic, blocked or not
Network · Websites
WebsiteCategoryDevices
outlook.office.comBusiness34
www.youtube.comVideo21
github.comDevelopment9
cdn.ads-track.exampleAds & tracking17
steamcontent.comGames3
Canada
United States
Netherlands
Germany
Blocked listnothing got through

Servers and infrastructure

Health of every machine, with nothing to install

CPU, memory, disks, uptime and failed services for Linux and Windows machines, Proxmox hosts and their guests, and Docker containers. Ink, toner, UPS battery and PoE by SNMP.

  • Read-only accounts, made with one line
  • 90 days of history
  • Update or restart a container from the page
Infrastructure · Servers

pve-2 Proxmox · 14 guests

CPU38%
Memory71%
Disk54%

nas-01 Linux · up 41 days

CPU12%
Memory46%
Disk91%

app-01 Windows Server · 6 containers

web api db worker cache proxy

Applications and uptime

Know before your users do

Watch websites, ports, certificates and services from the server, or from a small probe somewhere else. Share a public status page if you want one.

  • HTTP, TCP, ping, DNS and push checks
  • Response times and 90 days of uptime
  • Alerts to email, Teams, Slack, Discord, Telegram, ntfy
Applications
Company website99.98%
Mail (SMTP)100%
ERP99.71%
VPN gateway100%
Backup push99.89%
Response time, company website avg 182 ms

IP addresses and alerts

Addresses in order, problems in front

Subnets, how full each one is, and whether a DHCP scope is about to run out. Alerts for a server down, a full disk, a failed service, a new device or traffic to a blacklisted address.

  • Address use per subnet, at a glance
  • Security checks on what the traffic shows
  • Quiet when it's the collector, not the network
Network · IP addresses · Alerts
10.10.0.0/24 office
168 of 254 used · DHCP 92% full
Disk almost fullnas-01 · /volume1 at 91%4 min ago
New devicetv-4 · on ap-lobby12 min ago
DHCP scope almost fulloffice · 8 addresses left1 h ago
Back upERP · down 3 min3 h ago

How it works

Your network already says almost everything. Sentry Lens listens to it, in four ways.

How data reaches Sentry Lens Firewalls and routers send flows; a switch mirror port or the hypervisors send a copy of the traffic to the sensor; collectors sweep the networks and read devices with read-only logins; all of it lands in Sentry Lens on your server. Firewall or routerNetFlow, IPFIX or sFlow Switch mirror portA copy of the traffic HypervisorsProxmox, Hyper-V, vCenter: one line CollectorsSweeps, SNMP, read-only logins flowdstores every flow Traffic sensorapplications, DNS, DHCP Sentry Lenson your server: Docker,Linux or Windows
  1. Install it on a small server or VM on your network: one line with your key, about 10 minutes.
  2. Say which networks are yours on the setup page. Its own collector starts sweeping them: devices appear within minutes.
  3. Point your firewall's flows at it, and give the sensor a copy of the traffic: a mirror port, or one line on each hypervisor.
  4. Run one line on each server you want to watch: it makes a read-only account. Your admin login never reaches Sentry Lens.

It only listens

A monitoring tool that holds the keys to everything is the worst thing you could lose. So Sentry Lens holds none.

  • No firewall login, ever. Your firewall sends flows; Sentry Lens never signs in to it or changes it.
  • No admin password stored. Servers are read with read-only accounts you make with one line. That line runs with your login on your machine; the login itself is never sent.
  • Collectors only talk out. Each has its own key and opens no port.
  • Your data stays home. Flows, devices and history live in the database on your server. The daily license check sends only this install's ID, version and device count.
  • Sign-in your way. Local accounts, Google, Microsoft, GitHub or any OIDC provider, with admin approval for new people.

Runs where you already are

The same Sentry Lens, three ways to install it. No build, no compiler: the installer brings everything.

Docker

Any Linux server with Docker Engine and Compose. One line pulls the images and starts everything, your key included.

2 cores · 4 GB · 40 GB minimum

Linux services

No Docker needed: a self-contained package that runs as system services, with its own database. Tested on Ubuntu.

2 cores · 4 GB · 40 GB minimum

Windows services

Windows Server 2016+ or Windows 10/11. Runs as Windows services; its database runs in a small hidden WSL system, or on another machine.

4 cores · 8 GB · virtualization on

Works with any firewall or router that exports NetFlow v9, IPFIX or sFlow, and with Proxmox, Hyper-V, vCenter and ESXi for the traffic copies. Older CPUs without AVX2 are handled automatically.

Plans

The beta is free and has everything. Paid plans and their prices come at launch; beta testers hear first.

Beta

Free

  • 90 days, renewable
  • 1 install
  • Up to 500 devices
  • Every feature
Get a beta key

Starter

At launch

  • 1 install
  • Up to 100 devices
  • Devices, map, servers, uptime
  • Status page

Standard

At launch

  • 2 installs
  • Up to 1,000 devices
  • + Traffic sensor
  • + Collectors at other sites

Pro

At launch

  • 10 installs
  • Up to 10,000 devices
  • Everything
  • + Prometheus history

Get a beta key

Tell us a little about your network. We send you a key, free for 90 days, with the install line for Docker, Linux or Windows.

  • No credit card
  • Every feature, up to 500 devices
  • Your feedback shapes what comes next

Questions

Does my network data leave my server?

No. Sentry Lens runs on your server and keeps its data in its own database there. The only thing it sends out is the daily license check: this install's ID, its version, its name and how many devices it sees.

What if it can't reach the license server?

It keeps working for 14 days after its last successful check, then the settings become read-only until it checks in again. Collection never stops.

What happens when the beta ends?

Ask for a renewal, or move to a paid plan at launch. Without a valid key Sentry Lens keeps collecting, but its settings are locked until a key is entered.

Do I need a managed switch or a special firewall?

No. Devices are found by sweeping the network. Flows from your firewall, a mirror port or a hypervisor add the traffic views, and SNMP on switches adds the map's ports; each is optional.

Which systems can it read?

Linux over SSH, Windows by WMI over WinRM, Proxmox by its API, and anything that answers SNMP: switches, access points, printers, UPSs, NAS boxes.

Can I watch several sites?

Yes. Put a small collector at each site: it only talks out to your Sentry Lens, so no port needs opening there.