Use cases

These are some of the core use cases for the New Orchestrator. It is a partial list intended to give you an idea of how the Orchestrator may improve your processes.

Leverage your TF estate #

You have created an estate of Terraform or OpenTofu modules in your Organization and wish to make a curated set of these available to your project teams.

The Orchestrator lets you define a centralized catalog of modules available for self-service execution by your projects. Module code continues to be maintained in the same Git repositories with no code change is required.

Automate complex resource setups #

The Orchestrator lets you predefine complex resource setups which can be deployed automatically behind the scenes. Roll out security, IAM, or other supporting components whenever your projects request a thing they need, and shield them from the complexity involved.

The Orchestrator will always provide full visibility into all resources created, so your developers stay in control without having to master every technology they need to use.

Environment promotion and ephemeral environments #

Because the Orchestrator adheres to a familiar project/environment structure, it is easy to build a deployment cadence from development through to production. By adding a few lines to your existing CI/CD setup, the Orchestrator performs environment deployments, promotions, rollbacks, and spins up ephemeral environments for PR and testing flows.

Achieve compliance and governance #

The Orchestrator lets you expose a curated selection of modules to your projects. Bring in your security and governance teams to enhance and validate those modules and uphold the practices you require.

Because the Orchestrator will apply new module versions as your projects continously deploy, watch your latest standards roll out through your infrastructure without requiring separate tickets or manual toil.