Server & hardware monitoring: two dedicated pages, remote and local

Whether a remote VPS is over its traffic quota and whether your local GPU is running hot again are two different jobs—so 77Fox gives each its own page: Server monitoring watches remote nodes, Hardware monitoring watches local temperature and power. Dashboard widgets can still pin both onto one overview screen, and both pages follow the same rule: refresh on demand, stay quiet in the background.

Server monitoring

The server list shows latency, health and traffic. Refreshing is on demand: you get current data when you open the view, while tray monitoring drops to a lower frequency so the monitoring tool does not itself become the background load.

Bind VPS traffic with one command

Server monitoring can bind a Linux VPS to your account and track traffic per billing cycle. Binding is light: run a single install command on the target machine, and inbound and outbound traffic accumulates from there without any manual bookkeeping.

This is what stops the classic "throttled at the end of the month before you notice you went over" — usage stays visible instead of arriving with the bill.

Cycles, reset dates and provider calibration

Billing cycles differ per provider, so reset rules are configurable: choose monthly or yearly resets and set the reset month and day. More usefully, calibration lets you align the current cycle to the number shown in your provider's panel when the two drift apart, so later figures track the real bill instead of restarting from zero.

What the status colours mean

Latency colours were redefined to avoid alert fatigue from a wall of red: high latency is orange, and dark red is reserved for genuinely unreachable servers. VPS cards use a denser layout with details and actions moved into hover hints and the context menu, keeping long lists readable. Country flags make regions easy to scan.

Hardware monitoring (Windows desktop)

Hardware monitoring reads local CPU and GPU temperature and power. The tray shows auto-detected short model names with live readings, and a dashboard widget links through to the full monitoring page.

Low-level sensors and signed drivers

Reading low-level sensors requires driver support. 77Fox verifies the official driver's version, hash and digital signature before enabling it, then restarts the sampling process automatically. Production installs handle this on first launch or after an upgrade, and Windows builds run elevated by default to reach low-level sensors.

If low-level sensors cannot be enabled — for example when a source-build process is not running elevated — the app states the status clearly and offers a re-detect and repair action. GPU monitoring is unaffected. The web console does not run local hardware monitoring.

History and electricity cost

The full page charts temperature, power and energy over ranges from one hour to 30 days. Set your electricity price in a major currency and the app estimates cost for today and for any range you select. For a machine that runs long jobs, that is a direct answer to "what does this setup actually cost to run per month".

Why "refresh on demand" matters

The usual failing of monitoring tools is that they cost more than they save. 77Fox schedules background work centrally, starts heavy services only when needed and loads pages on demand, which keeps idle memory and process counts low. The hardware sampling interval is adjustable too, so the trade-off between immediacy and overhead stays yours.

Frequently asked questions

What needs installing on the VPS?

A single install command, provided by 77Fox and hosted on its own domain. Once bound, traffic accumulates from inbound and outbound deltas into a cycle total.

What if the traffic total disagrees with my provider panel?

You can calibrate the current cycle against the provider figure so later numbers track the real bill, without resetting to zero. Reset month and day are configurable monthly or yearly.

Why does hardware monitoring need administrator rights?

Reading CPU and other low-level sensors requires a driver. The app verifies the official driver version, hash and digital signature before enabling it, and Windows builds run elevated by default. GPU monitoring is not subject to this.

Can I see hardware monitoring on the web?

No. Local hardware monitoring runs only in the Windows desktop app. Server monitoring is available on both desktop and web.

Is monitoring resource-hungry?

Refreshes happen on demand and tray updates slow themselves down automatically. Background work is centrally scheduled, heavy services start only when needed, idle memory and process counts stay modest, and the refresh interval is adjustable in settings.

Are server monitoring and hardware monitoring the same page?

No, they are two separate pages: server monitoring watches remote nodes for latency, health and cycle traffic, while hardware monitoring watches local CPU and GPU temperature and power. Dashboard widgets can put the key readings from both on one screen.

Ready to put your efficiency tools on one dashboard?

Download the Windows desktop app, or sign in to the web console with Google. Your first login creates an isolated profile and initializes cross-device sync automatically.