Platform Orchestrator
Drive standardization

The engine powering  your enterprise grade Internal Developer Platform. Regenerating app and infrastructure configurations with every git-push.
APP
ENV
PROVIDER
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

How it works

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

01
Read

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

how-it-works-read
02
Match

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.

how-it-works-match
03
Create

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.

how-it-works-create
04
Deploy

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

Extensibility

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