No vanity counters. Capabilities that match how offshore operators evaluate a host.
Your kernel space, your stack. We do not micromanage lawful software choices within the AUP.
Netherlands, Iceland, Romania, Switzerland, Russia, China — pick for legal context and routing, not marketing flags.
Four tiers from Outpost to Fortress with published vCPU, RAM, disk and transfer.
Pay without a card. Invoice lifetime and rate lock handled by the payment rail.
Documented path for notices. We do not pretend courts do not exist.
Clear bans on malware, spam, phishing, DDoS and CSAM — so free speech stays defensible.
Every plan ships with full root on the virtual machine. That is not a marketing checkbox; it is a division of responsibility. Below the guest we handle the hypervisor, the network, and the physical host. Everything from the kernel up is yours: your distribution, your firewall rules, your package choices, your users. Pick from the images we publish — recent Ubuntu LTS, Debian, AlmaLinux, Rocky, Fedora, or rolling Arch — and rebuild whenever you want.
The honest catch is that root is a duty as much as a privilege. We do not silently patch your packages, rotate your keys, or lock down SSH for you, because doing so would mean touching a system we told you was yours. The security baseline of the guest is your job: disable password login, keep the kernel current, and do not run services you are not watching. We keep the platform underneath solid; you keep the box on top defensible.
Region is a first-class product decision here, not an afterthought buried in a dropdown. You choose the jurisdiction at order time, and each option has a dedicated page explaining the legal and network context rather than waving a flag at you: Netherlands for EU connectivity and open-internet culture, Iceland for its privacy-statute reputation, Romania for EU-east routing, Switzerland for neutral-jurisdiction framing, Russia for Eurasian routing, and China for APAC proximity. The full map lives on locations.
Treat jurisdiction as one input in a risk model, not as a cloak. A country's reputation for privacy or free speech shapes how legal pressure arrives, not whether it can. Region is chosen at order time; migrations afterward are handled case by case through support, since moving a live server across jurisdictions is a real operation, not a toggle.
Checkout is a crypto invoice, denominated in USD and rate-locked for the life of that invoice, so the amount you see is the amount you pay even if the market moves while you confirm. We do not run our own chain, and the coins available are whatever the payment rail quotes at checkout — check the invoice screen rather than trusting a fixed list here, because rails change and we will not print a promise we cannot keep.
There is no card, no billing name, no address form. The only identifier we need is a working email, because that is where server details and your ticket go. One operational reminder: on-chain payments are irreversible, so send the exact invoiced amount to the exact address shown. When a refund is warranted it is handled as a separate payout to an address you provide — see pricing and Terms for how that works.
Complaints are read by a human and answered, not auto-actioned and not silently ignored. When a notice arrives about your server, the default is to forward it to you so you can respond — we do not null-route first and explain never. Our full approach, including how counter-notices are treated where the jurisdiction supports them, is documented on the DMCA policy page, and the intent-versus-limits framing lives on DMCA-ignored VPS.
"DMCA-ignored" here means we do not treat a US-style takedown notice as an automatic kill switch for lawful content — not that law stops applying. A valid legal order from a competent authority is a different thing from a form-letter complaint, and we treat it that way. The point of running a real abuse desk is that it keeps upstreams calm and your server up; hosts that advertise pure indifference are the ones that get whole ranges null-routed.
The acceptable-use policy is public on purpose. Free-speech hosting is only defensible when the line between speech and crime is drawn where everyone — customers, upstreams, and us — can read it. The banned categories are the ones that are genuinely indefensible and that trigger fast escalation: CSAM, malware and its distribution, phishing and credential theft, spam operations, and DDoS or other network attacks launched from our infrastructure.
Publishing those lines is what makes the rest of the stance credible. A host that stays vague about what it forbids cannot honestly claim to defend lawful speech, because it has reserved the right to drop anything at any time. We would rather be specific and occasionally unpopular than vague and quietly arbitrary. If your project stays inside the AUP, you know where you stand; if it does not, we would rather you find that out before you pay.
Plans run from Outpost at $19/mo through Bastion, Citadel, and Fortress, each with published vCPU, RAM, NVMe, and transfer. What is not in the base plan is a paid add-on, and the add-on menu is deliberately cheap and itemised so you scale exactly what you need: extra RAM at $2 per GB, extra vCPU at $3 per core, additional NVMe in 10 GB blocks at $0.08 per GB, and additional IPv4 at $1.50 each. Optional automated backups, a filtered-transit option, and a priority support queue are flat monthly toggles.
The design goal is that nothing is free beyond the plan base and nothing is padded. You are not paying a "premium offshore tax" for resources — you are paying list price for RAM, cores, disk, and IPs, and you can see every line before you confirm. The full breakdown, including yearly billing, is on pricing.
Anti-hype means naming the things we refuse to sell, because in this niche the missing promises tell you more than the loud ones.
There is a paid filtered-transit add-on, billed as a flat monthly toggle. We describe it as a filter, not as invincibility, and we deliberately do not advertise a mitigation capacity figure — printing a number we cannot verify would be exactly the kind of claim this site refuses. If absorbing large volumetric attacks is core to your project, evaluate the add-on against your real threat model rather than a headline.
No. The entry plan is Outpost at $19/mo, and nothing beyond a plan's published base is free — every add-on is billable. That is deliberate: a genuinely free offshore tier attracts exactly the abuse volume that gets IP ranges null-routed, which would cost paying operators their uptime. Paying a real price for real resources is part of what keeps the platform stable.
The base plan includes its published vCPU, RAM, NVMe disk, transfer allowance, one IPv4, and full root. Everything else is an itemised add-on: extra RAM ($2/GB), extra vCPU ($3/core), extra NVMe ($0.08/GB in 10 GB blocks), additional IPv4 ($1.50 each), plus optional backups, filtered transit, and priority support as flat monthly toggles. You see every line before you confirm on the pricing page.