Best Low-Cost VPS Providers for IoT

The criteria, recapped

This comparison applies the same criteria covered in detail in How to Choose a VPS for an IoT Project: KVM virtualisation, dedicated rather than purely burstable CPU where possible, NVMe storage, honest bandwidth, and snapshot/backup availability. Headline price alone is a poor comparison axis on its own, which is exactly why that guide exists, but it’s still worth a direct, honest look at where several well-known budget providers actually land.

LumaDock

KVM-based, AMD EPYC hardware, NVMe storage throughout. The smallest plan (2GB RAM, 2 vCPU) runs from around £3.77/mo on annual billing or £4.53/mo paying month-to-month, the exact figures used throughout this site’s own setup guides, since LumaDock is the provider every screenshot and command on this site has actually been tested against. Current live pricing is worth checking directly, since it does change.

Hetzner

A long-established German provider with a strong reputation for price-to-performance, particularly within Europe. Entry-level shared-vCPU plans (the CX line) start from around €3.49-4.59/mo for 2 vCPU and 4GB RAM with NVMe storage, with all-inclusive pricing covering traffic, IPv4/IPv6 and basic DDoS protection at no extra charge, a genuine strength worth noting since some budget providers charge separately for these. Hetzner’s main limitation for some IoT projects is more limited datacentre geography (concentrated in Europe and a smaller US/Asia footprint) compared to providers with a wider global spread.

Contabo

Known specifically for unusually generous RAM and storage allocations at low prices, plans from roughly €4.50-7/mo commonly include 4 vCPU and 8GB RAM, noticeably more than comparably priced plans from other providers. The trade-off, worth knowing honestly: independent benchmarking consistently shows Contabo’s per-core CPU performance behind Hetzner’s at similar price points, and some plans still use SATA SSD rather than NVMe, worth checking the specific plan rather than assuming. For IoT workloads that are RAM-hungry but not CPU-intensive (a database holding a lot of time-series history, for example), this trade can still make sense.

Comparison at a glance

Provider	Entry price (approx.)	Entry specs	Storage	Notable strength
LumaDock	~£3.77-4.53/mo	2 vCPU, 2GB RAM	NVMe	The provider this site’s own guides are tested against
Hetzner	~€3.49-4.59/mo	2 vCPU, 4GB RAM	NVMe	Strong per-core performance, all-inclusive pricing
Contabo	~€4.50-7/mo	4 vCPU, 8GB RAM	NVMe or SATA, varies by plan	Most RAM/storage per pound at the lowest price points

All three meet the core criteria from the provider-selection guide: KVM virtualisation, and NVMe on at least their standard plans. Prices above are approximate and change over time; checking each provider’s current pricing page directly before committing is always worth the few minutes it takes.

Why this site uses LumaDock specifically

Worth being transparent about this: LumaDock is the provider every setup guide on this site has actually been built and tested against, which is why its screenshots, commands and pricing are used as the default example throughout. That’s a genuine, practical reason to start there if you want the closest match to what these guides describe, not a claim that it’s objectively superior to every alternative on every axis. The criteria in this guide and the provider-selection guide apply regardless of which specific provider you ultimately choose.

Providers worth a mention but outside this comparison’s scope

DigitalOcean and Vultr are both well-known, reputable options with solid documentation and predictable pricing, generally sitting a little above the providers compared here on price for comparable specs, in exchange for a more polished control panel and wider feature set (managed databases, more extensive marketplace images) that most projects on this site don’t specifically need. Worth knowing they exist as a slightly higher-cost, higher-polish alternative if budget isn’t the primary constraint.

Frequently asked questions

Is the cheapest plan from any of these providers always the right choice?

Not necessarily, refer back to the sizing table in VPS for IoT: The Complete Guide for what your specific combination of services actually needs. The cheapest plan that meets your real requirements is the right choice, not the cheapest plan available regardless of fit.

Do these providers all support WireGuard out of the box?

WireGuard support depends on the kernel, not the provider specifically, since it’s a kernel-level feature on modern Linux distributions. Any KVM-based provider running a current Ubuntu LTS image, which covers all three compared here, supports it without issue.

How often should I re-check pricing across providers?

Budget VPS pricing does shift periodically, sometimes upward as covered by industry pricing trend reporting through 2026, sometimes with new entry tiers introduced. An annual check, or whenever a renewal is approaching, is a reasonable cadence without becoming a constant distraction.

Is it risky to choose a smaller, less well-known provider over a major one?

Worth real consideration, financial stability and company longevity matter for infrastructure you’re depending on long-term. Checking how long a provider has operated, who owns them, and independent reviews (with appropriate scepticism toward affiliate-driven “best of” lists) is reasonable due diligence before committing.

Can I switch providers later without rebuilding everything from scratch?

Yes, see the migration approach covered in How to Choose a VPS for an IoT Project: stand up the new server, replicate configuration, run in parallel briefly, then cut over. Standard, open-source software throughout this site’s guides makes this considerably easier than it would be with proprietary, provider-specific tooling.

Testing a provider yourself before committing long-term

Reviews and comparison tables, including this one, are a reasonable starting point but shouldn’t be the final word, since pricing and performance both shift over time and individual experience can vary. The most reliable way to confirm a provider suits your specific project: provision a real instance on whatever monthly or hourly billing option is available, run the sysbench CPU benchmark and the basic provider-selection checklist covered in How to Choose a VPS for an IoT Project, and actually install your intended stack, MQTT and Node-RED at minimum, before committing to annual billing or a longer-term plan.

What “low cost” actually means at this end of the market

