A tour of the uniz.host dashboard — what this page is telling you

The uniz.host dashboard packs a lot onto one page. A single server row carries several layers of information, the tab bar is long, and each chart mixes numbers from different sources. This article walks through what each part means, with the most attention on the part people misread most: the resource-usage charts.

Where the dashboard menu takes you

On a computer the menu sits on the left, starting with Overview and followed by groups.

Help links such as Wiki guides and Contact us sit at the bottom of the menu. On a phone the menu becomes a bottom bar with four buttons: Overview, Servers, Credits and More, which opens everything else.

Above the menu is the Search… box (or press Ctrl K from any page). One box finds servers, pages, commands and guides.

Two things people get wrong. First, "Settings" in this menu is for your user account — your photo and display name, theme, language and notifications. There is no password setting, no two-factor option and no delete-account button. Server settings live in each server's own Settings tab. Second, the low-balance banner above the page content appears only when your balance is below the threshold or negative; if the balance read fails, it just stays silent.

The server list, and what each row carries

The All servers page groups your servers by state: Running, Asleep and Other (stopped, starting, archived and so on). A group with no servers is not shown. At the top of the page a card shows the sizes you can create right now, with a "Show details" button; that is free space across our machines, not anything about your servers.

Each row carries exactly this:

• The server name is a link covering the whole row — click anywhere to open the server, except on a button in the row.
• A "Shared" badge after the name means you do not own that server — you are there as a team member.
• The state line says what the server is doing: how many are playing, how long it has been asleep, or why it was stopped.
• The machine line gives the server type, the machine name, and the RAM and vCPU you chose. Those are limits, not live usage.
• CPU and RAM bars appear only while the server is running; these are live usage.
• Console and Files shortcuts open those tabs directly (shown according to your permissions).
• An action button such as Wake, Stop, Start or Restore, depending on the server's state. Every one asks you to confirm first.

The tabs on a server page, and what each is for

Click into a server and you get a header with its name, state, and start/stop buttons. Below the header is the tab bar.

Some servers also show an AI Assistant tab at the end, and a Velocity server gets a Network tab. Not everyone sees every tab. Team and Public page are owner-only; Files and Backups depend on the permissions the owner grants. A team member seeing fewer tabs than this table is the permission system working correctly, not a broken page.

The address players actually need

On the Overview tab, below the header, sits the Join the game card — the card you will send to friends most often. Every field has its own copy button, and where the game supports it, a "Share a link with friends" button sits in the corner.

For Minecraft the card has two parts. The Java part has a single address field with the note No port needed. If you have connected your own domain, a Custom domain field is added — both addresses genuinely work. The Bedrock part (a Bedrock server, or a Java server with crossplay on) has an address field paired with a port field.

For every other game the card has one field, Address (paste it whole, port included). Copy it and paste it into the game in one go; there is no port to split off.

Before a port has been reserved, the port field reads Port not yet assigned — give it a moment and refresh.

The common trip-up is a Java server with crossplay on. Its Bedrock port is only for Bedrock players; Java players still type the bare address.

Beside the Join card is the Running cost card, which shows the hourly price and what this round has charged so far (owner only), with a "See this server's charges" link.

What the Specs card tells you

The Overview tab has a Specs card whose rows depend on the game. For Minecraft: type, version, crossplay (Java servers), size and machine. For other games: the game's name and size. At the bottom is the Storage line with a bar showing how much is used.

The size row is the RAM and vCPU you chose — limits, not cores reserved for you alone. Storage is the real size of the world and every file, against the server's total space. When it gets close, the card warns that the world is nearly full: that is the signal to prune old backups or move to a bigger size. The link at the bottom of the card ("Change the size or version" on Minecraft) goes straight to the Settings tab.

How to read the resource-usage charts

The Resource usage section on the Overview tab is the most informative part of the server page — if you read it correctly. The charts run from the game first (Players online, then TPS or Server FPS) to the machine (RAM, CPU, Network, Disk I/O and Disk). Press the enlarge button on any chart to see it full-screen, and on a computer you can choose one or two columns.

