Skip to main content
Costs for runner infrastructure only. Does not include development environment costs or license fees.
AWS pricing varies by region. Check AWS pricing for current rates.

​
Billable resources

​
Base snapshot costs

For eligible Enterprise AWS runners, Ona maintains base snapshots to reduce environment startup time.
  • Ona meters each initial build, daily refresh, retry, and replacement as normal environment usage while its background environment runs.
  • AWS bills the EC2 instance and EBS volume used during each build as part of your cloud bill.
  • AWS bills EBS snapshot storage. Ona does not meter snapshot storage separately.
Ona normally keeps one compatible successful snapshot for each eligible runner. During a refresh, the previous snapshot remains available until its replacement is ready, so both snapshots can appear on the AWS bill for a short time.

​
Baseline costs

  • ECS task: Less than $8/month (covered by AWS free tier), fixed regardless of environment count
  • Other services (DynamoDB, S3, CloudWatch): Less than 1% of runner cost

​
Viewing costs in AWS Cost Explorer

​
Runner costs

  1. Open AWS Cost Explorer
  2. Group by Usage Type
  3. Filter by CloudFormation stack name (find it at Settings → Runners):
    • Tag: aws:cloudformation:stack-name
    • Or: aws:ecs:clusterName
Stack Name Filter

​
Environment costs

Filter by environment ID using the Name tag with value gitpod-environment-<ID>. Find the ID via Copy ID in environment details. Environment ID Filter

​
EC2 instance tagging

EC2 instances inherit tags from the CloudFormation template for cost allocation and access control. Add tags:
  1. Open your runner’s CloudFormation stack
  2. Select Update → Use current template
  3. Add tags in format Key=Value
  4. Complete the update
Tag changes don’t apply to the running ECS task immediately. Force a new deployment: ECS → Clusters → your cluster → Service → Update → Force new deployment.