Brokkr
If your cluster state lives in Git and changes on a deploy cadence, you already have the right tools; Argo CD and Flux do that job well, and Brokkr is not trying to replace them. Brokkr is for the other case, where what runs is decided at runtime rather than declared in a repository. Think of a PaaS or SaaS platform where a user picks services from a catalog and starts them on demand, or where every tenant gets its own set of resources stood up and torn down over its lifecycle. That work is dynamic and provisional; it does not fit a model where every change has to flow through a commit.
Brokkr is an environment-aware control plane for distributing those workloads across many clusters. The broker holds each running configuration as a “stack” of Kubernetes resources, and you create, update, and remove stacks programmatically through its API as your platform reacts to whatever your users are doing. A lightweight agent in each target cluster polls the broker and applies what it is given; because the agents reach out rather than wait to be reached, target clusters can sit behind firewalls or inside restricted networks and still receive workloads reliably. Each agent reports health and results back, so everything you have provisioned is visible from one place.
Routing is done with labels and annotations, so a stack lands on the cluster, or group of clusters, that should run it. Templates with JSON Schema validation let a platform expose a catalog of services and check a user’s parameters before anything is instantiated, and health tracking, webhook events, and a full API mean Brokkr sits inside your product rather than beside it.
Under the hood it is a Rust workspace. The brokkr-broker service runs the API and coordinates distribution; brokkr-agent does the polling and applying inside each cluster; shared models and utilities keep the two honest. Helm charts ship for both halves.
The name is Norse; Brokkr was the dwarven smith who forged the treasures of the gods.
Brokkr is available under the Elastic License 2.0. If you want to use it commercially or need help putting it to work, get in touch.