Buy in volume, bill your own way
The same nodes and the same network at a rate that reflects how much of it you take. You own the customer relationship and you are their first line. We stay behind you, in writing, at engineer speed.
Who this is for
If you run more than a dozen instances on behalf of other people and would rather they never saw our name, this is the arrangement. Everybody else does better with the catalogue and an annual cycle.
Most resellers here are agencies hosting client sites, small hosts who do not want to own hardware, and a handful of software vendors who ship an appliance and need somewhere for it to live. The common shape is many small instances, one invoice, one technical contact.
This is not a franchise, and there is no branded control panel to hand your customers. What you get is wholesale pricing, an API that creates and destroys instances without a human in the path, and a support relationship that assumes you already know what a route table is.
What it costs
The reseller discount applies to the effective rate after any cycle discount. It does not stack with launch pricing at a new site.
The commitment is a floor rather than a forecast. You agree a minimum monthly spend for three months and are billed for whichever is higher, the commitment or the actual usage. Moving up a tier takes effect the month you cross it; moving down waits for the end of the term.
Entry is €750 a month on a three-month term. Below that the annual and biennial cycles in the public catalogue beat anything we would write for you, and we will say so rather than sell you a contract you do not need.
| Committed monthly spend | Discount | Applies to |
|---|---|---|
| €750 to €2,499 | 10% | Every plan, add-on and licence. |
| €2,500 to €9,999 | 15% | Every plan, add-on and licence. |
| €10,000 and above | 20% | Every plan and add-on. Windows licences are passed through at cost. |
None of this changes the technical product. A reseller instance is the same instance on the same node, with the same SLA, the same unmetered port and the same 7-day refund on a first order.
The API
A plain REST interface over HTTPS, JSON in and JSON out, with tokens you scope yourself. It does everything the panel does, because the panel is written against the same endpoints.
Instances
Create, resize, rebuild, snapshot, restore and destroy. Creation returns an identifier immediately, and the instance is reachable in a median of 47 seconds, the same figure as an order placed by hand.
Networking
Attach and detach addresses, edit RDNS, delegate an IPv6 /48, and read the current filtering state during an attack. Everything on the network tab of the panel has an endpoint behind it.
Billing
List invoices, fetch a PDF, top up a balance, read the running spend for the month. Useful when you rebill by usage rather than per instance.
Webhooks
Signed callbacks on provisioning, migration, incident and invoice events. Retried with backoff for 24 hours, then dropped and logged where you can see that it was dropped.
Tokens and limits
Tokens scope per project and can be read-only. The rate limit is 120 requests a minute per token with a burst allowance, and the response headers tell you where you stand rather than leaving you to guess.
Versioning
One major version at a time, with 12 months of notice before anything breaking. Endpoints are deprecated in the changelog before they are removed, never after.
White-label, and where it stops
You can put your name on nearly all of it. The parts you cannot are the parts where somebody else needs to know who actually operates the machine.
Yours
Your invoice, your brand, your support hours, your pricing. Hostnames and RDNS are yours to set. Nothing we send ever touches your customer, because we hold no address for them and do not want one.
Ours
The network the addresses sit on is registered to us, so an abuse complaint arrives here and we answer it. The panel is not rebrandable and a white-label panel is not on the roadmap.
Do not claim
That you own the hardware, that you operate the sites, or that you hold capacity nobody has sold you. Say you run on premium AMD hardware across 34 locations, which is true, and stop there.
One consequence worth understanding: when your customer breaches the acceptable use policy we come to you, and your obligations towards us mirror theirs towards you. Passing the complaint on unchanged is a perfectly acceptable answer.
Support when you are the first line
Your customers have no ticket queue here. They contact you, you triage, and whatever you cannot resolve reaches us with the diagnosis already done. In practice about one ticket in twenty that you receive ever gets that far.
The trade is that we answer you faster and at a different level. Reseller tickets skip the general queue, the median first response stays under 11 minutes at any hour, and the reply comes from somebody who can reboot a hypervisor rather than somebody reading from a script.
What we will not do is speak to your customer directly, even when you ask and even when it would obviously be quicker. Every arrangement where that happened ended with the customer emailing us instead of you, which is not the business either of us signed up for.
Escalation
One address, watched around the clock, for anything affecting more than one of your instances at once. Use it sparingly and it stays fast.
Maintenance notice
Resellers get planned-maintenance notices 14 days ahead instead of 7, which leaves a week to schedule around it before your customers ever hear about it.
Capacity holds
Tell us what you expect to need in a given city and it gets reserved for 30 days. Sites marked low stock move quickly, and a hold is the only reliable way to plan a migration into one.
Incident credit
SLA credits land on your account automatically rather than on request. Whether you pass them through to your customer is your decision and your paperwork.
Reseller questions
You can buy as many instances as you like at catalogue prices with no agreement whatsoever, and plenty of people do exactly that. The discount is the only thing the commitment buys.
No. Everything is prepaid in crypto, resellers included. Credit means invoicing a legal entity, and invoicing a legal entity means knowing which one, which is the whole thing we do not do.
Instances suspend rather than delete, data is held for 14 days, and one ticket restores everything. Chasing you for a day is preferable to destroying a hundred of your customers over a mempool delay.
You can bring your own space on metal and on EPYC from the E-32 upward at sites where the upstream permits it. We do not assign a contiguous block from ours, because addresses are allocated per instance per site.
Yes, with a token type that provisions nothing and bills nothing. It returns the same objects and the same error shapes, including the ones you hope never to see in production.
Send the numbers, get a quote
How many instances, in which cities, at what size. A written quote comes back the same working day from an engineer, so the answer is occasionally that the standard annual cycle would serve you better.