Free while we’re in preview

Get TrafficPilot

A local proxy that counts, per site, exactly how many bytes crossed the wire.

The Mac button is for Apple Silicon. On an older Intel Mac, get this one instead.

One file, both ways. Double-click it for the window. Run the same file from a command prompt with arguments and it behaves as the command-line tool, because the engine is inside it. Nothing else to download and nothing to keep beside it.

Early preview. The window has been built and run, but not yet on a real Windows PC or Mac, so expect rough edges. The engine underneath it is fully tested.

One file — no installer
Reaches only what you point it at
Source code published below

Free while in preview. It isn’t signed yet, so Windows or macOS will ask you to confirm the first time you open it. At launch, TrafficPilot is included in every plan along with the rest of the range.

Counted on the socket

Run trafficpilot proxy --listen 127.0.0.1:8080 --log traffic.jsonl, point a program’s proxy setting at it, and every request that program makes gets measured: host, bytes out, bytes in, duration. trafficpilot report turns the log into per-host totals and each host’s share of the bandwidth. trafficpilot watch tails it live while it happens.

The bytes are counted on the upstream socket itself, not read off a Content-Length header. Transparent decompression and connection reuse are both switched off, so a gzipped response is measured compressed, the way it was billed to you.

No certificate goes into your trust store

An https:// request arrives as CONNECT. TrafficPilot opens a TCP connection and copies bytes both ways without looking inside. You get the hostname, the byte counts and the duration. No path, no header, no body, and the log says “tunnelled, not decrypted” rather than inventing a path field. Tools that show you inside your own HTTPS do it by making your machine trust a CA they run. This one never asks you for that.

Absence is not evidence

It sees a program’s traffic only if that program was configured to use it. Not a packet capture, not a firewall. Something with its own DNS-over-HTTPS, or a non-HTTP protocol, simply won’t appear in the report.

Reading on the job itself

How to find out what is using your bandwidth Meter per host, not per application. "The browser used 40 GB" is not useful; "40 GB went to one video host"...

The rest of Network Control Center

Why the network feels slow. Which doors are open, which links keep dropping, what is using the connection, and which office is the problem.

NetLens

Simple Ready

Port scanning and latency checks for one host, with no admin rights needed.

LinkGuard

Vertical Ready

Probe the link every 30 seconds for a month, then write four lines about it.

RouteWatch

Team Ready

Six offices, ten targets, one grid that names whose network is at fault.

Advanced & technical details Command-line builds, source code, checksums and a recorded session — for developers and IT teams

A working command-line build of the metering proxy: an HTTP forward proxy that counts bytes per host on the upstream socket, an allow and block list, and a report that totals traffic by site. HTTPS is tunnelled through CONNECT and never decrypted — no root certificate is installed and no page content is recorded, only the host and the byte counts. It sees only programs configured to use it.

Naming status

Working name only — brand verdict **RENAME** (High). Collision: TrafficPilot. Rename before launch.

What it draws on

Existing paid software whose best ideas shaped this program: GlassWire Premium, NetLimiter, PingPlotter Professional, NetWorx.

Command line

There is nothing extra to install. The program you download is the command-line tool as well: give it arguments instead of double-clicking it and it runs as one, with its output on your terminal. The standalone builds below are the same engine on its own, for machines where you would rather not ship a window at all.

trafficpilot 1.0.0 - a local HTTP proxy that meters traffic per host

USAGE
    trafficpilot <command> [flags]

COMMANDS
    proxy     Run the metering forward proxy
    report    Per-host bytes, share of total and averages from a traffic log
    watch     Live tail of a traffic log as requests arrive
    help      Show this help

WHAT IT ANSWERS
    "What is actually using my bandwidth?" - measured, not guessed. Point a
    program's proxy setting at trafficpilot and every host it talks to, and
    every byte that costs you, is written to a JSON-lines traffic log.

WHAT IT DOES NOT DO
    HTTPS is TUNNELLED with CONNECT and NEVER DECRYPTED. trafficpilot sees the
    host and the byte counts, and nothing else. It installs no root
    certificate and intercepts no TLS. It also only sees a program's traffic
    if that program is configured to use it.

EXAMPLES
    trafficpilot proxy  --listen 127.0.0.1:8080 --log traffic.jsonl
    http_proxy=http://127.0.0.1:8080 https_proxy=http://127.0.0.1:8080 curl http://example.com/
    curl -x http://127.0.0.1:8080 http://example.com/
    trafficpilot report --log traffic.jsonl --top 10
    trafficpilot watch  --log traffic.jsonl --interval 2s

Run "trafficpilot <command> --help" for per-command flags.

Recorded from the shipped binary, not written by hand.

Windows (amd64) macOS (Apple Silicon) macOS (Intel) Linux (amd64)

Source

Every file the program is built from:

console.go · console_test.go · guided.go · main.go

SHA-256 checksums · build instructions & scope notes · full build plan

TrafficPilot

Preview