Credits and billing — how you are charged, and how to read your bill

The question everyone asks before opening their first server is "so how exactly does this take my money?" — this guide answers it end to end: what a credit is, when the meter actually runs, and how to read every part of /dashboard/credits.

What a credit is, and the minimum top-up

A credit is the unit of money in your account, at a fixed ฿1 = 1 credit. There is no other conversion to learn. Topping up puts money in that wallet up front, and server charges are drawn out of it as you actually use them — it is not a monthly rental you prepay in one lump, and nothing is charged to a card on a recurring cycle. The same credit works for every server on the account.

The minimum top-up is ฿20 per transaction. Enter less and a message shows the minimum and the pay button will not go through; the API applies the same floor independently. Above that, any amount is fine.

How charging works

There are only two layers to it.

Layer one — per RAM size, per hour, only while the server is on. Each size has its own hourly rate, and a slice costs the hourly rate × seconds online ÷ 3600. The meter opens only once the server reports itself genuinely up, so time spent starting is not billed, and while a server is stopped, asleep or archived, compute is ฿0 — that is exactly what "per hour it is on" under the price in the create wizard means. While the server is up, charges are written about once an hour, and the remainder is charged the moment it stops or sleeps — nothing is held back until the end of the month.

Layer two — caps per round (a 24-hour round and a 1-month round). Each server counts two rounds side by side, both starting when the server is turned on. Before every deduction the raw amount is compared against what is left of the current 24-hour round's cap and of the current 1-month round's cap, and the smallest of the three is what you are charged. So within each 24-hour round a server never pays more than the 24-hour round cap, and within each 1-month round never more than the 1-month round cap, however many hours it ran. Once a round reaches its cap, the server runs free until that round ends, and if it is still on when a round ends, the next one starts at once. Turning the server off ends both rounds there and then — whether you stop it yourself, a schedule you set stops it, it auto-sleeps, or it stops because the account ran out of credit — so the next start begins fresh rounds. Stopping a server that has reached its cap gives up the free time left in that round. A restart does not count as turning it off, and neither does a stop made for a reason on our side, such as a fault, maintenance or a start that did not finish in time: the server stays in the same round. A 1-month round ends on the same date and time one month later, Thai time (on the last day of the month when that month has no such date).

Example figures for the standard machines — these are compiled-in defaults, they can be overridden on the server side, and different hardware classes price differently, so treat the pricing page as the live figures:

The disk in the "Disk included" column comes with the size at no extra charge. Wanting more space than that means moving to a larger size.

Topping up

Open the top-up window

Go to /dashboard/credits — the "Credits" entry in the dashboard sidebar. The top of the page is your wallet, with a "Top up" button beside the balance. Pressing it opens the "Top up credit" window, which shows your balance now and roughly how long it lasts at the rate you are running.

Pick an amount and top up with PromptPay

The window offers ready-made amounts, each showing roughly how many hours of play it adds, based on the servers you have running (or on the smallest size when nothing is running). For anything else, type it under "Other amount". Then press "Top up ฿… with PromptPay" and your browser goes to the payment page with a PromptPay QR. If the amount you typed is below the minimum, the warning appears when you press that button, and you stay on the window.

Scan the QR and wait for the credit

Scan the QR with your banking app. If you are browsing on the same phone, save the QR image and pick "scan from image" in your banking app. Once paid, you are sent back to the page you were on.

This is the part worth knowing: the credit is often not there the instant you land, because your browser gets back before the bank's confirmation does. The dashboard shows a strip saying it is waiting for the bank to confirm — and that you should not pay again — and asks for the status itself every 3 seconds (every minute after 10 minutes) until it knows. Meanwhile the wallet on the credits page shows the amount as on the way. When the money lands the strip turns into "Top-up done" with your new balance; no refresh needed. If you cancelled on the payment page or the QR expired, the strip says you were not topped up and nothing was charged, with a Try again button.

Check your spending history

Scroll to "Spending history" and pick "Top-ups only". The newest entry is at the top, reading "PromptPay top-up" with its time and amount. Once that row is there, the money is in the account and can start servers immediately.

Reading the wallet

The top of the page is your "Credit balance" in large type. It can go negative, shown in the warning colour, because a final usage charge can push past zero just before servers are stopped. Under it is how long you can play at the current rate — at least about so many hours. It counts the servers you own that are running and ignores caps, so it is a floor. With nothing running, the line says instead how long your credit runs the 2 GB size, at least — for example "Run a 2 GB server for at least ≈ 40 h". The line is hidden only when your credit covers less than an hour. Beside it are "Top up" and "How billing works", which opens an explanation of rounds and caps with examples.

Then come four figures:

• Running now — how many servers are billing, and their combined hourly rate
• Spent today — what has been spent since midnight, Thai time
• Last top-up — the amount and date of your latest top-up
• Total top-ups (since you signed up) — the lifetime sum of money you have actually paid in, with nothing subtracted. It counts payment-backed top-ups only, so credit from coupons or referral rewards is deliberately not in it. It is a cumulative figure, not a spendable one.

