The Platform Orchestrator

The rules engine powering  your enterprise grade Internal Developer Platform. Driving standardization for the platform team and self-service for developers.


What it does

With every git-push, the Orchestrator interprets what resources and configurations are required for a workload to run, it creates app- and infrastructure configs based on rules defined by the platform team and executes them.

Diagram How DCM works

How it works

The Orchestrator follows a “Read”-”Match”-”Create”-”Deploy” pattern.


The Orchestrator reads the description of the workload and its dependent resources (the workload specification or Score file) from the CI pipeline.


The Orchestrator identifies the context (e.g. deployment to env of type staging). It then matches the correct rules (resource and configuration definitions) provided by the platform team.


After matching the abstract request from the developer to the rules and defaults provided by the platform team, the Orchestrator creates the app- and infrastructure configs.


Finally, the Orchestrator creates/updates the resources and deploys the workload. It can do this itself or in collaboration with a dedicated CD tool.

Git-push your first deployment


How it integrates with your setup

The Orchestrator connects to your CI pipeline and integrates with your existing toolchain through drivers. These are extension points to Infrastructure as Code (IaC) modules and cloud-APIs, like your AWS or GCP.

Integrating with all your tools
logo band
Start building your own enterprise-grade Internal Developer Platform with Humanitec
Platform reference architectures

Vetted templates for scalable platform architectures

Check platform template
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.