Does the Nodetonet dashboard update in real time?

Yes. The dashboard communicates over a persistent WebSocket, so credit balances, proxy status and device counts all update live without a page refresh. A green indicator in the top right confirms the socket is active; grey means it is reconnecting and numbers will catch up automatically.

What does the runway estimate on the Service Credit card mean?

It shows how long your current balance would last at your average daily spend rate from the past seven days. If nothing has been running for a week it shows infinity. If you have active proxies burning credit it gives a day count so you know when to top up. It does not account for scheduled future usage, only past burn rate.

Why is my Devices Online count lower than the number of tokens I created?

A token and a device are different things. A token is a pairing credential; a device is a phone or PC that has successfully connected using that token. Tokens can exist without a device paired, and a paired device can go offline due to battery optimisation, Wi-Fi sleep, or the app being closed. Check /devices for per-device status.

What is the difference between N and M in the Active Proxies card?

N is the number of proxies currently active — running, reachable, and billing. M is the total number of proxies ever created on your account, whether active or stopped. Stopped proxies cost nothing; only active ones consume credit. The gap is your idle pool, ready to start instantly at no standing cost.

How do I know if someone is using my API key without my permission?

Check the "last used" timestamp and IP address in the Personal API Key panel at the bottom right of the dashboard. If you see a recent timestamp from an IP address you do not recognise, rotate the key immediately using the rotate button and then audit any scripts or integrations that hold it.

Can I see all my proxies from the dashboard?

The Recent Proxies table shows your five most recent proxies as a quick reference. For the full list with filtering by type and status, sorting, and batch controls, go to /proxies. The dashboard is a cockpit view designed for a five-second health check, not a full management interface.

What should I do if the live indicator turns grey?

A grey indicator means the WebSocket is reconnecting, usually after a brief network interruption on your browser side. Wait a few seconds — it reconnects automatically and the numbers update. You do not need to reload the page. If it stays grey for more than a minute, check your own internet connection.

Where do I find the full billing and transaction history?

The Service Credit card on the dashboard shows your current balance and a runway estimate. For the full ledger — every top-up, every per-second burn entry, webhook credits and refunds — go to /balance. You can also export the history for accounting purposes.

The Nodetonet dashboard, card by card — what every number actually means

The Nodetonet dashboard is the first page you land on after logging in, and it is intentionally dense. The goal is that you can glance at it for five seconds and know the complete operational state of your account: do I have credit, are my proxies running, are my devices reachable, and what happened recently? Once you understand what each card is actually measuring, the dashboard becomes your fastest diagnostic tool — far quicker than digging through logs or pinging devices one by one.

TL;DR: every card on the home screen is a live operational signal. The three stat cards (credit, proxies, devices) tell you whether your infrastructure is healthy right now; the Recent Proxies table and Quick Actions let you act without navigating away; and the API Key panel tells you whether something else is acting on your behalf.

How the dashboard stays live

Before walking each card it helps to understand the plumbing. The dashboard communicates over a persistent WebSocket — the same transport that mobile devices use to stay connected to their edge server. That means numbers update in real time without any page refresh. If you add credit from another tab, the balance card updates instantly. If a device goes offline, the Devices Online counter decreases within seconds.

A small connectivity indicator lives in the top-right corner of the screen. When it is green the WebSocket is healthy; when it turns grey the socket is reconnecting, usually after a brief network hiccup. During a grey period the numbers shown are frozen at the last known state — they catch up automatically the moment the socket re-establishes. You do not need to reload.

1. The Welcome strip

The top banner greets you by username and shows a one-line subtitle such as 3 proxies active · $48.92 credit. This subtitle is a compressed version of the three cards below — it exists so you can read the essentials even before the cards fully render or if you just want a quick glance. If it reads 0 proxies active · $0.00 credit you know, without scrolling, that you have nothing running and an empty wallet.

2. Service Credit

The violet card on the left shows your prepaid balance in USD. Nodetonet uses a pay-as-you-go prepaid model — you top up credit and the platform deducts cost as your proxies and tunnels run. There is no monthly subscription, so when everything is stopped, the balance does not move.

Below the big dollar figure is a runway estimate: for example "~1 488 days at current burn." That number is calculated from your average daily spending over the preceding seven days:

If you have spent nothing in seven days the runway shows as infinite (∞) — your balance would last indefinitely at that rate.
If you ran ten proxies heavily yesterday, the burn average rises and the runway shortens accordingly.
If auto top-up is enabled, any positive runway can be treated as effectively indefinite — the balance will be replenished before it hits zero. Projected charges are not subtracted from the displayed balance; the figure is what you have right now.

Clicking the card navigates directly to /balance where you can review the full transaction ledger, set auto top-up rules, and see the per-second burn history. For a detailed breakdown of what drives cost see understanding your bills.

3. Active Proxies

The cyan card in the centre shows proxy counts in N / M format, where N is the number currently active (running, traffic-capable, and billing against your credit), and M is the total number of proxies ever created on your account. The difference M - N is your idle pool — proxies that exist but are stopped, incurring no cost.

The sub-line shows the combined daily burn rate for everything currently active, for example "2 idle · $0.066/day." Multiply that figure by 30 to get a rough monthly estimate. Bear in mind that active proxies span several types:

