IDrive Compute

What IDrive Compute actually is

Let us start with the fact that should drive every other decision on this page: IDrive Compute has been discontinued. The service shut down on 15 August 2023, and IDrive's own documentation site now carries the notice on every page. PCMag's review carries an editor's note confirming the date and stating that unused prepaid and postpaid resources from before 31 July 2023 were refunded. You cannot buy this product today. We are keeping the entry in our /category/vps-providers comparison because the pages are still live, the brand still trades on the IDrive name, and people still land here from old links — but the honest answer to "should I host here" is no.

What the product was, for context: a VPS platform IDrive launched in March 2021 as an edge-computing play, initially with a network of 20 US edge locations and NVMe-backed Linux virtual machines. By the time it shut down, the footprint had consolidated to nine data centers — Los Angeles (LA3), Portland/Hillsboro (PDX1), Chicago (ORD1), Miami (MIA1), Manassas (VA1), Dublin (DUB1), London (LHR1), Frankfurt (FRA1), and Paris (CDG1) — spanning the US and four European countries. Each location offered virtual private servers, bare metal servers, shared and dedicated CPU instances, NVMe block storage (at most sites), application stacks, networking, and a cloud firewall.

The instance line was conventional and sensible: shared-CPU plans for general workloads, and dedicated-CPU plans split into CPU-optimized, memory-optimized, and storage-optimized shapes. Instances were Linux-only — CentOS, Ubuntu, Fedora, openSUSE Leap, and Debian were the supported distributions — with live snapshots, instance cloning, scheduled image backups as an add-on, expandable block storage volumes that survived instance deletion, and native IPv6 at no extra charge. Management was a single web console for instances, volumes, snapshots, backups, users, and billing. It was a credible, if unremarkable, small-provider VPS built on the same recipe as Vultr or Linode, with IDrive's backup heritage layered on top.

Pricing: what you really pay

You pay nothing, because the service no longer sells plans — but the published price list is still readable and worth recording, both for former customers reconciling invoices and for anyone judging whether the shutdown was a pricing failure. It was not, particularly. The shared-CPU list started at $5 per month for 1 vCPU, 1 GB RAM, 40 GB NVMe, and 1 TB of monthly transfer (with a promotional $3.75 first-payer rate), and scaled linearly: 2 vCPU/4 GB/80 GB/4 TB at $20 per month, 4 vCPU/8 GB/160 GB/5 TB at $40, 8 vCPU/16 GB/320 GB/6 TB at $80, and the top shared tier at 32 vCPU/64 GB/1,280 GB/12 TB for $320 per month. Prepaid yearly plans advertised 50% off the first year ($30 instead of $60 for the entry shape), and postpaid hourly billing ran at $0.0074 per hour for the entry instance — an honest pay-as-you-use model with no hidden charges, as IDrive put it.

Against the value leaders we track on /benchmarks, that entry price was fine but not exceptional: Hetzner's CX22 gives you 2 vCPU and 4 GB for €4.35 per month, and Vultr's regular-performance tier was in the same band as IDrive's $5 shape. IDrive Compute's real argument was location — nine sites including four European cities — and the NVMe-plus-block-storage configuration at every tier. For US and EU edge workloads in 2021-2023, that was a reasonable offer.

The important pricing lesson from the shutdown is different: when a compute product is a side line for a company whose main business is backup, plan pricing is not the risk. Continuity is. Prepaid balances were refunded, which is the right behavior and deserves credit, but anyone who had architected on these instances still had to migrate. That is the same risk you take with any sub-scale compute provider, and it is why we weigh "will this company still sell VMs in three years" in our ratings.

Performance & infrastructure

The infrastructure claims were respectable on paper: NVMe SSD storage throughout, enterprise-grade hardware in "modern and secure facilities" with physical security controls, a 99.99% uptime figure advertised for instances and block storage volumes, and a distributed edge network positioned for latency-sensitive applications — real-time communication, remote monitoring, content delivery, cloud gaming. Native IPv6 support at no extra charge was ahead of several bigger names at the time.

