Billing
Prepaid balance, hourly charges with a monthly cap, and what happens when the balance runs out.
Odinex is prepaid. You top up a balance in euros, and your resources are paid for from it, hour by hour. There are no invoices to pay afterwards.
Topping up
Top up in the console under Billing by card (payments are processed by Stripe). The console shows the minimum and maximum amount and any payment processing fee before you pay; a fee, if there is one, is listed separately on the receipt. You get a receipt for every payment.
Automatic recharge. You can save a card and let Odinex top up a fixed amount whenever the balance falls below a threshold you choose. After three failed attempts in a row it turns itself off and you are notified.
How charges work
Every billable resource has an hourly price and a monthly price (see Pricing and the public
/pricing and /server_types endpoints).
- Every started hour counts. A resource is charged for each hour or part of an hour it exists. A server that existed for five minutes is charged one hour.
- Monthly cap. In a calendar month (UTC), a resource is never charged more than its monthly price. The hourly price is the monthly price divided by 625, so a resource that exists the whole month reaches the cap after 625 hours and is free for the rest of the month.
- Servers are charged while they exist, also when powered off, because their disk, IP addresses and capacity stay reserved. To stop paying for a server, delete it (take a snapshot first if you want to keep the data).
- Per GB: volumes are charged by their size and snapshots by their size in GB.
- Backups add 20 % to the server's price.
- Primary IPv4 addresses and floating IPs are charged separately; IPv6 primary addresses are included.
- The price is fixed when a resource is created. A price change applies to new resources, and to existing ones when they change type or size.
- Traffic: each server type includes traffic (see the type's
included_traffic).
The balance is charged as time passes. In the console, Billing → Usage shows the cost of the current month so far,
resource by resource, and a forecast for the whole month; the same data is in GET /billing/usage. At the start of a
month a statement for the previous month is issued.
Creating resources needs balance. To create a resource, your balance must cover at least one hour of all your
resources, the new one included. Otherwise the request fails with 402 insufficient_funds, and the error details show
the balance and the required amount.
When the balance runs low or out
Your account is never blocked without warning. With the default settings the timeline is:
| When | What happens |
|---|---|
| The balance lasts less than 72 hours, then less than 24 hours at the current cost | Email warning (once for each threshold) |
| The balance reaches zero or below | Email with the time your servers will be stopped |
| 24 hours after the balance went negative | The account is suspended: all servers are powered off and locked, and no new resources can be created (403 account_suspended). Email with the deletion date |
| 3 days before deletion | Final warning email |
| 14 days after suspension | All billable resources are deleted, including servers, volumes, snapshots, floating IPs and load balancers, even if they have delete protection. This cannot be undone |
Resources keep being charged while they exist, also while the account is suspended.
To get out of it, top up so that the balance is positive again. The suspension is lifted immediately; your servers stay powered off until you start them.
Keep the balance above your monthly costs, or turn on automatic recharge, if your services must not be interrupted.
A disputed card payment (chargeback) also suspends the account until the dispute is resolved.