Moxon Metrics

Linux desktops and servers · version 4.0

Everything your machines are doing, and everything around them

Moxon Metrics is a monitoring tool for people who look after their own computers and networks. It shows every reading, every app, every connection and every device on the network, keeps a month of history, warns you before problems turn into outages, and lets you open any of your machines from anywhere, end-to-end encrypted with keys that never leave your devices.

Download freeWhat's new in 4.0Take the feature tour
Version 4.0 is the current release. It is a rebuild in native code (Rust, no Python) for Ubuntu 22.04 and newer, on Intel/AMD and ARM, with a separate package for servers. Upgrading from 3.3 to 4.0 keeps your history, settings and relay pairing.

See it all, per app

Processor, memory, disk, network, graphics, power and temperature, split by app and process, live and for the last 30 days, without installing anything else.

Understand your network

A map of every network you join: the devices on it, routers, DNS, DHCP, the protocols heard on the wire, the path to the internet and the traffic mix.

Reach your machines anywhere

Open any of your machines, or your phone's view of them, through a relay that passes encrypted data it cannot read. No ports to open, no VPN to set up.

Know before it breaks

Alerts for heat, full disks, failing drives, low battery, data caps, unusual activity and new devices, sent to your desktop, phone, chat, email, SMS or WhatsApp.

New in 4.0

Version 4.0 rebuilds Moxon Metrics in native code. Everything 3.3 does is still there; this is what changes.

All native, no Python

One background agent replaces the separate 3.x services. Runs on Ubuntu 22.04 and newer (tested on 22.04, 24.04 and 26.04), on amd64 and ARM64, including Raspberry Pi and ARM servers.

Desktop and server packages

moxon-metrics is a native window with a tray icon. moxon-metrics-headless is the agent and the moxon command line with no desktop dependencies; it runs as a system service for a user you choose, with nobody signed in.

A new window

Navigation down the left side, and three views: Basic for the readings that matter most, More for the detail behind them, All for everything.

Wireless tab

Wi-Fi link details, a log of roaming between access points, nearby networks, and LTE/5G modems with operator, technology and signal.

Packet capture

Capture live on one interface, read each packet decoded and in hex, and save it as a .pcap file for Wireshark. Asks for the administrator password each time.

SMS and WhatsApp alerts

Alongside desktop, ntfy, Telegram and email: SMS through Twilio or any provider with a web link, and WhatsApp through Meta or Twilio, using your own provider account.

The moxon command

Check a machine, join your relay, make pairing codes, list devices, control the terminal and sharing, run the agent as a service, read logs and verify that every part works.

Same relay, same keys

4.0 speaks the same end-to-end encrypted relay protocol as 3.3, so machines on either version share one account. The relay still never has the keys.

Upgrades in place

Install 4.0 over 3.3 and your history, settings and relay pairing are kept. The 3.x services are switched off and replaced by the agent.

How it works

Each of your machines Systemhardware · apps Helperroot · reads only Agentrecords · runs as you Historystays on this disk readings every few seconds Windowcharts · processes Alertswatch the history shows checks you pause, reprioritise, end desktop · ntfy · Telegram · email · SMS · WhatsApp sharing link · HTTPS · read-only Machine on your networkor a browser on the same Wi-Fi encryptedconnects out Relayroutes and stores, cannot read end to endencrypted Your phoneany network Machinesanywhere Only your devices hold the key. No ports to open at home. 1 2 3 4 5 6
Swipe sideways to see the whole picture. Readings never leave a machine unless you switch on sharing or the relay. Orange numbers are the levers you control.

Your levers

  1. 1Recording: a reading every 1 to 60 seconds, how many days to keep, and fair accounting of shared memory.
  2. 2Alerts: which ones, their limits, how often they repeat, and where they go.
  3. 3Processes: pause, resume, change priority or end your own; system processes are protected.
  4. 4Network: listening is passive; a scan runs only when you ask. Monthly data caps per network.
  5. 5Sharing: off by default. Switch on for a read-only link; a new key cuts off every old link.
  6. 6Relay: add a device with a one-time code, remove any device, keep your recovery code.

Live

Readings every few seconds, explained

The Live view shows the whole machine at a glance and what is responsible for it.

  • Processor load per core with clock speed and throttling, memory with its real breakdown, swap and pressure, disk speed and free space, network speed per interface.
  • Battery charge, health, charge cycles and power draw; temperatures and graphics use.
  • "Apps right now": every app ranked by processor, memory, disk, network, graphics or energy, with its processes one click away.
  • Charts keep the last 5 to 60 minutes on screen; readings every 1 to 60 seconds.
Why it mattersMost tools show that the fan is loud. Moxon Metrics shows which app made it loud, how long it has been doing it, and how much battery it cost.

Apps & processes

Per-app use, including network and energy

  • Every process as a list or a tree, with its user, command, start time, threads and priority.
  • Per app: processor time, memory (shared memory split fairly between apps), disk reads and writes, network sent and received, graphics time and energy in watt-hours.
  • Click a process for its open files, network ports and working folder.
  • Pause, resume, change priority or end your own processes. System and desktop processes are protected so a stray click cannot take the machine down.
