Orchestration
Describe your infrastructure as code and let UNIQCloud build it. The same definition produces the same environment every time — in development, in test, and in production.
Information
Orchestration is how infrastructure stops being a sequence of manual actions. Instead of clicking through a dashboard and hoping the next environment matches the last one, a team writes down what the environment should contain — networks, instances, volumes, load balancers — and the platform reconciles reality against that description.
On UNIQCloud this is done with Terraform (or OpenTofu) through the OpenStack provider. The definition lives in version control alongside the application, so an infrastructure change is reviewed, approved, and traceable in the same way a code change is. Rebuilding an environment after an incident, or standing up a copy of production for a test, becomes a repeatable operation rather than a project.
Repeatable environments
One definition produces the same result each time it is applied, so development, test, and production stop drifting apart.
Reviewable change
Infrastructure changes arrive as pull requests. What changed, who approved it, and when it was applied are all recorded.
Rebuildable after failure
If an environment has to be recreated, the definition is the recovery plan — no one has to remember how it was built.
Runs under its own identity
Automation authenticates with a dedicated application credential belonging to the project's service user, not a person's account.