Feature
Guided Provisioning Catalog
Form-driven provisioning for 90+ AWS and 60+ Azure services, with cost on the form, generated Terraform you can review, and import of the resources you already run.
Not every change starts from a repository. Sometimes a team needs a queue, a database or a cluster, and writing Terraform from scratch is the slow part.
Forms instead of boilerplate
The provisioning catalog has guided forms for more than 90 AWS services and more than 60 Azure services, from networks, compute and Kubernetes to databases, messaging, DNS and identity. Google Cloud and OCI have their own, smaller catalogs. Each form:
- asks for the settings that matter for that service, with safe defaults,
- lets you pick existing networks, roles and other resources from your account instead of typing IDs,
- shows a cost estimate while you fill it in.
Submitting a form produces Terraform/OpenTofu, priced and checked against policy packs, and it goes through approval before anything is applied.
Bring what you already run
Most teams already have infrastructure. OrchesTerra can adopt existing resources by importing them into Terraform/OpenTofu state, so they are covered by drift detection and approvals without being recreated.
Why it matters
The catalog gives teams that don't write Terraform every day a governed way to provision, and gives platform teams code they can still read and review.
FAQ
Is the generated code ours?
Yes. It is plain Terraform/OpenTofu you can keep in your own repository.
Which clouds have forms?
AWS and Azure have the largest catalogs; Google Cloud and OCI have smaller ones. Import of existing resources is deepest on AWS and Azure.