Mobile (Android) proxies — your paired phones acting as exit nodes over their cellular SIM.
Rotating proxy groups (token groups) — pools of mobile devices with round-robin or least-connection selection and automatic failover.
SOCKS5 / HTTP proxies — single-device tunnels supporting both protocols.
HTTP tunnels — inbound tunnels hosted by a Windows .exe agent.
Upstream-only proxies — proxies that chain through an external residential or datacenter provider instead of a local device.

If N is unexpectedly lower than you remember creating, check whether a proxy was auto-stopped because a client quota was exhausted. See quota limits per client for how per-customer enforcement works.

4. Devices Online

The emerald card on the right counts paired devices currently reachable — those with an open WebSocket to an edge server and a heartbeat within the last 30 seconds. The sub-line breaks the count by type, for example "2 Android · 1 PC."

This is the single most important card when a proxy starts behaving strangely. A device that is offline means any proxy backed by that device will either fail or fall back to an upstream. Common reasons a device drops offline:

Android battery optimisation — the OS kills background apps to save power. Fix: disable battery optimisation for the Nodetonet agent in Android settings. See Android agent troubleshooting.
Wi-Fi sleep — some routers cut inactive connections. Fix: enable "Keep Wi-Fi on during sleep" in Android developer options, or switch to cellular.
App not running — the agent was manually closed. Fix: reopen and pair the token via a QR scan. See installing the agent.
Token revoked or expired — check /tokens for the token status.

Clicking the card takes you to /devices, which shows each paired device individually, including its last-seen timestamp, public IP, signal strength and the proxy it is backing. For a full explanation of what "online" means at the protocol level, read device health: what online means.

5. Recent Proxies table

Below the three stat cards is a table listing your five most recently created or most recently active proxies. Each row shows:

A status dot: green for active (traffic is flowing or the proxy is ready), amber for paused, grey for stopped.
The connection string — host, port, and a truncated credential. Click the copy icon to grab the full string including username and password.
The backend type: Android, PC agent, upstream-only, or token group.
The live throughput in Mbps, updated over the WebSocket.

Clicking any row navigates to the full proxy detail page for that tunnel, where you will find usage charts, full auth credentials, per-client controls, IP and domain allow/deny lists, and the action menu (start, stop, edit, delete). For per-client access control see proxy clients and per-customer auth.

The table only shows five rows. The complete list, with filtering by type and status and sorting by creation date or throughput, is at /proxies. If you manage a large fleet, bulk operations for managing 100 proxies explains the batch controls.

6. Quick Actions

A grid of large shortcut buttons lives below the Recent Proxies table. The defaults are:

New Proxy — opens the create-proxy wizard (type, device, protocol, port).
New Token — generates a pairing token and QR code for a new Android device.
Top Up — goes straight to the balance credit page.
Documentation — opens the docs. If you are reading this and want to return, the same button takes you back.

These four cover the most common next actions after landing on the dashboard. They are plain shortcuts — nothing more clever than that — but they remove the two or three navigation steps otherwise needed to get to each function.

7. Personal API Key panel

The bottom-right panel is often overlooked but operationally important. It shows:

The first eight characters of your personal API key, with an eye icon to reveal the rest.
A copy button — grabs the full key to the clipboard.
A rotate button — immediately invalidates the current key and issues a new one. Useful if you suspect the key has leaked or been logged somewhere it should not be.
The last-used timestamp and IP address — for example, "Last used 4 minutes ago from 203.0.113.7."

The last-used field is a security signal. If the timestamp is recent but you have not used the API, something else is calling it as you — possibly a script you forgot about, or a credential that has been shared or exposed. Rotate the key immediately in that case, then audit what has it. For full key hygiene practices and the difference between a personal key and a customer API token, read understanding your API key and customer API tokens vs personal keys.

Personal API keys are used for calls to the management REST API: creating proxies programmatically, reading usage stats, rotating tokens and so on. See REST API: your first call for a quick walkthrough.

Dashboard vs the engine-room pages — what lives where

The dashboard is a cockpit view — designed for a five-second health check. Several things are intentionally absent from it because they belong in specialised pages:

What you need	Where to find it	Why it is not on the dashboard
Full proxy list, filter, sort	/proxies	Too many rows to show in a cockpit
Full transaction and burn history	/balance	Raw ledger data, not a status signal
Every paired device, live stats	/devices	Device-level detail needs its own surface
Token management, QR pairing	/tokens	Infrequent but detailed task
Rotating proxy groups (pools)	/proxies (token group tab)	Separate workflow from single-device proxies
Audit log — who called what, when	Audit logs guide	Log data, not a real-time status signal

The cockpit/engine-room split means the dashboard never gets cluttered no matter how many proxies or devices you add. Keep it as your starting point for every session and you will always have an immediate read on account health.

Reading the dashboard under different conditions

A few patterns worth knowing as your account grows:

Credit runway dropping fast? Check Active Proxies for anything you may have left running unexpectedly. High throughput devices consume credit faster.
Devices Online lower than expected? Open /devices, filter by "Offline," and check the last-seen timestamp — a device that went offline hours ago usually points to a battery optimisation event.
Active Proxies showing N = 0 when you expect traffic? A proxy stopped by a quota enforcement will show grey status in the Recent Proxies table. See quota limits.
API key showing an unexpected last-used IP? Rotate immediately. The key controls your entire account management surface.

What is next

The complete Nodetonet walkthrough — from sign-up to your first live proxy request.
Your first token and Android pairing — pair a phone in under five minutes.
Monitoring your tunnel health — what to watch when you outgrow the dashboard snapshot.
Understanding your bills — the per-second billing model explained.
Create a free account and explore the dashboard yourself.