Skip to content

Plans and billing

Choosing a plan

A new network has no plan until it goes through checkout under Dashboard → Billing. That includes the Free plan. Until then no server can be added and no backend can connect.

The free trial

A paid plan starts with a 14-day free trial, taken at checkout. The trial has everything the plan it belongs to has. The dashboard counts it down in its last week.

Each account gets one trial, used by the first checkout for a network it owns. Choosing the Free plan counts as using it, so later checkouts are charged straight away.

When the trial ends it continues as a subscription. If you cancel it, the plan stays until the trial ends and the network then moves to the Free plan.

Plans

Plans are priced by peak concurrent players across the network, not by server count. Every paid plan covers as many servers as you want to point at it.

PlanPeak playersServersHistoryPrice
Free2013 days$0
Starter100Unlimited7 days$6.99/mo
Network300Unlimited30 days$19.99/mo
Pro1,000Unlimited90 days$49.99/mo
Scale3,000Unlimited120 days$129/mo
Enterprise3,000+Unlimited120 daysContact us

Annual billing is twelve months for the price of ten, and is available on every paid plan.

Every plan runs every detection. The tier changes the player ceiling, how far back you can read, which features are included, and how quickly support answers.

History and retention

History is how far back a plan reads detections, replays and analytics. Retention is how long the evidence is kept, and it is 120 days on every plan including Free.

The two are deliberately different. Nothing is deleted when it leaves your history window, so upgrading shows the whole window of the new plan straight away, already filled in — there is no waiting for it to build up again. Evidence older than 120 days is deleted for everyone.

What each plan includes

Detection, alerts, auto-bans and Discord alert delivery are on every plan, including Free — except that the Free plan is flag-only: it detects and alerts exactly as a paid plan does but never kicks or bans.

FeatureFrom
Discord slash commandsStarter
Live spectateNetwork
Custom webhooks (non-Discord URLs)Network
ReplaysAny paid plan or trial

On the Free plan, alerts arrive after a short random delay, name the category (Movement, Combat, World, Packets) rather than the check, and pause for an hour for a player who has set off several different checks. Detection itself is identical.

Public server verification

Free networks are verified by checking that they run a real public server: the public address you enter during setup has to answer a Minecraft server ping from the internet, and a few different players have to have joined in the last week. Thorium checks as soon as you save the address, then every 5 minutes.

A Free network that is still unverified seven days after it was created stops receiving alerts until it is verified or upgraded. Local and private-network servers need a paid plan.

One account can own one network without a paid subscription.

When a trial or subscription ends

The network moves to the Free plan. Coverage is not withdrawn: detection keeps running on one backend, with a ceiling of 20 peak concurrent players. The Free plan has no expiry.

Backend allowances

Free covers one connected backend at a time. Paid plans cover as many as you want, on as many servers as you want.

The allowance counts what is connected, not what is registered, so on Free the first backend to connect holds the slot and any others are refused until it disconnects. Nothing is deleted by going over it, and choosing a plan lets the rest straight back in.

A backend that stops cleanly releases its slot immediately. One that crashes releases it within 45 seconds, when its connection stops being counted — so a free network whose backend dies can see up to 45 seconds of refusals while it restarts. The plugin retries with a backoff and reconnects on its own.

Going over the player ceiling

Exceeding your plan’s peak-player ceiling does not stop detection. If a network runs over on three days inside a 30-day window, replays, live spectate and bot commands pause 72 hours after the first warning. Detection continues throughout.

Changing plans

Dashboard → Billing. Upgrades apply immediately.

One token for the network

Backends authenticate with the network token, on the servers tab of your network in the dashboard. It is one value for every backend, and each backend says which server it is through server-name in its plugin config.

That is what lets one server run several backends. A minigame network scaling pods up and down uses the same token and the same server-name on all of them, and they appear as one server running several backends rather than as a new server per pod.

Rotating the token disconnects every backend on the network until each has the new value.