Dedicated CPU VPS with Reserved Cores, from $75/month

Dedicated CPU means your virtual cores are reserved exclusively for your VM, with no scheduling shared across tenants on the underlying physical hardware. There is no oversubscription, no burst credits to exhaust, no scheduler pause when neighbor VMs get busy. Your cores run your workload at full speed every cycle.

This is different from "shared CPU" or "shared vCPU" plans (DigitalOcean droplets, Linode shared instances, our own Shared CPU Cloud Cubes) where the physical cores are scheduled across multiple VMs. For most web workloads shared scheduling is fine because traffic is bursty. For sustained CPU load, compliance environments, and predictable p99 latency, dedicated cores are required.

The most common signs: sustained CPU usage above 70-80%, p99 response times spiking under load while p50 stays flat, scheduled jobs taking longer than expected during peak hours, write-heavy OLTP databases where commit latency varies in ways that break SLAs, or CPU-intensive workloads (ML inference, video transcoding, ETL pipelines, batch processing) that hold cores at 100% for minutes or hours.

Compliance is the other major trigger: PCI-scoped data, HIPAA-adjacent workflows, contracted SOC 2 environments, or any obligation that prohibits shared CPU scheduling. Auditors increasingly flag oversubscription as a risk surface, and dedicated cores remove that surface entirely.

The CPU model is the only thing that changes. Shared CPU schedules virtual cores across multiple tenants. Dedicated CPU reserves cores exclusively for your VM. Memory, storage, network, and the entire operations stack are identical between the two families, and both are fully managed with everything included.

The other practical difference is sizing. Shared CPU runs from 1 to 64 GiB RAM with vCPU counts that scale with plan size. Dedicated CPU runs from 8 to 128 GiB with exactly one reserved +3.00 GHz core per 8 GiB. At the same RAM, Dedicated gives you fewer cores for slightly more money (two dedicated cores at $135/month versus six shared vCPUs at $121.67 at 16 GiB), which is the price of guaranteed cycles.

No. Dedicated CPU plans have no oversubscription, no burst credits, and no scheduler-induced throttling. You can sustain 100% CPU usage on every reserved core for as long as your workload requires, without performance degradation. This is the entire point of the family.

The only thing that can throttle a workload here is the workload itself: poorly tuned application code, lock contention in databases, or single-threaded bottlenecks that cannot use additional cores. Those are application-level issues, not infrastructure issues, and we help diagnose them when they show up in monitoring.

Yes, with caveats. The CPU isolation that compliance frameworks (PCI DSS, HIPAA, SOC 2) often require is fully met by Dedicated CPU plans. Reserved cores remove the shared-scheduling risk surface that auditors flag at most cloud hosts.

That said, compliance is a holistic process, not a single checkbox. We provide the infrastructure controls (dedicated cores, hardened firewall, IDS, audit logs, encrypted backups) and procedural support (incident response, change management, documented patching cadence) that an auditor will check. We are happy to discuss your specific compliance scope before you order, so reach out if you have a regulated workload.

Yes, this is one of the primary use cases. OLTP workloads (financial transactions, ticketing, inventory, real-time analytics) need predictable commit latency. Shared scheduling causes commit times to vary in ways that break SLAs. Dedicated cores keep commit latency flat under sustained writes.

For typical OLTP sizing: DC-32GB or DC-64GB handles MySQL or Postgres workloads with millions of rows and hundreds of concurrent writes per second comfortably. We tune InnoDB or Postgres WAL for throughput, configure replication if needed, and keep an eye on long-running queries through our monitoring stack.

Probably yes. If your CPU usage stays consistently under 30% and you are not on Dedicated for compliance reasons, you are paying for exclusivity you are not using. Shared CPU Cloud Cubes deliver the same management with more scheduled vCPUs for slightly less money, and shared scheduling will not affect your workload at that utilization level.

The downgrade is a simple server move, free of charge, scheduled at a time you choose. We monitor your CPU patterns and will proactively suggest a downgrade if we see you are consistently under-utilizing reserved cores. We would rather you pay for the right plan than the bigger plan.

Yes, every Dedicated CPU plan includes daily snapshots with 7-day retention plus dual offsite backups, no extra charge. Snapshots are block-level and fast to restore. Offsite backups run to two independent destinations, PBS and S3, so your data survives even if the server hardware fails.

Because the two offsite copies are independent of each other and of the server itself, there is no single point of failure in the backup chain. Compliance customers can request extended retention beyond the included 7 days, billed by storage.

Yes. Free migration is included on every Dedicated CPU plan, regardless of where you are coming from (cPanel host, Plesk host, AWS EC2, DigitalOcean Premium AMD, Linode Dedicated, Vultr, anywhere). Our team handles the move: sites, databases, mail accounts, DNS records, SSL certificates, the whole stack.

For Dedicated CPU migrations we plan extra carefully because workloads at this scale are usually production-critical. We do a test migration first, run it under load to verify performance, then schedule the final cutover at a low-traffic window. Most customers experience zero downtime during migration.

We do not throttle, we do not bill you in surprise overage charges, and we do not suspend your service. Instead, we monitor your resource usage and reach out when you are consistently using 80% or more of your allocated RAM, CPU, or disk. We will recommend either an upgrade or a tuning pass to optimize your existing usage.

For network transfer, the included allowance is generous (20 to 320 TB per month depending on plan size) and most workloads never come close. If you do exceed it, we charge a small per-GB fee that we communicate before applying.

Yes, in either direction. Upgrades within the Dedicated CPU family (8GB to 128GB) usually happen with zero downtime: we add the resources to your existing server in place. Downgrades require a brief reboot to apply the new resource limits, scheduled at a time you choose.

Moving between families (Dedicated CPU to Shared CPU, or back) involves a server move, which our team handles for you. There is no fee for upgrades or family changes, you just pay the difference for the new plan.

30-day money-back guarantee on all Dedicated CPU plans. If you sign up and decide we are not the right fit within the first 30 days, we refund your full first payment, no questions asked, no exit fees, no contracts to cancel.

After 30 days, plans are billed monthly or annually depending on your selected cadence. You can cancel anytime through your account dashboard. Annual plans get pro-rated refunds for unused months on cancellation.