Skip to main content

VPS hosting

VPS-16

VPS-16 is the top virtualised tier — sixteen vCPU, thirty-two gigabytes of error-correcting memory, four-hundred-eighty gigabytes of NVMe storage, twenty terabytes of monthly transfer, eighty-gigabit DDoS shield, ninety-nine-point-ninety-nine-percent uptime SLA. It exists for projects that have outgrown VPS-8 but prefer a predictable monthly invoice to a fresh dedicated-server procurement cycle.

$128 per month

Order this plan → No KYC · No DMCA · Crypto only
  • 16 vCPU (AMD EPYC)
  • 32 GB DDR4 ECC
  • 480 GB NVMe SSD
  • 20 TB / month

Specification

Processor
16 vCPU (AMD EPYC)
Memory
32 GB DDR4 ECC
Storage
480 GB NVMe SSD
Bandwidth
20 TB / month
IPv4 addresses
1
IPv6
yes
Virtualization
KVM
Uplink
1 Gbps
Uptime SLA
99.99%
Operating systems
Ubuntu, Debian, AlmaLinux, Rocky, Fedora, Whonix

Who this plan suits

A regional newsroom consolidating multiple properties on one machine, an NGO IT lead running Nextcloud plus Matrix plus Mastodon plus a small WordPress multisite for member outlets, an investigative consortium running an indexed corpus over a hundred thousand documents with full-text search and aggressive caching, a video-archive serving a documentary back-catalogue. The tier is designed for the case where the workload is heavy enough to justify dedicated hardware in principle but the project prefers the simpler operational model of a virtual private server.

It is the right answer when the upgrade from VPS-8 is driven by capacity rather than by threat model. When the upgrade is driven by threat model — when shared hardware itself becomes a concern, when a side-channel attack from a co-tenant is part of the working threat picture — DS Lite at the same price point removes the hypervisor from the trust boundary and is the more honest answer.

Where this plan can be operated

VPS-16 deploys in Iceland or Switzerland. At the SLA tier where this plan sits — 99.99% uptime, the threshold at which downtime becomes itself a story rather than an inconvenience — both jurisdictions operate on infrastructure with redundant transit, redundant power, and operational practices that match the SLA. Iceland's hosting industry is concentrated in geothermally-cooled Reykjavik-area facilities; Switzerland's runs out of the Zurich-Geneva-Bern triangle on hydro-baseline power.

The practical jurisdiction question at this tier is which legal frame fits the project's adversary profile. For a regional newsroom whose adversary is a domestic-EU prosecutor, Iceland's geographical and treaty distance — backed by the IMMI reforms and outside the Five-Eyes intelligence-sharing arrangement — is the more conservative answer. For a research-team consortium whose adversary is more diffuse — civil-procedure attacks, disclosure orders from various jurisdictions — Switzerland's revFADP and the courtroom culture established by ProtonMail v UVEK are comparable. The threat-model framing for archives covers the choice in detail.

What the operator sees, and what it does not

Operationally, VPS-16 sits at the boundary where some customers ask whether dedicated hardware is the more honest answer. The KVM hypervisor's tenant isolation is robust and well-audited, but it is not a hardware boundary; the operator's mechanical view is the same as on lower tiers, but customers running workloads where hypervisor-side attacks are part of the threat picture should look at DS Lite instead. For everyone else — most workloads — VPS-16 delivers the same metadata posture as the smaller tiers at four times the working capacity.

What we cannot see remains the same: encrypted-disk contents at rest, in-memory secrets, application-layer logs you keep on the VM, the contents of your TLS streams. Payment in Monero, Lightning, on-chain Bitcoin, or cash; the annual prepayment route exists for projects that prefer to settle their financial surface once per year rather than monthly. The full operational framing is in our operating principles and the threat-model essay in the journal.

Jurisdictions

The offering is available from the jurisdictions listed below. The choice between them is made at the order step; this section discloses what the choice is, so the reader knows before the form opens.

Ordering this plan

The order step confirms the jurisdiction, the payment rail, and the contact detail before any service is provisioned. Questions about the plan or migration ahead of an order go through the contact form.

Order this plan →