What we cannot do is vouch for any of it with numbers. We never benchmarked IDrive Compute instances in our own sysbench, fio, or iperf3 runs — our /benchmarks covers Hetzner, DigitalOcean, UpCloud, Vultr, and Linode shapes only — and third-party testing was thin. VPSBenchmarks lists comparisons involving IDrive Compute plans, but published sample sizes were small and the service existed for barely two years. There is no independent, multi-year reliability record to examine, which for a discontinued product is a permanent gap rather than one we can close by waiting.

The security and compliance story leaned on IDrive's corporate posture rather than the compute platform itself: firewall controls per instance, private IP options, and the parent company's SOC 2 Type 2 certification and data-center partners. There was no published DDoS scrubbing capacity, no ISO or PCI certification specific to the compute line, and no bug bounty or public status history we can point to.

Where it falls short

Everything falls short now, because the service is gone. But even setting the shutdown aside, the weaknesses were the usual sub-scale-provider set. Nine locations sounds broad until you notice the documentation and the homepage disagreed about the exact list — the homepage carousel listed Amsterdam and Madrid among locations that do not appear in the data-center directory, which counted nine sites without them. Small inconsistencies like that are a tell about how much attention the web estate was getting.

Feature depth never matched the leaders. No Kubernetes offering, no object storage integration beyond the IDrive family, no load balancers or private networking tiers beyond basics, no Windows images, and backups — the one thing you would expect IDrive to bundle — were an add-on rather than an included plan feature. Snapshot and backup storage pricing was never clearly published on the main pricing page. Support was the shared IDrive support apparatus rather than a compute-focused team, and response quality for VPS issues was not something we would have wanted to depend on.

And then the discontinuation itself: a two-year-old service switching off with a few months' notice, refunds issued but migrations forced on every customer. Whatever the internal economics, the effect on customers was the same. We also noticed the support surface never grew compute-specific depth: documentation lived on a separate help-center domain, status communication was minimal, and there was no public postmortem or migration guide of the kind a provider with a serious compute business would publish when switching off a platform. Refunding balances was decent of IDrive; giving customers a year of runway instead of a few months would have been better.

Who should pick this

Nobody, in the direct sense — you cannot. If you arrived here looking for IDrive-branded infrastructure, the practical routes are: IDrive e2 if what you actually need is cheap S3-compatible object storage (we review it separately and it remains active), the core IDrive backup product for data protection, or a mainstream VPS provider from our /category/vps-providers comparison for compute. For former IDrive Compute customers, we would move to providers with multi-year public track records and pricing that does not depend on a side-business subsidy.

The one audience this entry still serves is the cautionary one: if you are evaluating a small or mid-size compute provider today, weigh corporate focus and continuity alongside the spec sheet. A great $5 instance from a company whose revenue engine lives elsewhere is a position you should hold for reversible workloads only.

Key takeaways

• IDrive Compute was discontinued on 15 August 2023; IDrive's own docs confirm it and PCMag notes unused balances were refunded.
• In its two-year life it ran nine data centers across the US, Ireland, the UK, Germany, and France, with NVMe-backed Linux VPS and bare metal at most sites.
• Published pricing was conventional value-tier: 1 vCPU/1 GB/40 GB NVMe/1 TB at $5 per month, scaling to 32 vCPU/64 GB/1,280 GB/12 TB at $320 per month, with hourly postpaid from $0.0074/hr.
• Advertised 99.99% uptime for instances and block storage, native IPv6 included, snapshots and cloning built in; backups were an add-on.
• No independent long-term performance or reliability record exists; we never benchmarked it ourselves.
• Continuity, not price, was the failure mode — treat sub-scale compute providers accordingly.

Sources

• https://www.idrivecompute.com/
• https://www.idrivecompute.com/location.htm
• https://www.idrivecompute.com/pricing.htm
• https://www.idrivecompute.com/instance.htm
• https://docs.idrivecompute.com/hc/en-us/sections/5598415245853-Compute
• https://blog.idrive.com/2021/03/18/idrive-releases-idrive-compute-a-vps-hosting-and-edge-computing-service-for-developers-enterprises/
• https://pcmag.com/reviews/idrive-compute
• https://en.idrive.com/online-backup-company