If you're on Rackspace right now, you've probably seen or heard about the invoice. Price hikes through 2026, some with as little as 30 days' notice, have a lot of us re-shopping infrastructure for the first time in years.
There are lots of sales and marketing comparison charts out there, so this is not that. It's nine Rackspace alternatives run through the questions that matter for the people provisioning this stuff: is there a real API, does terraform init work, is there a CLI or am I stuck clicking through a web console, and can I see the price before I talk to sales?
Rackspace still does some things well, its SLAs are solid and its support org is huge. This isn't a "Rackspace bad" post. I just wanted to look into what else is out there.
Rackspace competitors at a glance
| Provider | API | CLI | Terraform | Ansible | Starting price |
|---|---|---|---|---|---|
| Liquid Web | Yes | Yes | Yes | Not found | ~\$169/mo |
| phoenixNAP | Yes | Yes | Yes | Yes | 0.08/hr (~\$39/mo) |
| Hetzner | Yes | Yes | Yes | Yes | Quote-based |
| Kamatera | Yes | Yes | Yes | Yes | \$4/mo |
| OVHcloud | Yes | Yes | Yes | Community only | ~\$163/mo |
| Leaseweb | Yes | Not found | Yes | Not found | ~\$65/mo |
| AWS | Yes | Yes | Yes | Yes | Usage-based |
| Google Cloud | Yes | Yes | Yes | Yes | Usage-based |
| Microsoft Azure | Yes | Yes | Yes | Yes | Usage-based |
How I evaluated these
Four criteria, checked directly against each provider's docs and GitHub orgs:
- API access -- REST API available, documented, usable without a sales conversation
- CLI -- an official command-line tool, not just a web console
- Infrastructure as code -- an official Terraform provider and/or Ansible collection
- Pricing transparency -- published rates vs. quote-only
Here's roughly what "good" looks like on the IaC front, using Liquid Web's provider as an example:
No web console, no ticket, no waiting on a sales callback. That's the bar for everything below.
1. Liquid Web
An official CLI (LW CLI) built specifically for infrastructure automation, supporting YAML "plan files" for repeatable deployment tasks, comparable to a Chef cookbook or Puppet manifest. An official Terraform provider covers Cloud VPS, WordPress deployments, SSL via ACME, load balancers, and block storage. No official Ansible collection turned up in research.
Good fit if: you want CLI and Terraform-driven provisioning with managed support behind it, rather than a fully self-service platform.
Skip if: Ansible is a hard requirement. You'd be scripting against the REST API directly.
2. phoenixNAP
Bare Metal Cloud servers deploy in as little as 60 seconds via API or CLI, and phoenixNAP maintains official integrations for Terraform, Ansible, Chef, Puppet, and Pulumi. Pricing is published and starts at $0.08/hr(~$38.81/mo).
Good fit if: you want dedicated hardware managed the same way you manage cloud infrastructure, with a CI/CD pipeline doing the provisioning.
Skip if: you want a support team handling patching and monitoring for you. This is a self-managed platform.
3. Hetzner
REST API, official CLI, an official hcloud Terraform provider, and Ansible integration, all documented for their Cloud line. Pricing runs through a server configurator or a dynamic-pricing auction rather than a flat rate, but it's consistently one of the cheapest ways to get real infrastructure.
One caveat: this automation story is confirmed for Hetzner Cloud specifically. Their separately sold dedicated root servers aren't the same product line, and I didn't find the same level of API/IaC documentation for those.
Good fit if: you're comfortable running your own stack and want the most automation-complete option at the lowest price point.
Skip if: you specifically need it for dedicated (not cloud) hardware. Confirm which product line you're looking at.
4. Kamatera
API, an official CLI , an official Terraform provider, and an official Ansible collection . Kamatera even sells a pre-configured Ansible hosting product with Ansible already installed. Pricing is published and starts at \$4/mo for entry-level cloud servers, scaling up to 104-vCPU configurations.
Good fit if: you want the most complete IaC coverage at the low end of the pricing spectrum.
Skip if: you need dedicated (single-tenant) hardware specifically. Kamatera's core product is cloud/VPS, with a separate dedicated tier.
5. OVHcloud
Official CLI covering Public Cloud, Baremetal, VPS, and IAM, plus an official Terraform provider with bare-metal-specific guides for OS installation and iPXE boot configuration via API. Ansible support exists only through community-maintained collections, not an official one. Pricing starts around \$163/mo for entry-tier dedicated hardware.
Good fit if: you want CLI and Terraform access to actual bare-metal servers, not just cloud VMs.
Skip if: Ansible is your primary automation tool and you need vendor-maintained modules.
6. Leaseweb
REST API with public SDKs on GitHub, plus an official Terraform provider for Leaseweb Cloud. No official CLI or Ansible collection found. Physical, single-tenant servers with month-to-month contracts, starting around \$65/mo for entry configs (regional pricing varies; US-based configs run closer to \$194/mo).
Good fit if: Terraform is your primary IaC tool and you want single-tenant hardware without a long-term contract.
Skip if: you're standardized on Ansible or want a CLI for quick manual operations.
7. AWS
The baseline every IaC-native workflow gets compared against. EC2 Dedicated Hosts and Bare Metal instances are provisionable through the AWS CLI, SDKs, and a mature Terraform provider maintained by HashiCorp and AWS jointly. Pricing is usage-based and can get complex to model, but it's fully published.
Good fit if: you're already running IaC against AWS elsewhere and want to consolidate.
Skip if: you want predictable flat-rate billing. Usage-based pricing takes real modeling to forecast accurately.
8. Google Cloud
Similar profile to AWS: CLI (gcloud), full API, official Terraform provider. Bare Metal Solution is the relevant product for dedicated-hardware use cases, and it's built to integrate with the rest of Google Cloud, which matters most if you're already running BigQuery, Vertex AI, or other Google-specific tooling.
Good fit if: your stack already leans on Google's data or AI tools.
Skip if: you have no other reason to be in Google's ecosystem. The automation story doesn't meaningfully differentiate it from AWS or Azure on its own.
9. Microsoft Azure
Azure Dedicated Host rounds out the hyperscaler group, with the same CLI/API/Terraform completeness as AWS and Google Cloud. The clearest reason to pick it over the other two is existing investment in Microsoft's ecosystem (Active Directory, .NET, Microsoft 365 integrations).
Good fit if: you're already deep in Microsoft's tooling.
Skip if: you're choosing infrastructure independent of an existing platform commitment. On automation alone, this is a three-way tie with AWS and GCP.
Where to start
If IaC completeness is your top priority, phoenixNAP, Hetzner, and Kamatera cover Terraform, Ansible, and a CLI. If you need dedicated (not cloud/VPS) hardware specifically, narrow to OVHcloud, Leaseweb, or Liquid Web, since Hetzner and Kamatera's strongest automation support is documented for their cloud lines.
From there, provision a small test workload through each candidate's actual API or Terraform provider before committing. The docs page and the real provisioning experience don't always match, and you want to figure that out before a migration.
Top comments (0)