Browse by cloud provider
Every cloud we cover, with its verified module count. Each provider hub lists plug-and-play Terraform/OpenTofu modules (and Ansible roles where available) - statically validated and publish-checked, live-tested where marked. Prefer to slice the other way? Compare the same service across clouds.
How to read a provider hub
The count beside each cloud is the number of published modules and roles that target it: 901 across 19 clouds today, 341 of them live-tested. Every one of them passed the same static checks before it was listed (parse, lint, a security scan), so the count is a count of checked modules, not of listings. A hub sorts its modules by what they provision and marks each with the verification level its record supports; a live-tested module was applied to a real account in that cloud, its outputs asserted against, then destroyed with the teardown confirmed, and its receipt is fetchable without an account.
The largest hubs (AWS, Google Cloud, Azure) carry the live-tested majority because those are the accounts the live lane runs against. The alternative clouds (Oracle, Alibaba, Huawei, Tencent, IBM and the rest) are listed at the static level until a sandbox account for each comes online, and their pages say so on every module rather than implying a test that did not run. 228 Ansible roles for EL 10 sit in the multi-cloud hub, each live-tested in a systemd container.
Two other ways in: the solutions pages compare one service (DNS, Kubernetes, object storage) across every cloud that has a module for it, and the verification page explains each level and what a receipt contains.