These terms cover everything Paragon sells: virtual servers, bare metal, storage nodes, GPU instances, the add-ons bolted to them, and the panel you drive it all from. They are shorter than most hosting contracts because we sell one product to one standard and we do not write side letters. Section 9 is the one that costs money if you skim it.
We have been trading since 2019. Thirty-four sites, twenty-nine countries, one set of terms for everyone on them.
1. Acceptance
You accept these terms when you create an account, place an order, or use any part of the service, whichever happens first. Ordering on behalf of a company means you are telling us you can bind that company. Nobody checks that, because nobody here checks anything about who you are; the no-KYC policy (/no-kyc) sets out what that means and exactly where it stops.
If you disagree with any of this, the correct response is to not order. There is no negotiated variant for ordinary accounts, and for volume accounts the differences are commercial rather than legal.
2. What the service is
We sell compute on hardware we own and operate. Dedicated Zen 5 and Zen 4 cores, DDR5 memory with ECC across the EPYC line, Gen4 NVMe in mirrored pairs, and ports between 10 and 40 Gbit/s. Capacity is allocated once. A core you buy is scheduled against nothing else, and the same holds for your memory, your storage and your port.
Everything is unmanaged unless you have bought managed hardening. The host, the network, the power and the filtering are ours to keep running. What happens inside the instance is yours: the kernel, the packages, the configuration, and the backups you did or did not take.
Two operational points are worth knowing before you order.
- An instance may be migrated between hosts inside the same site for maintenance or after a hardware fault. Live migration is the default. Where a reboot cannot be avoided, notice follows the schedule in the SLA (/legal/sla).
- Stock is finite and counted per site. A plan available in one city says nothing about the next one. Pre-order sites bill only when the instance is actually delivered.
Hardware generations move. We do not shift a running instance onto a slower part, and when the replacement node happens to be faster you keep the price you were already paying.
3. Accounts and credentials
An account is an email address and a password. That is the whole of it. Passwords are stored as scrypt hashes, so we cannot read one, recover one, or hand one to anybody, including you.
Everything done through your account and your instances is your responsibility, whether or not you were the one who did it. Two-factor authentication is available and we would much rather you turned it on. Lose both the password and the second factor and the account is gone: there is no identity document on file to check you against, which is precisely the trade you accepted at sign-up.
Panel access is logged for seven days and then deleted. That log exists to catch account takeover and for nothing else. Full detail sits in the privacy policy (/legal/privacy).
4. Payment
We take cryptocurrency and nothing else. Settlement runs through OxaPay across roughly thirty assets, with the network fee shown before you commit to anything. Prices are quoted in euro and exclude whatever tax applies where you are. The euro figure is what the invoice is denominated in; the asset amount is derived from it at the reference rate quoted when the invoice is generated.
No cards, no bank transfers, no cash, no invoice-on-account. This is not a philosophical position about money. It is what keeps sign-up down to an email address, because a card drags identity in behind it.
Three things go wrong often enough to be worth writing down.
- An invoice paid short of the quoted amount stays open. The difference sits against it until you top it up or ask for it back.
- Overpayment lands on your account balance in euro at the rate at settlement, and it does not expire.
- A chain that confirms after the invoice window has closed still pays. The amount goes to your balance rather than the expired invoice, and you re-order against the balance in one click.
5. Term, renewal and cancellation
Terms run monthly, quarterly, six-monthly, annually or for two years, and the longer ones carry a published discount rather than one you have to ask for in a ticket. A term renews for the same length unless you cancel before it ends. Cancel from the panel and the instance runs to the end of what you paid for.
Renewal invoices issue seven days ahead. What follows an unpaid one is fixed, and we do not vary it per account:
| Day | What happens |
|---|---|
| 0 | Term ends, invoice unpaid, instance still running |
| +3 | Instance suspended, data intact, network off |
| +10 | Final notice to the email address on the account |
| +14 | Instance destroyed, storage wiped, addresses returned to the pool |
Nothing survives day fourteen. There is no hidden copy, a wiped volume cannot be un-wiped, and a request on day fifteen produces sympathy rather than data.
6. Suspension and termination for cause
Suspension happens for one of three reasons: an unpaid renewal, a breach of the acceptable use policy (/legal/aup), or a live security problem, most often a compromised instance flooding somebody else.
Where the cause is abuse, the escalation ladder in the AUP applies and you get notice plus a window to fix it. Four categories skip the ladder entirely: child sexual abuse material, attacks launched from your instance against a third party, phishing pages impersonating a real service, and malware command and control. Those come down first and get discussed afterwards.
Termination for cause ends the term without a refund. You keep the right to ask for whatever data can still be extracted, provided the request does not require us to restore something already wiped.
We can also terminate without cause on thirty days of notice, refunding the unused part of the term pro rata. It has happened twice in five years, both times because a site closed.
7. Your content, your responsibility
What sits on your instance is yours. You own it, you answer for it, and we do not look at it. Traffic is not logged, not sampled and not read; we route packets and that is the extent of our involvement.
The same fact cuts the other way. You are responsible for the legality of what you host under the law of the site you picked, and for what your users do with it. Choosing Chișinău because you liked the sentence on the location page is not legal advice, and it is certainly not legal advice from us.
Backups are yours unless you bought the off-node backup add-on. A snapshot living on the same node as the instance is a convenience, not a backup, and we will say so again the day the node dies.
8. Warranties and their limits
The service is provided as it is. We warrant three things: the hardware is what the catalogue (/hardware) says it is, capacity sold is not oversold, and the uptime commitment in the SLA is real and credited without being asked for.
Beyond that, no warranty. Not of uninterrupted service, not of fitness for your particular workload, not that data you never backed up survives a failure, and not that any given city stays in the fleet forever. Where local law gives you a warranty that cannot be excluded by contract, it applies and this section does not pretend otherwise.
9. Liability
Total liability, per account, across any twelve-month period, is capped at what you paid us in the three months before the event behind the claim. That is the entire cap.
Lost profit, lost revenue, lost or corrupted data, loss of goodwill, business interruption and any indirect or consequential loss are excluded however they arise. Service credits under the SLA are the sole remedy for downtime: automatic, no claim form, and not a floor to be argued upward afterwards.
Nothing in this section excludes liability for fraud, or for anything else that the applicable law does not permit to be excluded.
10. Indemnity
If someone brings a claim against us over what you hosted, what your users did, or how you used the network, you cover our defence and any award or settlement that follows. We will tell you about the claim promptly. Nothing gets settled without asking you first.
11. Changes to these terms
These terms change occasionally. When they do, the date at the top of this page changes with them and the diff is published in the journal (/journal). Material changes, meaning anything that touches price, liability, retention or what you are permitted to run, go out by email to every account thirty days before they take effect.
Carrying on after that date is acceptance. Would rather leave? Cancel inside the notice window and the unused term comes back pro rata. Changes are never backdated, and a change never applies to a term you have already paid for.
12. Governing law
These terms are governed by the law of the jurisdiction in which the operating entity is established, and the courts of that jurisdiction have exclusive competence over disputes arising from them. The entity and its jurisdiction appear on the contact page and on every invoice we issue. We are not typing a country name into a template that would go stale the moment anything about it changed.
Where mandatory consumer law in your own country gives you rights this section cannot remove, those rights win. That is not a courtesy on our part; it is how mandatory law works.
Before anyone files anything, open a ticket. Every dispute we have had in five years turned out to be billing arithmetic, and each of them took an afternoon.
13. Notices
Notice to you goes to the email address on the account. Keep it alive. It is the only channel we have, and an account with a dead address is an account we cannot warn before a suspension.
Notice to us goes to [email protected] for anything commercial, [email protected] for reports, and [email protected] for data requests. Email is the record. A message in a chat room is not notice, however quickly somebody answers it.
Should any part of these terms turn out to be unenforceable, the rest of it survives unchanged.