Edge monitoring, without the fog

Your edge.
Fully in view.

EdgeWatch brings network activity, service health, security posture, private tunnels, and Plex activity into one focused command center for self-hosted infrastructure.

Local-first telemetry Hardened service design Built for operators
EdgeWatch
Live
Security postureHealthyAll core controls reporting
Public connections176 unique networks
Service health8 / 8All endpoints available
Connection intelligenceLIVE
Edge node Active peer Trusted path
ProtectionGOOD
92Risk score
  • Cloud firewall attached
  • SSH policy verified
  • No unexpected listeners
PodFlixDirect PlayLiving Room TV
WireGuardPeers healthy
ProtectionNo critical findings
LINODECADDYWIREGUARDPLEXSSHNTFYUBUNTU
One operational picture

Everything at the edge tells part of the story.

EdgeWatch connects those signals so you can move from a vague alert to useful context without bouncing between terminals, dashboards, and service pages.

Connection intelligence

See who is connected and why it matters.

Follow active and recently observed public connections with direction, process, service, port, approximate location, ISP, ASN, and correlated application context.

Chicago, United StatesCaddy · HTTPS · Active nowTrusted
Frankfurt, GermanyPlex · Direct Play · 8.4 MbpsStreaming
Ashburn, United StatesSSH · Authentication failureReview
Security posture

Turn host controls into a readable security picture.

Review UFW, cloud firewall attachment, public listeners, SSH configuration, login activity, certificates, DNS alignment, updates, AppArmor, time sync, and prioritized findings.

Service health

Know the difference between online and actually healthy.

Track services, public endpoints, private tunnel paths, TLS state, failed units, journal warnings, resource pressure, and availability from one place.

Plex visibility

Understand the stream, not just the server.

See viewer, player, source, output, bandwidth, progress, secure and relay state, plus Direct Play, Direct Stream, and transcode classification.

Operator workflow

Separate observation from administration.

Viewer and administrator experiences keep everyday monitoring clean while protecting configuration, credentials, notifications, protection policies, and audit history.

From signal to context

A connection should tell you more than an IP address.

EdgeWatch correlates low-level network observations with the services and sessions you actually care about. The result is a faster path from “something connected” to “this device is streaming through this route at this bandwidth.”

  • Active and recently observed connection views
  • Public, private, internal, and loopback separation
  • Service, process, port, direction, ISP, and ASN context
  • Plex client and session correlation when evidence is exact
Living Room RokuConfirmed Plex identity
ACTIVE
ActivityDirect Play
DirectionInbound
Bandwidth8.4 Mbps
SecureYes
NetworkResidential ISP
RouteCaddy → WireGuard
Playback progress42:18 / 1:51:02
Identity confirmed by exact client identifier match. EdgeWatch does not assert identity when the evidence is ambiguous.
Secure by design

Monitoring should not become another exposed control plane.

EdgeWatch uses explicit trust boundaries, least privilege, secret isolation, local assets, and bounded storage to reduce the monitoring system's own attack surface.

01

Split privilege model

The collector reads protected host state. The web service remains unprivileged and consumes sanitized monitoring data.

02

No collector listener

The privileged collector does not expose a network socket or accept browser input.

03

Secrets stay separate

Credentials remain in protected files and are excluded from the live browser snapshot.

04

Local-first browser

Core assets, map data, and GeoIP enrichment can stay local, without analytics or remote IP lookup calls.

i

Clear boundaries matter. EdgeWatch is a focused edge monitoring and operations platform. It does not claim to replace a SIEM, IDS, EDR, malware scanner, vulnerability platform, or external attack-surface scanner.

Purpose-built architecture

Designed for the infrastructure it observes.

EdgeWatch runs close to the edge so it can read the host, tunnel, service, and connection state that generic remote monitoring often misses.

5s

Near real-time cycle
Fast operational state and session visibility.

0

Third-party browser calls
Core dashboard assets remain local.

1

Focused command center
Network, security, services, and media context.

PUBLIC EDGEInternet trafficHTTPS · SSH · WireGuard
TRUST BOUNDARYCaddy + IdentityTLS · Authentication · Headers
READ-ONLY WEBEdgeWatch UILoopback service · Sanitized data
COLLECTORHost telemetryFixed commands · No listener
LOCAL DATARuntime snapshot + bounded historyFast live state · Durable operational context
Built for hands-on operators

For the systems you care enough to run yourself.

01

Self-hosted edge

Understand the VPS, reverse proxy, public listeners, certificates, DNS, traffic, and resources that keep your services reachable.

02

Private service paths

Follow WireGuard peer health and the private routes connecting public entry points to services behind the tunnel.

03

Media operations

Watch Plex availability, active sessions, stream methods, users, devices, bandwidth, and route context in the same operational view.

Frequently asked

The practical questions.

EdgeWatch is intentionally specific about what it observes, how it is deployed, and what it does not pretend to be.

What does EdgeWatch monitor?

EdgeWatch combines public connections, traffic, listeners, SSH activity, host and cloud firewall state, WireGuard, endpoints, TLS, DNS, services, system health, findings, notifications, and Plex activity.

Does EdgeWatch inspect packet contents?

No. EdgeWatch observes operating system, socket, service, configuration, API, and application state. It does not capture or inspect packet payloads.

Is EdgeWatch a SIEM or intrusion detection system?

No. It is a focused edge monitoring and operational security command center. It complements broader security tools rather than replacing them.

Where does the dashboard run?

The current architecture runs the web application on loopback behind Caddy and an identity layer. The collector and browser-facing service are separated by privilege and data boundaries.

Is EdgeWatch only for Plex?

No. Plex visibility is one part of a larger platform covering the public edge, private tunnels, service availability, security controls, and host operations.

Current release

Download EdgeWatch 0.5.9 R11.

The R11 upgrade package includes the current EdgeWatch command center, administration workspace, Microsoft Entra integration, protection controls, and installation validation.

Release0.5.9 R11 PackageLinux tar.gz DownloadsLoading
SHA-256 3baac44e...ede4954 View checksum
Download R11 The counter records download starts, not personal information.
Contact EdgeWatch

Questions, ideas, or product feedback?

Send a message through the secure form. The destination address stays in private server configuration and is never exposed in the website source.

No public email address Rate-limited submissions Direct reply to your inbox