.cirun.yml builder

Work in progress

This builder UI is a work in progress — most combinations are not yet wired into the form below. Cirun itself supports them; only this generator hasn't caught up. If you hit a "not yet wired in this UI" notice, or need anything beyond what's exposed here, write the YAML by hand using the YAML reference for the full schema.

Generate a working .cirun.yml for your cloud and workload. The output is a starting point — see the YAML reference for the full schema.

01Cloud

02Machine

OSLinuxWindowsmacOS

Arch

Workload

SizeTiny — 2 vCPU · 2 GiBSmall — 2 vCPU · 4 GiBMedium — 2 vCPU · 8 GiBLarge — 4 vCPU · 16 GiBXLarge — 8 vCPU · 32 GiB2XLarge — 16 vCPU · 64 GiB4XLarge — 32 vCPU · 128 GiB8XLarge — 64 vCPU · 256 GiB16XLarge — 96 vCPU · 384 GiBHigh-mem L — 4 vCPU · 32 GiBHigh-mem XL — 8 vCPU · 64 GiBHigh-mem 2XL — 16 vCPU · 128 GiBHigh-mem 4XL — 32 vCPU · 256 GiBHigh-mem 8XL — 64 vCPU · 512 GiB

03Placement & tweaks

Regionus-east-1 · N. Virginiaeu-west-1 · Ireland

Disk (GiB)

Spot / preemptible

.cirun.yml

runners:
  - name: cirun-aws-medium
    cloud: aws
    instance_type: t3.large
    machine_image: ami-04680790a315cd58d  # ubuntu-2204 x86_64
    region: us-east-1
    labels:
      - cirun-aws-medium
 

Commit this file to your repo root as .cirun.yml. Cirun reads it on every push. Read the quickstart →

How it fits together

Cirun watches your repo for the .cirun.yml file at the root. When a workflow asks for a self-hosted runner with the label you defined, Cirun spins one up in your cloud, runs the job, and tears the runner down when the job finishes.

• One YAML file controls every runner shape your repo can request.
• Workflows reference runners by label — no manual fleet management.
• Add cloud credentials in the Cirun dashboard once.
• For multi-cloud fallback, custom networking, env injection, etc. see the YAML reference.