Why it mattersPer-app network and energy use are the two numbers operating systems hide best. They are usually the answer to "why is my connection slow" and "why is my battery empty".

Network & topology

A map of every network you join

  • The devices around you, identified by maker, name and type (router, switch, access point, printer, phone, TV, camera, computer), with first and last seen times.
  • What the machine hears on the wire, listening only: LLDP and CDP (which switch port you are plugged into, and its VLAN), spanning tree, DHCP, IPv6 router adverts, mDNS, SSDP and NetBIOS.
  • Routing table, addresses, DNS servers and DHCP lease; routing daemons (FRR, BIRD, keepalived and others) with their BGP and OSPF neighbours.
  • Path to the internet hop by hop, gateway and internet latency, Wi-Fi signal, band, channel and link rate, IPv4 versus IPv6 traffic, and every connection with the app behind it.
  • An active scan of the network runs only when you ask for one.
  • Monthly data use per network with caps, kept for 13 months.
Why it mattersWritten by a network engineer: the switch port, VLAN and neighbours a laptop sees are exactly what you need on a site visit, and they are usually locked inside vendor tools.

System health

Drives, sensors, services and startup

  • Every drive's speed, busy time and health: SMART status, wear, errors and hours, checked hourly.
  • Memory pressure: the share of time apps were stalled waiting, which tells you when a machine really needs more memory.
  • All temperature sensors and fans; Docker and Podman containers and QEMU virtual machines with their use.
  • Services and startup apps: see what runs, start, stop or switch them off, with an administrator prompt when needed.
Why it mattersDrives rarely fail without warning; the warning is just buried in SMART counters nobody reads. Moxon Metrics reads them every hour and tells you.

History

A month of history, down to the app

  • Every reading kept for 30 days (you choose how long), summarised in 30-minute blocks so the file stays small.
  • Charts for processor, memory, disk, network, graphics, power, temperature, pressure, latency and battery, with sleep and restart markers.
  • Click any block to see the top apps at that moment, including their network use by connection.
  • A daily summary for the last 30 days and CSV export for any range.
Why it matters"It was slow yesterday afternoon" becomes a question you can answer: open the block, see the app.

Alerts

Warnings that arrive where you are

  • Processor or memory too high for too long, disks filling up, overheating, low battery, memory or disk pressure.
  • Unusual activity: compared with what is normal for that machine at that hour of the week, after a week of learning.
  • Drive health warnings, data caps at 80% and 100%, and new devices joining a network you know.
  • Delivered as desktop notifications, to your phone with ntfy, to Telegram or by email, with a repeat interval so they never turn into noise.
  • In 4.0, also by SMS (Twilio or any provider with a web link) and WhatsApp (Meta or Twilio), with a daily limit and quiet hours, since your provider charges per message.
Why it mattersThe useful alert is the one that says "this is not normal for this machine", not one more red number.

Your machines, anywhere

One window for every machine you own

  • Same network: switch on sharing and add the machine; its full dashboard opens inside your window over HTTPS, read-only, with its certificate pinned.
  • Anywhere else: connect your machines to the relay with a one-time pairing code. Each machine connects out, so there is nothing to open on your router.
  • Your phone: scan a QR code and see all your machines, their live summary and their history, over Wi-Fi or mobile data.
  • History while offline: machines upload encrypted 5-minute summaries (kept 30 days) and hourly ones (kept 400 days), so you can see what a machine did even while it is asleep.
  • Prometheus: a /metrics endpoint with the same access key, for Grafana and existing monitoring.
Why it mattersRemote monitoring usually means handing your data to someone's cloud. Here the relay only ever sees encrypted data and which of your devices are online. How that works.

Wireless 4.0

Wi-Fi and mobile links in detail

  • The Wi-Fi link: network, access point, band, channel and width, signal and noise, link rates and security.
  • Roaming: each move between access points, with the signal before and after and the channel.
  • Nearby networks, refreshed when you ask for a scan.
  • LTE and 5G modems through ModemManager: maker and model, operator, technology, signal and whether the modem is roaming.
Why it matters"The Wi-Fi keeps dropping" usually means roaming between access points or a weak mobile link. Seeing each roam, and the signal on either side of it, shows which.

Packet capture 4.0

See the packets, save them for Wireshark

  • Capture on one interface with an optional capture filter and a time limit of up to an hour.
  • A packet list with each packet decoded and shown in hex; headers only unless you ask for full packets.
  • Save the capture as a .pcap file.
  • Asks for the administrator password for every capture; the packets go only to the app of the person who asked.
Why it mattersWhen the charts say something is wrong on the wire, the next step is the packets. Here that is a tab, not a separate tool.

Servers 4.0

A package for machines with no desktop

  • moxon-metrics-headless installs the agent, the read-only helper and the moxon command line, with no window and no desktop libraries.
  • Runs as a system service for a user you name, so it records with nobody signed in. It never runs as root.
  • Join it to your relay with a pairing code, then watch it and open its terminal from your other machines or your phone.
  • Built for amd64 and ARM64, so it also runs on a Raspberry Pi or an ARM server.
