[ TAKEDOWN-RESISTANT ]
Built so a complaint cannot end your project
Resistance is not one feature, it is four decisions stacked on top of each other: the jurisdiction, who owns the metal, how disposable the public surface is, and how fast the origin can move. Get all four right and a takedown stops being an existential event and becomes an entry in someone else's log file.
- Jurisdiction chosen for legal posture, not rack rate
- Owned hardware — no upstream reseller to lean on
- Snapshot and relocate between regions with no fee
- Proxy-friendly design so the public face stays disposable
[ RATE CARD ]
DMCA-Ignored VPS pricing
Public pricing, charged monthly or by the hour from the prepaid balance. Unmetered transfer, dual-stack addressing and mitigation are standard.
Safe-harbour placement · EPYC 9354P · DDR5 ECC · Gen4 NVMe in RAID-10 · dual-stack, unmetered
[ HOW IT WORKS ]
The four layers, in the order they fail
Most projects die at the second layer without ever reaching a legal question. The provider is a reseller, someone leans on its upstream, and the machine goes dark for reasons the provider itself cannot control. Owning the hardware removes that entire failure mode, which is why we buy and rack our own rather than reselling a larger cloud.
The third layer is architectural and it is the one you control. Keep the origin in the strongest jurisdiction you can tolerate and put a disposable proxy in front of it. Complaints, scanning and attacks reach the layer you can rebuild in five minutes, not the machine holding your database. The fourth layer is portability: snapshot, redeploy elsewhere, point DNS at the new address. With a low TTL that is a two-minute operation.
See VPS plans
[ WHY NODMCAVPS ]
What resistance does not mean
It does not mean immunity. A court with jurisdiction over the building is followed, criminal law applies wherever the metal physically sits, and the categories in our Acceptable Use Policy are removed on sight. Anyone selling you an absolute is either lying or running the kind of operation that gets emptied by a police van.
What it does mean is that the routine, automated, high-volume complaint — the one that generates ninety-nine percent of hosting suspensions — has no path to your infrastructure. That is the failure mode that actually happens to people, and it is the one worth engineering against.
Full specs & options[ INCLUDED WITH EVERY PLAN ]
What you always get
[ FAQ ]
Frequently asked
Can I move a server between regions later?
Yes. Snapshot it and redeploy in any other region from the client area. There is no migration fee and no re-verification, because there was never any verification to redo.
Do you support putting a proxy in front of the origin?
It is the pattern we recommend most often, and there is a full guide to it. Deploy the origin in a safe-harbour region, a small proxy close to your users, and firewall the origin to accept only the proxy address.
What is the single most common way people still get taken down?
Historical DNS. The domain pointed at the origin at some point, passive-DNS archives remember it permanently, and the proxy in front is decorative from then on. Always start with an address that was never published.
[ DEPLOY ]
Built so a complaint in 45 seconds.
Top up, choose a region, deploy. No ID, no card, from $4.50/mo in crypto.