Available on the Enterprise plan. Contact sales to learn more.
Architecture
A GCP Runner consists of:- Runner orchestrator: a containerized service running on Compute Engine that manages environment lifecycle
- Environment VMs: Compute Engine instances automatically sized based on your environment class configuration
- Load balancer: routes traffic to environments, available as external or internal
- Supporting services: Memorystore Redis for state, Cloud Storage for build cache, Artifact Registry for container images
Getting started
The runner is deployed using a Terraform module that provisions and configures all components. The Setup guide walks you through the process step by step, from creating the runner in the Ona dashboard to verifying it’s online. Before deploying, you may want to review the reference architectures to choose between external and internal load balancer modes based on your network requirements.| Setup | Step-by-step deployment with Terraform |
| Reference architectures | External vs internal load balancer modes, networking, and certificate requirements |
| Access requirements | IAM permissions, network connectivity, GCP APIs, and image access |
| Private GAR images | Use private Google Artifact Registry images in Dev Containers |
| Costs & budgeting | Infrastructure costs and optimization strategies |
| Updating a runner | Terraform infrastructure upgrades and release notifications |
| Alerts & dashboards | Pre-built Grafana alerts and monitoring dashboards |
| Troubleshooting | Common problems and diagnostic steps |