Overseer

System requirements

What each platform needs, and what Overseer can honestly do there today. Where an operating system cannot ask before a connection, we say so instead of faking it.

Windows dev build
Metadata only
No TLS interception

Overview Download Requirements What is sent Docs

Development build - not for sale

There is no signed installer, no macOS or Linux client, and nothing that can hold a connection open while it asks you. Everything here describes what exists today, not what is planned.

Per platform

Windows

Monitor only

Windows 11 23H2 or later, x64

Needs

Administrator approval, for elevated capture and for Overseer's own firewall rules
Microsoft Edge WebView2 runtime, already present on current Windows 11
About 200 MB of disk for the app and its local history

Can do today

Name the process behind each TCP and UDP flow, IPv4 and IPv6
Fingerprint executables with SHA-256 and check Authenticode signatures
Read per-flow byte counts and DNS answers through ETW when elevated
Score flows with stable reason codes and write local allow and block rules
Enforce blocks as named Windows Firewall rules, removable in one action

Cannot do today

Hold a connection while it asks you. That needs a Microsoft-signed filtering driver that has not been built, so a block takes effect from the next attempt.
Guarantee attribution for very short-lived flows, because identity is correlated after the fact rather than supplied by the filter.
Report itself as fully protected. It reports Monitor only, which is the truthful state.

macOS

Not implemented

macOS 13 or later, Apple silicon or Intel

Needs

An approved Network Extension content filter, Developer ID signing and notarization

Cannot do today

Everything. No macOS client exists in the repository yet.

Linux

Not implemented

Ubuntu 22.04 or 24.04, Debian 12, Fedora 40 or later, kernel 6.1+

Needs

cgroup v2, BTF for CO-RE eBPF, nftables with Netfilter queue support, systemd

Cannot do today

Everything. No Linux client exists in the repository yet.

What the app reports

Overseer never shows a generic green “Protected” while a required piece is missing. Every installation reports exactly one of these:

Full protection

Attribution, capture, rules, interactive hold and cloud lookups are all healthy.

Local protection

Everything local works; cloud services are offline or turned off.

Monitor only

Overseer sees traffic but the enforcement component is missing or unapproved.

Limited visibility

A platform prerequisite is missing, so some traffic cannot be attributed.

Paused

Enforcement is paused until a named time. What is still monitored is stated separately.

Action required

A driver, extension, entitlement or credential needs your attention.

Error safe mode

Something failed. Known rules were kept where safe, but full enforcement is not promised.

Account

A Defynta account on Silver or any higher plan.
Up to five active installations per account. You can revoke one during activation.
A normal browser for activation. Overseer never embeds the website or a payment form.
Outbound HTTPS for activation and plan checks. Monitoring, rules and history keep working without it.