Skip to content
StackHeal

Platform

Deployment models

StackHeal cloud, private execution runners and self-hosted deployment.

The control plane and the execution runners can be placed independently, which is what makes the platform workable for organisations with strict network or residency requirements.

StackHeal cloud

Control plane and runners hosted by StackHeal. Your systems are reached over authenticated outbound connections from the runner. Simplest to operate; suitable where your platform APIs can be reached from a managed network path.

Private execution runners

Control plane hosted by StackHeal; runners deployed inside your network. Runners connect outbound to the control plane and reach your systems locally, so credentials and command execution never leave your environment. No inbound firewall rules are required.

Self-hosted

Control plane and runners both deployed in your environment. Used where data residency, air-gapping or compliance requirements make a hosted control plane unsuitable. Specifics — orchestration, update process, model access — are agreed during implementation.

Choosing

Most providers start on StackHeal cloud and move to private runners as they widen the set of systems automation touches. Enterprises with existing residency commitments usually start at self-hosted. Talk to our team about which fits your constraints.

Scope of this documentation

This page describes how the StackHeal platform is designed to behave. This website does not execute workflows or connect to infrastructure — see the repository README for the backend integration points.