Skip to content

Pricing

Priced Around the Work You Automate.

Three plans, built around execution volume, estate size and the governance you need — not around seats. Commercial terms are not finalised yet, so you will find the structure of the model here and a concrete quote one conversation away.

Why there are no numbers on this page. Pricing is not finalised. Publishing a figure we would have to change — or a usage allowance we have not committed to — would waste your time during evaluation. The dimensions below are real; the values are deliberately blank until they are agreed.

Starter

For a first automation project — one team, a focused set of workflows, and the integrations behind them.

Best for: Teams automating their first few operational workflows

Includes

  • Workflow builder with registered action catalogue
  • AI request classification and context gathering
  • Core ticketing, virtualization and monitoring connectors
  • REST API and outbound webhooks
  • Full run history with inputs, outputs and approvals
Request pricing

No card required. We will scope it with you first.

Most chosen

Growth

For providers running automation across customers, sites and platforms, where multi-tenancy and approvals matter.

Best for: Hosting providers, cloud providers and MSPs operating at scale

Includes

  • Everything in Starter
  • Tenant isolation for credentials, policy and run history
  • Per-tenant approval rules and maintenance windows
  • Custom roles with separated author, approve and run permissions
  • SSO with group-to-role mapping
  • Shared workflow library with versioning
Request pricing

No card required. We will scope it with you first.

Enterprise

For organisations with deployment, residency, change-control or audit requirements that need to be designed in.

Best for: Enterprise IT, regulated industries and large multi-site operators

Includes

  • Everything in Growth
  • Self-hosted execution runners inside your network
  • Data residency and model-handling options
  • Binding to your change-management process
  • Configurable audit retention with export
  • Custom connector development
Contact sales

No card required. We will scope it with you first.

Compare

What each plan covers

Allowance values are described rather than numbered until the model is finalised. Everything structural — roles, deployment, approvals, retention — is accurate.

Comparison of StackHeal Starter, Growth and Enterprise plans across scale, platform, security and support dimensions.
DimensionStarterRequest pricingGrowthRequest pricingEnterpriseContact sales
ScaleHow much automation the plan covers.
Automation workflowsHow many distinct workflow definitions you can publish and run.Entry allowanceExpanded allowanceNegotiated
Monthly execution volumeWorkflow runs per month, including scheduled, event-driven and API-triggered runs.Entry allowanceExpanded allowanceNegotiated
Managed assetsServers, instances and devices that workflows may act on.Entry allowanceExpanded allowanceNegotiated
Tenants or customer accountsSeparate customer scopes with isolated credentials, policy and run history.Single tenantMulti-tenantUnlimited tenants
Team membersNamed users with platform access. Roles determine what each can author, approve and run.Small teamExpanded teamNegotiated
PlatformCapabilities available to your workflows.
Native connectorsMaintained connectors for ticketing, virtualization, monitoring and backup systems.Core connectorsFull connector catalogueFull catalogue plus custom connectors
REST API and webhooksProgrammatic workflow triggering, run status and definition management.IncludedIncludedIncluded
AI request interpretationClassification, context gathering, runbook matching and reply drafting.IncludedIncludedIncluded, with model and residency options
Security and governanceControls, identity and deployment.
Approval policiesNamed approvers, thresholds and timeout behaviour per action, tenant or environment.Basic approvalsPer-tenant policiesChange-control integration
Roles and permissionsSeparation of authoring, publishing, approving and running by role.Standard rolesCustom rolesCustom roles and delegated administration
Run history retentionHow long immutable run records are retained and exportable.Standard retentionExtended retentionConfigurable retention with export
SSO and directory syncSAML or OIDC single sign-on with group-to-role mapping.Not includedIncludedSSO with directory sync
Deployment modelWhere the control plane and execution runners run.StackHeal cloudStackHeal cloud, regional optionsSelf-hosted or private execution runners
SupportHow you get help.
SupportChannels, hours and response expectations.Email supportPriority supportNamed contact
OnboardingHelp getting your first workflows designed, connected and verified.Documentation and guidesGuided onboardingImplementation support

Values such as “entry allowance” and “expanded allowance” are placeholders for figures that have not been finalised — not hidden limits. Ask for the current numbers.

Getting a quote

Four questions and we can price it.

We would rather ask than guess. These are the inputs that actually move the number.

Request pricing
  1. 01

    How many assets would workflows act on?

    Servers, instances and devices in scope — not your whole estate, just the part automation would touch.

  2. 02

    Roughly how many runs per month?

    Ticket volume in the categories you want automated, plus scheduled work like patch campaigns and backup reconciliation.

  3. 03

    How many tenants or customer accounts?

    Separate customer scopes with isolated credentials and policy. This is the dimension that distinguishes Starter from Growth.

  4. 04

    Any deployment or residency constraints?

    Whether you need private execution runners or a fully self-hosted deployment, and where data must stay.

What we will not do

Quote a price before understanding your estate, publish a discount we have not agreed, or promise a saving percentage. If you need a business case, we would rather help you measure your current volumes than hand you someone else's numbers.

Pricing questions

Something not covered here? Ask our team.

Before you commit

Scope a proof of concept instead of a trial.

A generic trial tells you very little about operations automation, because the value is in how a workflow handles your systems and your policy. We scope proofs of concept around one or two of your real request types.

Tell us what you want to automate.

Share your estate size and the request types you handle manually today. We will come back with a plan recommendation and a concrete quote.