Host my own runner for my own building block definitions
complete
Jelle den Burger
I am a platform engineer working at a large organization. I currently use the shared runner provided by meshStack to run my building blocks, which is also used by other platform teams.
I would rather run my own runner infrastructure and register it with meshStack. This could work similarly to how GitHub does it with their GH Action Runners
Update:
Please note that private runners operated by meshcloud are available as a solution to have runners in a private networking configuration.
See https://docs.meshcloud.io/meshstack.building-blocks.private-runners for more details.
However, it is currently not possible to
self-host the runner on your own without support by meshcloud as we have not made the necessary APIs available yet
have separate runners for separate platform teams as requested in this feature request. Runners are currently shared between all building block definitions in a meshStack
Jelle den Burger
updated the status to
complete
🎉 This is now shipped!
You can now host your own runner for your Building Block definitions using a Docker image — giving you full control over where your Building Blocks execute.
How to get started:
- The meshStack UI walks you through the setup step by step — just follow the wizard when configuring your Building Block runner.
- Prefer reading docs first? Everything you need is here: https://docs.meshcloud.io/guides/platform-ecosystem/how-to-run-building-block-runners/
Open source & transparent:
We've also open-sourced the meshStack runner, so you can inspect exactly what's running on your infrastructure: https://github.com/meshcloud/building-block-runner
Coming up next — Kubernetes Run Controller:
If you're interested in the Kubernetes controller variant (which we use ourselves to run meshStack runners), that's coming in the future. Head over here to vote and stay in the loop: https://feedback.meshcloud.io/feature-requests/p/self-hosted-run-controllers
Thank you for this request — we hope this gives your team the control and transparency you were looking for. 🚀
Janny the AI Product Manager
**Update: Significant runner improvements shipped in meshStack v2026.24.0**
What shipped in this release:
- Unified Building Block Runner— all five separate system-managed runners (Terraform, GitHub Workflow, GitLab Pipeline, Azure DevOps, Manual) are now consolidated into a single unified runner. This simplifies runner management and reduces operational overhead.
- Correct setup instructions per runner type— the runner detail page now shows the correct setup instructions for your specific runner type, not just Terraform-specific instructions.
- Accurate connection status for new runners— newly created runners now correctly show as disconnected until they connect for the first time.
Work on self-hosted runner capabilities continues. We will post further updates as they ship.
Janny the AI Product Manager
Update — meshStack v2026.24.0 (June 2026)
We made significant progress on the runner infrastructure in this release:
- The five separate system-managed runners (one per implementation type: Manual, Terraform, GitHub Workflow, GitLab Pipeline, Azure DevOps Pipeline) have been consolidated into a single unified run-controller runnerthat handles all implementation types.
- You will now see one managed runner in your runner overview instead of five.
- Existing building block definitions have been automatically migrated to the new unified runner.
If you reference runner UUIDs via the API or Terraform provider, please update to the new unified runner UUID:
98520496-627d-43e6-82da-ce499179ff3f
. The latest meshStack Terraform provider handles this migration automatically.More self-hosted runner capabilities are in progress.
Jelle den Burger
updated the status to
in progress
We will start working on this and plan to launch it within the next 1-2 months.
J
Johannes Rudolph
Please note that private runners operated by meshcloud are available as a solution to have runners in a private networking configuration.
See https://docs.meshcloud.io/meshstack.building-blocks.private-runners for more details.
However, it is currently not possible to
- self-host the runner on your own without support by meshcloud as we have not made the necessary APIs available yet
- have separate runners for separate platform teams as requested in this feature request. Runners are currently shared between all building block definitions in a meshStack
We are looking at both of these features for this request, since self-hosting is a necessary pre-requisite for enabling separate platform teams to each have their own runners.