Managing your servers
Every server in your account lists here, with start, stop, reboot, console, and destroy on each row's ⋮ menu. The list refreshes on its own every few seconds, so statuses update without a reload.
Deploy a new server
The Deploy server button sits in the top-right of the page and opens the deploy wizard. From an empty account you'll instead see an Empty rack card with a Deploy your first server button.
Working inside a team account
When you're acting inside another account as a team member, the Deploy server button is hidden — you can still view and control what's already there, but deploying is reserved for the account owner.
Read the summary bar
The tiles across the top summarize your fleet:
- Servers — how many servers you have in total, and how many are running.
- vCPUs — total vCPUs currently in use.
- Memory — total memory currently in use.
- Run-rate — your monthly run-rate, with the approximate hourly rate underneath.
These count running servers only
vCPUs, Memory, and Run-rate add up only the servers that are running. Stopped servers don't contribute to the in-use totals shown here.
Find a server
Once you have more than a handful of servers, use these to narrow the list:
- Search — the search box matches on server name, handle, IP address, or tag. Filtering
is instant, and a handle matches on any part of it — paste
ekire-7k4m2por just7k4m2pout of a support reply and you land on the right server. - Status filters — the chips below the tiles let you filter by status. Each chip shows a live count, and only statuses that actually exist in your list appear.
- List / grid view — toggle between a detailed table and denser cards with the buttons on the right. Your choice is remembered the next time you visit.
What the table shows
In list view, each server is a row:
| Column | What it shows |
|---|---|
| Server | Name (links to the server's detail page), its plan, OS image and handle, and any tags. |
| Status | The server's current state (see below). |
| IPv4 | The public IPv4 address, or pending while one is being assigned. |
| Region | Where the server runs. |
| Specs | vCPUs, memory, and disk size. |
| Cost | The server's monthly cost, shown in your account's display currency (USD by default). Charges are always billed in USD. |
Copy an SSH command in one click
Click a server's IPv4 address and the full ssh root@<ip> command is copied to your clipboard, ready to
paste into a terminal.
Names and handles
Two different things identify a server, and it's worth knowing which is which.
The name is yours. Pick anything; rename it whenever you like; reuse the same name on ten servers
if that's how you think about them. Nothing depends on it being unique. The deploy form arrives with a
readable one already filled in — something like quiet-harbor — so you never have to stop and invent
one, and no two customers end up staring at the same my-server. Type over it, or press the dice for
another.
The handle is ours — ekire- and six characters, like ekire-7k4m2p. Every server gets one when
it's created, no two servers share one, and it never changes for the life of the server. It's on every
row of this list and in the header of the server's detail page, where one click copies it. Quote it to
support: it's the fastest way to point at exactly the server you mean. Under the hood it's also what the
server is called on the hypervisor, which is how we tie a machine back to your account.
Server statuses
The colored dot and the status chip tell you what a server is doing:
| Status | Meaning |
|---|---|
| Running | Powered on and reachable. The dot pulses green. |
| Booting | Being provisioned or powered on. Controls are hidden until it settles. |
| Stopped | Powered off. Start it to bring it back. |
| Error | The server hit an error. |
Control a server
Each row and card has a ⋮ actions menu. Which actions appear depends on the server's status:
- Running — Open console, Reboot, Stop, and Destroy.
- Stopped — Start and Destroy.
- Any other status — Destroy only.
No controls while booting
While a server is Booting, the actions menu is hidden entirely. Wait for it to reach Running or Stopped before acting on it. Only one action runs at a time — a spinner shows while an action is in flight.
Open the web console
For a running server, choose Open console from the ⋮ menu. It takes you to that server's Console tab, where the screen is attached directly to the virtual machine — so you get terminal access even when SSH or RDP isn't reachable, including when a firewall change or a bad network config has locked you out.
You can also go there directly: open the server and choose the Console tab.
Start, stop, or reboot
Open the actions menu
Click the ⋮ button on the server's row or card.
Choose an action
Pick Start (stopped servers), or Stop or Reboot (running servers).
Watch the status update
The list refreshes on its own, so the status chip moves to its new state within a few seconds.
Destroy a server
Destroying is permanent. Choose Destroy from the ⋮ menu to open a confirmation dialog that spells out exactly what happens.
Select Destroy
Open the ⋮ menu and choose Destroy.
Type the server's name
You must type the server's exact name before the Destroy button unlocks.
Confirm
Click Destroy. Billing stops immediately.
This can't be undone
Destroying a server wipes every disk for good and releases its public IPv4 address. There's no undo — if you might need the data or the IP again, take a snapshot or backup first.