Credits and billing — how you are charged, and how to read your bill
Credits and billing — how you are charged, and how to read your bill
Last updated 2026-08-14
Short answer
uniz.host bills in credits at ฿1 = 1 credit, with a ฿20 minimum top-up. A server is charged per hour on its RAM size only while it is actually running (off or asleep = ฿0), under a three-step cap cascade — hourly, then daily, then monthly. A 2GB plan is ฿0.50/hour, capped at ฿7/day and ฿149/month. Your balance, top-up history and every individual charge live on /dashboard/credits.
Steps at a glance
Open the credits page
Enter an amount and continue to payment
Come back to the credits page and wait
Check the top-up history table
Contents
Contents
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 number on /dashboard/credits, including the one figure people go looking for there and never find.
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 minimum top-up is ฿20 per transaction. Enter less and the dialog refuses to submit and shows you the minimum instead; the API applies the same floor independently. Above that, any amount is fine — there are no fixed bundles to buy.
One ฿50 figure does appear on the site: the worked example inside the cost summary shown when you pick a server size, which tells you roughly how many hours that money buys. That number is a fixed illustrative amount written into the code, not the minimum. The minimum is always ฿20.
How charging works
There are only two layers to it.
Layer one — per RAM size, per hour, only while the server is on. Each plan 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 the line only while the server is running under the hourly rate means. Charges are written in small slices of roughly five minutes while the server is up, not held back until the end of the month.
Layer two — a three-step cap cascade (hourly → daily → monthly). Before every deduction the raw amount is compared against what is left of the day's cap and what is left of the month's cap, and the smallest of the three is what you are charged. So a server left on all day cannot cost more than the daily cap, and one left on 24/7 for a whole month cannot cost more than the monthly cap, however many hours it ran. The daily bucket is keyed to the Thai calendar day, not UTC, so it resets at local midnight.
Example figures for the standard plans — these are compiled-in defaults, they can be overridden on the server side, and different hardware classes price differently, so treat as the live figures:
Plan
RAM
vCPU
Disk included
Per hour
Daily cap
Monthly cap
Starter
1GB
1
15GB
฿0.30
฿5
฿99
Play
2GB
1
25GB
฿0.50
฿7
฿149
Squad
4GB
2
40GB
฿0.90
฿13
฿279
Community
8GB
4
60GB
฿1.70
฿25
฿529
Pro
16GB
8
100GB
฿3.20
฿48
฿999
Max
32GB
16
150GB
฿5.90
฿89
฿1,890
The disk in the "Disk included" column comes with the plan at no extra charge. Wanting more space than that means moving to a larger plan.
Topping up
Open the credits page
Go to /dashboard/credits — the "Credits" entry in the dashboard sidebar. The balance card carries the top-up button under the figure; pressing it opens a dialog. You know you are in the right place when the page heading reads Credits with three cards in a row beneath it.
Enter an amount and continue to payment
The amount field is pre-filled with the minimum; change it to whatever you want and press the continue button. Below the minimum, nothing navigates and the minimum-amount message appears under the field instead. Once the amount passes, your browser is sent out to the payment provider's checkout page, which the system picks for you at that moment.
Come back to the credits page and wait
After paying you are returned to the credits page with a "verifying your payment" strip at the top. This is the part worth knowing: the credit is often not there the instant you land. Your browser gets back before the provider's confirmation reaches us. The page checks for you 4 times, 3 seconds apart; when the credit lands you get a success message and the balance moves on its own with no refresh needed. If about 12 seconds pass with nothing, the message changes to say credits are added automatically once the provider confirms. That is not an error — wait a moment and refresh.
Check the top-up history table
Scroll down to the top-up history table. Your payment should be the newest row, with its date, amount and note. Once that row is there, the money is in the account and can start servers immediately.
Reading the three cards
Balance — what you can actually spend right now. It can go negative and is shown in the warning colour when it does, because a final usage charge can push past zero just before servers are stopped.
Total top-ups — 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.
This month's savings — the most misread number on the page. Its info popover defines it exactly: monthly cap minus the compute you actually used this month, summed across all your servers, counting hourly-billed servers only. In other words, "what running flat out to the cap all month would have cost, minus what you really paid". The percentage beside it is that gap against the summed monthly caps. 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. A freshly created server that has never been switched on shows the full cap as savings, which is normal.
Reading the chart and the two ledgers
Credit usage by server (30 days) is a single line: total baht spent per calendar day. Days with nothing running are filled in at ฿0 so the line stays continuous instead of breaking up. Hovering a point shows that day's total plus a per-server split. Below it, the per-server card sums each server's 30-day spend and then walks day by day with page controls.
Below that sit two tables that look alike and are not:
Table
What it holds
Columns
Top-up history
payments only — coupon and referral credit is left out on purpose
date · amount · note
Detailed transactions
every movement on the account, in and out
date · type · amount · balance · note
The detailed table is the real bill, because it carries the balance after each row, letting you trace exactly where the money went. Negative amounts are shown in the warning colour. The types you can see are:
Top-up — money in, from a payment or a redeemed coupon
Usage — hourly compute for a server; the most numerous rows by far, since they are written in short slices while a server runs
Adjustment — a manual correction by our team, for instance compensation after an incident
Refund — money returned to the account
Storage — the storage-side line item; normally your plan's included disk covers you, per the table above
AI assistant — spend on the in-dashboard AI assistant
Where the daily cap is, and is not, shown
This one sends people hunting. The daily cap is not shown on /dashboard/credits, and it is not shown in the resource-usage card on a server's page either. Those two tell you money spent and resources used, but never the ceiling.
Two places do show it: the cost summary shown while picking a server size (the line that says off or asleep is free, followed by the per-day cap and the monthly ceiling), and the rate table on , which gives the daily cap its own column for every plan. The size cards in the create wizard show only the hourly rate and the monthly cap — no daily figure there.
Coupons
Under the three cards is the coupon card. Type a code into the coupon field — it is upper-cased for you as you type — and press redeem. On success a message tells you how many credits arrived, and the balance, chart and ledgers all refresh themselves straight away. Coupon credit shows up as a top-up row in the detailed ledger. A malformed, expired, already-used or non-existent code each gets its own message. Under the form, a line notes that we hand codes out in our Discord, linking to the .
What happens when you run out
When the balance no longer covers the charges, running servers are stopped, and opening one shows an Out of credits banner saying it was stopped because the account ran out. Server owners get a shortcut to the credits page in that banner; team members see a different wording telling them to wait for the owner, 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 once you drop under ฿20, 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: . And if you have not opened a server yet, the current rates for every size are on .
Frequently asked questions
What is the minimum top-up, and why does ฿50 appear somewhere?
The real minimum is ฿20, enforced both in the browser and on the server. The ฿50 in the cost summary of the create wizard is a fixed illustrative amount used to work out how many hours that money buys — it is an example, not a floor.
Am I charged while the server is stopped?
No. Compute is metered only for the time a server reports itself running. Time spent starting up, asleep, or stopped is not billed.
What exactly is 'this month's savings'?
It is the plan's monthly cap minus the compute you actually used this month, summed across your servers and counting hourly-billed servers only. It measures the gap against running always-on — it is not a discount, a refund, or spendable credit.
Why can't I find the daily cap on the credits page?
Neither the credits page nor the resource-usage card on a server shows it. The daily cap appears in the cost summary when you pick a server size, and as its own column in the rate table on /pricing.
I paid but the credit hasn't arrived — what now?
The page checks for you 4 times, 3 seconds apart. If nothing has landed after about 12 seconds it tells you the credit will be added automatically once the payment provider confirms. Wait a moment and refresh; nothing is lost.
Do I lose my world if I run out of credits?
No. The server is stopped and its page shows an 'Out of credits' banner. Top up until the balance is positive again and start it as usual — a balance at or below zero is refused when starting a server or creating a new one.