Google Cloud region
Self-hosted GitHub Actions runners in GCP us-central1 (Iowa)
GCP's flagship US region with full A100 / H100 availability. Cirun spins Google Cloud VMs in GCP us-central1 (Iowa) on demand for each workflow and tears them down when the job completes — compute stays in US.
Why this fits
- GCP's flagship US region with full A100 / H100 availability.
- Google Cloud GCP us-central1 (Iowa) keeps your CI compute in US for the duration of the job — useful for GDPR, RBI, HIPAA-adjacent and other data-residency rules.
- Audit-friendly — every job logs the region it ran in; data leaving the region requires an explicit step in your workflow.
.cirun.yml
.cirun.yml
1runners:2 - name: gcp-us-central1-runner3 cloud: gcp4 instance_type: n2-standard-85 # Use a GCP image family path or a self-link to a custom image6 # you've built and shared with Cirun's service account.7 machine_image: projects/ubuntu-os-cloud/global/images/family/ubuntu-2204-lts8 labels:9 - cirun-gcp-us-central1
Drop this in your repo root. The first workflow that requests the runner label spins this configuration up on your cloud account.
Common instance SKUs on Google Cloud
Ready to run your CI here?
Cirun is free for open source. For private repos, flat monthly plans by repo count — never per CI minute.
Sources · verified 2026-05-25