> ## Documentation Index
> Fetch the complete documentation index at: https://ona.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# GCP runners

> [!NOTE]
>
> Available on the Enterprise plan. [Contact sales](https://ona.com/contact/sales) to learn more.

GCP Runners deploy Ona's runner infrastructure inside your own Google Cloud VPC. Development environments run as Compute Engine instances in your project. Source code and credentials never leave your infrastructure.

![Architecture diagram showing GCP Runner components including runner service, load balancer, and environment VMs in your VPC](https://mintcdn.com/gitpod-13c83c2b/x2ZR1GQ5eyh1CR6Q/images/docs/flex/runners/gcp-runner.png?fit=max\&auto=format\&n=x2ZR1GQ5eyh1CR6Q\&q=85\&s=f73c7353c9ac89ffd4da1719a59b79fb)

## 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](https://ona.com/docs/ona/runners/gcp/reference-architectures.md)
* **Supporting services**: Memorystore Redis for state and Cloud Storage for build cache

## Getting started

The runner is deployed using a [Terraform module](https://registry.terraform.io/modules/gitpod-io/ona-runner/google/latest) that provisions and configures all components. The [Setup guide](https://ona.com/docs/ona/runners/gcp/setup.md) 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](https://ona.com/docs/ona/runners/gcp/reference-architectures.md) to choose between external and internal load balancer modes based on your network requirements.

| | |
| - | - |
| [Setup](https://ona.com/docs/ona/runners/gcp/setup.md) | Step-by-step deployment with Terraform |
| [Reference architectures](https://ona.com/docs/ona/runners/gcp/reference-architectures.md) | External vs internal load balancer modes, networking, and certificate requirements |
| [Access requirements](https://ona.com/docs/ona/runners/gcp/detailed-access-requirements.md) | IAM permissions, network connectivity, GCP APIs, and image access |
| [Private GAR images](https://ona.com/docs/ona/runners/gcp/private-gar-images.md) | Use private Google Artifact Registry images in Dev Containers |
| [Costs & budgeting](https://ona.com/docs/ona/runners/gcp/gcp-runner-costs.md) | Infrastructure costs and optimization strategies |
| [Updating a runner](https://ona.com/docs/ona/runners/gcp/update-runner.md) | Terraform infrastructure upgrades and release notifications |
| [Warm pools](https://ona.com/docs/ona/projects/warm-pools.md) | Pre-initialized instances for near-instant environment startup |
| [Alerts & dashboards](https://ona.com/docs/ona/runners/gcp/alerts-and-dashboards.md) | Pre-built Grafana alerts and monitoring dashboards |
| [Troubleshooting](https://ona.com/docs/ona/runners/gcp/troubleshooting-runners.md) | Common problems and diagnostic steps |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.