Compatible clouds
Where Flexpair runs.
Flexpair is Terraform-native and provider-agnostic by design — not an AWS-only architecture. Every cloud listed below has already passed the technical baseline our bootstrap pipeline requires: a Terraform compute provider that accepts a cloud-init/user-data payload at instance creation. The table is sorted by Terraform Registry downloads over the last 12 months.
The key handoff iscloud-init: Terraform passes user data when the VM is created, and cloud-init turns that into the first-boot configuration inside the instance.
In plain English: this is amulticloudroadmap, with AWS and Microsoft Azure shipped; OVHcloud/OpenStack next.
Tier values verified against the Terraform Registry. Download counts are the last 12 months, fetched from the public Terraform Registry API at build time. Spotted a stale entry? Drop us a line and we will fix it.
What the tiers mean
Terraform Registry tiers, in plain language.
HashiCorp groups providers in the public Terraform Registry into three tiers based on who maintains them. The tier tells you who you call when something breaks, not how good the provider is.
- Official
Maintained by HashiCorp itself. These cover the hyperscalers and a handful of core services HashiCorp owns end to end (AWS, AzureRM, Google Cloud, Kubernetes, Helm). Bug reports and security issues go to HashiCorp; release cadence is predictable and the docs are first-party.
Examples:
hashicorp/aws,hashicorp/azurerm,hashicorp/google,IBM-Cloud/ibm.- Partner
Built and maintained by the cloud vendor (or an organisation they sponsor) under HashiCorp's Technology Partner programme. The vendor signs the provider with their own GPG key and commits to a published support model. In practice this is the tier most regional and European clouds sit in.
Examples:
hetznercloud/hcloud,scaleway/scaleway,ovh/ovh,oracle/oci,exoscale/exoscale.- Community
Published by individual maintainers, community groups, or vendors who have not joined HashiCorp's partner programme. No formal SLA from HashiCorp; quality and release cadence vary. A vendor publishing under their own namespace does not automatically make a provider "Partner": the OpenStack project, for example, sits here despite being maintained by an active community.
Examples:
terraform-provider-openstack/openstack,Telmate/proxmox.
For Flexpair the tier matters mostly as a stability and longevity signal. Official and partner providers ship reliably enough that we can pin versions, run Dependabot bumps, and promise a working terraform applyacross releases. Community providers we treat case by case.
Reference:HashiCorp's official tier definitions.
Need a cloud we have not shipped yet?
If your procurement is locked to a specific provider, tell us. Customer demand is the fastest way to move a cloud up our queue.
Talk to us