It’s worth being honest about what separates these budget providers from significantly more expensive enterprise cloud platforms (AWS, Azure, Google Cloud) beyond price alone. Budget VPS providers generally offer less polished management consoles, fewer managed add-on services (managed databases, serverless functions, and similar), and typically less extensive global datacentre coverage. For the kind of self-hosted, single-VPS projects covered throughout this site, none of these gaps matter much, you’re running your own software stack regardless, not relying on a provider’s managed services layer. The price difference reflects genuinely different target markets, not simply “you get what you pay for” in every dimension.

A note on currency and billing

Several providers compared here bill primarily in EUR or USD rather than GBP; LumaDock is a notable exception, billing natively in GBP among other currencies, worth factoring in if currency conversion fees or exchange rate fluctuation matter for your budgeting, particularly on annual commitments where a meaningful exchange rate shift over the billing period is a real, if usually small, consideration.

Do any of these providers offer a free trial?

Policies vary and change over time; some offer short money-back guarantees rather than a true free trial. Checking the current terms directly on each provider’s site before committing, rather than assuming, is worth the few minutes it takes.

Is it worth paying more for a provider with 24/7 live chat support specifically?

For most projects on this site, ticket-based support with a reasonable response time is adequate, given how infrequently genuine emergencies arise once the initial setup is hardened correctly. Live chat becomes more valuable for anything genuinely business-critical where downtime has immediate financial consequences.

Should I worry about a budget provider’s long-term financial stability?

It’s reasonable due diligence, particularly for a provider you haven’t heard of before. Established providers with a multi-year track record and clear, public company information carry less of this risk than newer, less transparent operations, worth a quick check before committing to anything beyond a short initial trial period.

Datacentre location: more choice than it first appears

All three providers compared here operate multiple datacentre locations, worth choosing deliberately based on where your devices actually are, rather than defaulting to whichever region happens to be selected first during signup. For UK-based projects specifically, a Western European location generally offers the best latency without meaningful cost difference compared to other EU regions, while providers with a UK-specific datacentre, where available, can shave a small amount of additional latency for genuinely latency-sensitive applications, though as covered in the provider-selection guide, this rarely matters much for typical IoT telemetry.

A note on IPv4 address scarcity and pricing

Worth knowing as a minor but real cost factor: IPv4 addresses have become a genuinely scarce, priced resource industry-wide, and some providers now charge a small additional monthly fee for a dedicated IPv4 address, with IPv6-only or shared-IPv4 options offered as the cheaper default. For most projects on this site, a single dedicated IPv4 address is worth the modest extra cost for simplicity (reverse DNS, certain firewall and routing scenarios are simpler with a dedicated address), but it’s worth checking whether a specific plan includes this by default or charges separately.

Do these providers all offer the same level of DDoS protection?

No, this varies meaningfully and is worth checking explicitly rather than assuming, since basic DDoS protection is included by some providers (Hetzner, for example) and offered as a paid add-on or more limited by others. For most projects on this site, basic protection is sufficient, but it’s worth confirming rather than discovering a gap during an actual attack.

Should I choose based purely on the lowest price for my exact required specs?

Not purely, the criteria throughout this guide and the provider-selection guide (CPU allocation honesty, support quality, snapshot availability) matter alongside price. The cheapest plan meeting every genuine requirement is the right target, not the cheapest plan regardless of whether it actually fits.

Do any of these providers specialise specifically in IoT hosting?

Not specifically; all three are general-purpose VPS providers. No major provider markets itself purely as an “IoT VPS host”, which is fine, since the actual requirements (KVM, NVMe, honest CPU allocation) are general infrastructure qualities, not IoT-specific features a specialised provider would offer that a general one wouldn’t.

Is it reasonable to mix providers across different projects rather than standardising on one?

Yes, and it’s not unusual, different projects sometimes have genuinely different priorities (one favouring raw price, another favouring performance), and there’s no strong reason to force every project onto the same provider if their actual needs differ.

A practical decision shortcut

For most readers of this site facing this choice for the first time, a reasonable shortcut: start with LumaDock specifically, since every other guide on this site has been tested directly against it, removing one layer of “does this command actually match what I’m seeing” uncertainty during your first setup. Once comfortable with the basics, comparing Hetzner and Contabo against your actual experience, rather than against a review page, is a far more informed comparison than trying to choose blind between three unfamiliar options on day one, and switching later costs little once you know what you’re actually looking for.

Why doesn’t this comparison include AWS Lightsail or similarly priced offerings from the big cloud platforms?

Those products exist and are reasonable options, generally sitting closer in price to Hetzner and LumaDock than to AWS IoT Core’s metered pricing covered elsewhere on this site. They’re left out of this specific comparison mainly because the providers covered here are the ones most commonly used and discussed for exactly this kind of small-scale self-hosted IoT project.

How this guide’s recommendations might age

Budget VPS pricing is genuinely competitive and shifts more often than most other parts of this site’s content; a provider offering the best value today may not hold that position in a year, and a newer entrant not covered here at all might emerge as genuinely competitive. The criteria in this guide, KVM virtualisation, NVMe storage, honest CPU allocation, transparent published specifications, are the durable part worth remembering even as specific prices and specific providers’ relative standing shift around them. Anyone reading this guide some time after it was written should treat the named providers as worked examples of how to apply the criteria, not as a permanently fixed verdict, and is encouraged to re-run the comparison against current pricing using the same framework rather than assuming nothing has changed.

This is, in a sense, the whole point of teaching a method rather than just handing over a single answer: prices move, criteria for evaluating them don’t, at least not nearly as quickly.