Licensing and usage

RunsOn uses a single company-scoped license across both Flex and Fleet. You do not buy a separate license per product when the same legal entity owns or controls the AWS accounts and GitHub organizations using RunsOn.

Configure the license key

Set the LicenseKey CloudFormation parameter when you create or update the stack — see CloudFormation parameters. It can be a plain string or an SSM parameter ARN.

Set license_key on the Fleet Terraform module:

module "runs_on_fleet" {
  source  = "runs-on/runs-on/aws//modules/fleet"
  version = "v3.1.0"

  license_key = var.runs_on_license_key
  email       = var.alert_email
  # ...
}

The license key is sensitive input. Keep it in your secret-management path rather than committing it to source control.

Usage reporting

RunsOn usage is measured by monthly runner volume (runners launched) across Flex and Fleet, grouped by license.

Running above your current tier does not block CI. Short spikes are never charged. If usage exceeds your tier for two consecutive months, we give at least 15 days’ notice and you can either bring usage back down or move to the matching tier — any mid-term upgrade is prorated for the remainder of your term.

Choosing a tier

Choose the tier that matches total expected monthly runners across both products. A team can start on Flex, add Fleet later, and keep the same license key.

Use the pricing page for current tiers, or compare the products in Flex vs Fleet.