Guides
The catalogue publishes evidence for every module it sells. These guides are about reading that evidence and acting on it: which rung of verification your use actually needs, how to weigh one cloud against another for the same job, and the part most vendors leave out, which is what a green badge still does not tell you.
Today that is 183 published modules, of which 116 were really applied to a cloud account, verified and destroyed. The rest are statically validated and say so. Which of those you should accept is a judgement about your own risk, and the first guide is about making it deliberately.
Choosing a module by its evidence
Four rungs of verification, what each one actually costs to produce, and how to decide which one your use needs. Includes the case nobody else writes down: when a statically validated module is the right choice, and when it is not.
Comparing the same service across clouds
How to use the solution hubs to weigh one cloud’s managed database, Kubernetes or load balancer against another’s, what is genuinely portable between them, and where the comparison stops being useful.
What our verification does not prove
The limits, stated plainly. A passing live test says a module applied and tore down cleanly in one account, on one day, with one set of inputs. Here is everything that leaves open, and what you still have to do yourself.
Reference, not guidance
If you already know what you want and need the specifics, the reference material is separate: every module and the evidence it carries, installing through the Terraform registry protocol, and the read-only catalogue API.