Clipper 8
$ 49 /month
- vCPU
- 4 × dedicated
- RAM
- 8 GB
- Storage
- 200 GB NVMe Gen4 SSD
- Transfer
- 20 TB
- IPv4 / IPv6
- 1 / /64 routed
High-frequency KVM
Clipper
Highest clock speeds we run. For latency-sensitive work.
Dedicated AMD Ryzen 9 7950X / EPYC 4004NVMe Gen4 (RAID-10)From $49/mo
Short answer
High-frequency dedicated cores (5.0 GHz turbo) with NVMe Gen4 and priority network queues. Built for workloads where single-thread latency decides the outcome: trading bots, matchmaking, real-time APIs.
Clipper plans
Clipper 16
$ 92 /month
- vCPU
- 8 × dedicated
- RAM
- 16 GB
- Storage
- 400 GB NVMe Gen4 SSD
- Transfer
- 30 TB
- IPv4 / IPv6
- 1 / /64 routed
Clipper 32
$ 174 /month
- vCPU
- 12 × dedicated
- RAM
- 32 GB
- Storage
- 800 GB NVMe Gen4 SSD
- Transfer
- 40 TB
- IPv4 / IPv6
- 1 / /64 routed
Clipper 64
$ 329 /month
- vCPU
- 16 × dedicated
- RAM
- 64 GB
- Storage
- 1.6 TB NVMe Gen4 SSD
- Transfer
- 50 TB
- IPv4 / IPv6
- 1 / /64 routed
Available in all 138 locations.
What Clipper is for
The Clipper line is the fastest thing we run: single-core turbo at 5.0 GHz, paired with NVMe Gen4 in RAID-10 and priority network queues. Below it, the Standard line trades peak clock for more cores per dollar. Clipper is the purchase when wall-clock latency on one thread matters more than core count — trading bots, matchmaking services, real-time APIs. If a workload is embarrassingly parallel, the lower line will often be the cheaper fit; if it ends with a line in a flame graph, Clipper is what you want.
People run Forex and crypto trading bots that must place orders inside a window; a few milliseconds of scheduling jitter is the difference between a fill and a miss. Game matchmaking services compute a ranking while players wait, and a real-time API response time is a product feature. The single-thread headroom plus low queue latency makes each request deterministically fast.
Choosing a size
Each size doubles RAM and storage while clock stays identical. Pick the vCPU count the concurrency needs — most latency-sensitive services are not CPU-bound in aggregate. If your response percentiles start climbing before the request rate explains it, you have bought too small: the next size up reduces queueing, not clock speed.
Specifications
| Plan | vCPU | RAM | Storage | Transfer | IPv4 | Monthly |
|---|---|---|---|---|---|---|
| Clipper 8 | 4 | 8 GB | 200 GB NVMe Gen4 SSD | 20 TB | 1 | $49 |
| Clipper 16 | 8 | 16 GB | 400 GB NVMe Gen4 SSD | 30 TB | 1 | $92 |
| Clipper 32 | 12 | 32 GB | 800 GB NVMe Gen4 SSD | 40 TB | 1 | $174 |
| Clipper 64 | 16 | 64 GB | 1.6 TB NVMe Gen4 SSD | 50 TB | 1 | $329 |
Best suited to
Forex & crypto trading botsLow-latency APIsGame matchmakingRenderingCompilation
In every plan, at every tier
| Included | What it means |
|---|---|
| Full root / Administrator access | Including custom kernels, nested virtualisation and raw sockets. |
| True KVM virtualisation | Not a container. Your own kernel, your own /proc, no shared namespace. |
| Custom ISO upload | Boot anything: OpenBSD, NixOS, Whonix, a hand-rolled image. |
| Out-of-band VNC console | Recover a broken network config without opening a ticket. |
| Routed IPv6 /64 | Not a single address — a whole subnet, at no cost. |
| Always-on DDoS mitigation | Up to 12 Tbps of edge scrubbing capacity, included at every tier. |
| Three free snapshots | Instant, and taken without pausing the instance. |
| Self-service reverse DNS | Set PTR records from the panel; essential for mail. |
| Full REST API and Terraform provider | Everything the panel does, scriptable. |
| No identity verification, ever | An email address you control is the only account identifier we hold. |
Frequently asked questions
Who is the Clipper line for?
High-frequency dedicated cores (5.0 GHz turbo) with NVMe Gen4 and priority network queues. Built for workloads where single-thread latency decides the outcome: trading bots, matchmaking, real-time APIs.
Are Clipper cores dedicated?
Yes. Each vCPU is a physical thread reserved for your instance, with no other tenant scheduled against it, so steal time is effectively zero.
Can I upgrade later?
CPU and RAM increase with a short reboot, and disk grows online. Moving down a tier requires a rebuild, so start smaller than you think you need.
Why would I pick Clipper over the cheaper line?
Because your workload ends with one core waiting on another instruction. The lower line shares its boost headroom differently; Clipper pins the fast cores to your process and prioritises your network queues. If a latency percentile is a contractual term or a trading edge, the premium is insurance against the next-nearest neighbour.
Can I use the whole core without contention?
Yes. Clipper plans are dedicated cores, not shared slices. The vCPU count maps to physical cores on the Ryzen 9 7950X or EPYC 4004, and the host is not oversubscribed for this line. The priority network queues sit in front of your traffic; other tenants on the box do not degrade your latency.