The wallet ends with the code field (see Coupons below).

This round per server, and the savings

• This round, per server — every server you own. A server inside a 24-hour round gets a bar showing what this round has charged against the cap, how much is left before the cap, and when the round ends; once it has reached the cap, it says the server runs free until the round ends. A server outside a round reads "not on this round", with its hourly rate and its cap per 24-hour round. Servers shared with you by someone else are not listed, because their owner pays for them.
• Saved over the last month — the most misread figure on the page. It has one row per server, each showing what the server has used against its cap and what that leaves saved, and the line under the list defines it exactly: each server's 1-month cap minus what it actually paid over the last month, counting hourly-billed servers only. "The last month" runs back from now to the same date and time a month ago and includes the hour that is running right now. It is not a billing round, so stopping a server or letting it sleep does not send what it paid back to zero. In other words, "what running flat out to the 1-month cap would cost, minus what you really paid over the last month". So it is not a discount, not a rebate, and not credit you can spend — it only shows how much hourly billing plus auto-sleep is keeping off your bill. But every stop you cause settles the bill: pressing Stop, a scheduled stop, auto-sleep and running out of credit all do, while a restart or a stop for a reason on our side does not. The next start opens a new bill, with fresh 24-hour and 1-month rounds. So a server stopped even once after reaching its cap, or stopped and started often, can pay more over the last month than running it always-on would cost, even though no round ever went over its own cap. When that happens, the row shows what the server paid next to the always-on price instead, and no saving. A freshly created server that has never been switched on shows the full cap as savings, which is normal.

Reading the 30-day chart and your spending history

Credit usage by server (30 days) is a daily bar chart for the last 30 days up to today, each bar stacked by server, with a legend and the 30-day total. A day with nothing running shows as an empty stub, and pointing at a bar shows that day's amount. "30 days" here is how far back the chart looks, not a billing round.

Credit history by server gives each server's 30-day total; press a row to open that server's days. The link to a server's charges on its own page opens its row here for you.

Spending history is the real bill. Show "All" or "Top-ups only". Entries are grouped by day, Thai time, and each day's heading says what that day cost. Inside a day there are two kinds of row:

• A running session — one row per time the server was on: the server's name, how long it ran and from when to when, what it cost, and why it stopped — it slept because nobody was playing, it was stopped, it stopped because the account ran out of credit, or it stopped on schedule. A server still running reads "Still on · the meter is running". A session across midnight is split into each day's part, and a session that hit a cap carries a tag saying the 24-hour or 1-month round cap was reached and how much over it was not charged.
• Other money in and out — "PromptPay top-up", "Code …" for a coupon, "Referral reward", "Adjustment" (a manual correction by our team, for instance compensation after an incident), "Refund", "Storage", and "AI assistant" (spend on the in-dashboard AI assistant).

"Show earlier entries" at the bottom goes back further.

Where each round's cap is shown

On /dashboard/credits, This round, per server lists every server you own. A server inside a 24-hour round gets a bar showing what this round has charged against the cap; a server outside one shows its hourly rate and its cap per 24-hour round. On a server's own page, the Running cost card shows what it has been charged in both rounds, the 24-hour round and the 1-month round, each against its cap and with the time it ends, plus a "See this server's charges" link (only the server's owner sees the money on this card).

Before you create a server, the size step of the create wizard shows both caps for the size you pick under Forgot to turn it off? It stays capped, and the rate table on the pricing page gives both round caps for every size. For how the rounds are counted, press How billing works on the credits page.

Coupons

The wallet ends with "Have a code?". Type the code — it is upper-cased for you as you type — and press "Use code". On success a message tells you how many credits arrived, and the balance and history refresh straight away; the coupon credit shows up in your spending history as a "Code …" row. A malformed, unknown or expired code each gets its own message. A line under the field says free credit codes are handed out on the uniz.host Discord.

What happens when you run out

When the balance no longer covers the charges, running servers are stopped, and opening one shows a strip reading "Out of credit, so the server was stopped", saying the world and files are all there, with a "Top up" button. Team members see a different "Out of credits" message telling them to wait for the owner, with no button, because a member cannot pay the owner's bill.

Nothing happens to your world. The server is only stopped and the data is all still there. Top up until the balance is positive, then start it as usual — but it does need to be genuinely positive: at or below zero, both starting a server and creating a new one are refused. Before it gets that far, a low-balance strip appears across the dashboard when something is running and your credit would last less than 24 hours at that rate, switching to a negative-balance message below zero. Treat it as the cue to top up before a session gets cut short.

Read next

The biggest lever on your bill is choosing the right size in the first place: how much RAM does a game server need. And if you have not opened a server yet, the current rates for every size are on the pricing page.