Why it mattersServers are the machines you most need to watch and the ones nobody sits at. The headless package gives them the same history, alerts and remote access as a desktop.

Terminal

A shell on any of your machines

  • A Terminal tab in each machine's window: a shell on this machine, or on any of your machines through the relay.
  • Encrypted end to end with keys made for that one session; neither the relay nor your other devices can read or type into it.
  • Off on every machine until you switch it on there. You choose which of your machines may connect, and "Ask me each time" shows a prompt on the machine before anyone gets in.
  • Runs as the signed-in user, never as an administrator; ends after 15 minutes without typing or 8 hours; any open session shows a banner with an End button, and a log records who connected and when, never what was typed.

In Linux 3.3 and 4.0, and the macOS 3.4 preview.

Why it mattersFixing something remotely normally means SSH, port forwarding and keys to manage. Here it is a tab, and the owner of the machine stays in control.

On each system

FeatureLinux 4.0Linux 3.3macOS 3.x
Live readings, history, alerts, sharing, relay, phoneYesYesYes
Per-app network useYes (helper)Yes (helper)Yes (helper)
Per-app graphics useYesYesNot reported by macOS
Per-core clock and throttlingYesYesPer cluster
Memory and disk pressurePressure stall timePressure stall timeMemory pressure level
Drive healthFull SMARTFull SMARTPass / fail
Listening for LLDP, CDP, mDNS and othersYesYesYes
Services and startup appssystemd, autostartsystemd, autostartlaunchd agents and daemons
TerminalYesYes3.4 preview
Wireless tab, packet captureYesNoNo
SMS and WhatsApp alertsYesNoNo
Server package and moxon command lineYesNoNo
Processorsamd64, ARM64Any (Python)Apple silicon

The macOS and Windows versions are paused. They will be rebuilt on the 4.0 core.

Download

Linux: install with apt Recommended

Add the Moxon Metrics package source once; updates then arrive with your normal sudo apt upgrade. Packages and the source list are signed; apt checks the signature with the key you add in the first line.

curl -fsSL https://get.142-93-115-168.sslip.io/apt/moxon-archive-keyring.gpg | sudo tee /usr/share/keyrings/moxon-archive-keyring.gpg >/dev/null
echo "deb [signed-by=/usr/share/keyrings/moxon-archive-keyring.gpg] https://get.142-93-115-168.sslip.io/apt stable main" | sudo tee /etc/apt/sources.list.d/moxon.list
sudo apt update
sudo apt install moxon-metrics

On servers install moxon-metrics-headless instead of moxon-metrics. Intel/AMD and ARM64 (Raspberry Pi) are both served; apt picks the right one. To test upcoming versions, write preview instead of stable in the second line. More in the guide.

Stable: version 4.0

Ubuntu 22.04 or newer (tested on 22.04, 24.04 and 26.04), on Intel/AMD and ARM64. Install the desktop package or the server package on a machine, not both. Upgrading a 3.3 machine to 4.0 keeps its history, settings and relay pairing.

Linux desktop · Intel/AMD 64-bit
moxon-metrics_4.0.1_amd64.deb · 11.5 MB
SHA-256 61087e04b41ddedc1fea426b18127089e2cafa4a9ea894c6e171f32f3edbc575
Download .deb
Linux desktop · ARM64
moxon-metrics_4.0.1_arm64.deb · 10.4 MB
SHA-256 36678a925bcbac429058f607d703cd6d60db3ab4db32318e81b2caf39a6c999c
Download .deb
Linux server (headless) · Intel/AMD 64-bit
moxon-metrics-headless_4.0.1_amd64.deb · 6.2 MB
SHA-256 300e361753c2f8e53f0a3ac21cebdb4ce4755eeede507f9063af0d1a2a21df52
Download .deb
Linux server (headless) · ARM64, including Raspberry Pi
moxon-metrics-headless_4.0.1_arm64.deb · 5.7 MB
SHA-256 0d519d83c7d8077a77280f1d25ba577aa8b24ede4459cdee940a239ea5d39814
Download .deb

Desktop: sudo apt install ./moxon-metrics_4.0.1_amd64.deb (or the arm64 file), then open Moxon Metrics from your applications. Server:

sudo apt install ./moxon-metrics-headless_4.0.1_amd64.deb
sudo moxon service enable --user <name>
moxon join <code>

Use the arm64 file on ARM machines. <name> is the account the agent runs as (never root); the pairing code comes from Settings → Relay → Add a device on one of your connected machines, or moxon pair. More in the guide.

All checksums: SHA256SUMS. Everything is free to use.

Coming next

Planned after 4.0, in no fixed order and without dates:

Privacy, in one paragraph

Readings stay on each machine. Nothing leaves it unless you switch on sharing or connect the relay. Through the relay, everything is encrypted with a key only your devices hold: the relay can see which of your devices are online and how much data moves, but not their names, readings, history or terminal sessions. Read the details on the security page.