Pick the range that matches your question first

The range buttons beside the heading set the window the charts draw, from "5 min" through "7d" and "30d". The charts always open on the shortest range.

Match the range to the question. "What is happening right now?" wants a short range; "is my RAM enough?" wants a long one, because that behaviour never shows up in five minutes. The charts refresh the selected range on their own, and the "Refresh" button fetches immediately. The 30-day range is the slowest to load and the most likely to fail; if it does, a message says so plainly instead of spinning forever.

Under the heading is a small line giving the percentage of this window the server was online. If the server was off during the window, that line says so too, for example "Off until 14:10". Off periods show as gaps in the chart, not smoothed over with a joining line, and a server that auto-slept counts as off in exactly the same way as one you stopped yourself.

Read the figure at the top of each chart before the line

Each chart has a large figure at the top, the value now, with a small line under it. The RAM and CPU figures do not come from the chart — they come from a live poll every 5 seconds while the server runs. That is why a server started half a minute ago already has figures while its chart is still empty. RAM is shown in gigabytes, with of {total} GB underneath; CPU is shown as a percentage of the limit, with {used} of {total} vCPU underneath.

If the server is not running, the figures show a dash, because there is no current value. If the whole section reads "No usage data yet", there is nothing to measure at all, which is different from "No data for this period": measuring works, but the range you picked has no data points.

To read the exact value at any point, hover over the chart — the tooltip always shows the real number.

Keep disk space and disk throughput apart

The single most misread thing here is that two charts start with the word "Disk", and they measure completely different things.

Disk I/O spiking every few minutes is normal for a game that autosaves on a timer. It does not mean the disk is filling up, and a nearly full disk does not move the I/O line. To see how much space is left, look at the Disk chart or the Storage line on the Specs card. The Network chart reads the same way as Disk I/O: two per-second rates (Out and In), not a running total, and with no limit to compare against, so its axis scales itself.

Find the restart and OOM lines on the charts

Vertical dashed lines on a chart are events, of two kinds: a restart (the container started again, whether you pressed it, the platform did it, or it came from a scheduled task) and an OOM (the server was killed for using more RAM than its limit). These lines are drawn on every chart at the same moment, so you can see at once whether a jump in a game chart lines up with a restart, and the line under the heading gives the time of the latest one, for example "Restart 17:02" or "OOM 03:15".

A single OOM is hard evidence that RAM is not enough for what the server is doing, not just a suspicion. The details are in Game server RAM.

Read the RAM warning as a 7-day verdict

Sometimes a warning box appears above the charts: "RAM has been near its limit often over the last 7 days — a bigger plan may help", with a "View plans" button that goes to the Size and machine group on the Settings tab.

This box is not read from the range you have selected. It is a fixed 7-day verdict computed on the server side, and two conditions must both hold: the server has run for at least 24 hours in total over the 7 days, and RAM has been above 90% of the limit for more than 20% of that running time. The result is also cached for about five minutes, since it barely moves.

So switching to the 5-minute range and seeing a calm, flat chart does not make the warning wrong. And a brand-new server, or one switched on and off for under 24 hours in the week, never sees this box at all, even if its RAM is pinned the whole time — there is not enough data to judge. The "View plans" button appears only for the server's owner; team members see the message without the button, because changing the size spends the owner's credit.

The game charts, and what these charts do not tell you

Games that send us in-game figures get a "Players online" chart (with the peak for the range) and a TPS or "Server FPS" chart ahead of the machine charts. The TPS chart pins its axis near 20 so that a 19.9 line reads as healthy. Games that send no in-game figures say so in a line under the heading and get the machine charts only.

Finally, what these charts contain no trace of: money. This server's hourly price and what this round has charged so far are in the "Running cost" card beside the Join card. For what your whole account has spent, go to Credits (/dashboard/credits) and its 30-day credit-usage chart and spending history.

Read next

• Game server RAM — what causes OOM and how much RAM is enough
• /pricing — the price table and a real cost calculator