Run your CI in your cloud

Get fully managed GitHub Actions runners in your own cloud with autoscaling, build caching, warm runner pools, and more.

Get started Read the docs

acme/Runners

live

Busy14

Idle pool2 / 2

Spot71%

Cap14 / 40

JobLabelMachineRegionStateTime

test (ubuntu, node 24)acme/webairship-buildAWSc7i.xlargespotus-east-1busy2m 41s

train-smokeacme/modelsairship-gpuGCPg2-standard-8spotus-central1-blaunching0m 12s

e2e (shard 3/4)acme/webairship-buildAWSm7i.xlargeus-east-1running0m 38s

msbuild releaseacme/desktopairship-windowsAzureStandard_D4s_v5eastusbusy6m 02s

lintacme/apiairship-smallAWSt4g.mediumspotus-west-2pending—

cargo build --releaseacme/engineairship-armAWSc7g.2xlargespoteu-west-1finished4m 19s

.github/workflows/ci.yml

jobs:
  test:
    runs-on: airship-build--${{ github.run_id }}
    steps:
      - uses: actions/checkout@v5
      - run: make test

Cloud Native

Run CI in your AWS, GCP, or Azure account using existing cloud credits.

Faster CI

Right-size instances and automatically scale runners to match demand.

Faster Builds

Speed up builds with caching, warm pools, and optimized compute.

Managed Runners

No runner provisioning, management, or maintenance required.

Features

Built for every workload

From simple tests to complex builds, everything you need to run and scale CI in your own cloud.

Multi-cloud supportRun CI across AWS, GCP, and Azure with one configuration. Switch clouds without rewriting your workflows.Spot with fallbackCut compute costs with Spot instances and automatically fall back to on-demand when capacity runs out.Warm runner poolsKeep runners ready for incoming jobs with warm pools that scale to your schedule and workload.GPU runnersRun GPU-intensive CI workloads on the accelerators you need, with automatic driver setup.Custom environmentsRun CI on Linux, Windows, or ARM using your own machine images, dependencies, and configurations.Build cachingSpeed up repeated builds with GitHub Actions-compatible caching backed by storage in your own cloud.Developer APIAutomate repository setup, cloud connections, and access management with a simple API.

airship.yaml

runners:
  - name: build
    cloud: aws                 # or gcp · azure
    instance_type: c7i.xlarge
    region: us-east-1
    labels: [airship-build]
 
  - name: windows
    cloud: azure
    instance_type: Standard_D4s_v5
    machine_image:
      publisher: MicrosoftWindowsServer
      offer: WindowsServer
      sku: 2022-datacenter-g2
    labels: [airship-windows]

airship.yaml

runners:
  - name: gpu
    cloud: gcp
    instance_type: n1-standard-8
    region: us-central1        # any zone with capacity
    gpu: nvidia-tesla-t4
    preemptible: true
    labels: [airship-gpu]

$ nvidia-smi --query-gpu=name,memory.total

name, memory.total [MiB]

Tesla T4, 15360 MiB

terminal

$ curl -H "Authorization: Bearer $AIRSHIP_TOKEN" \
    https://api.airshipci.com/api/v1/repo \
    -d '{"repository": "acme/web", "active": true}'
 
{"fullName": "acme/web", "activated": true, ...}

How it works

Fully Managed GitHub Actions Runners

Run GitHub Actions on AWS, GCP, or Azure without managing the underlying infrastructure.

Connect a cloud

GitHubAirshipYour cloud

job queued: airship-build

reads airship.yaml

RunInstances c7i.xlarge · spot

runner registers for this one job

job runs

shuts itself down

On-Demand Provisioning

Airship automatically provisions runners in your cloud as GitHub Actions jobs are queued.

cloudaws · us-east-1

access_keyAKIA••••••••••••

secret_key••••••••••••••••••••

sealed · bound to this row

opened forRunInstances→ dropped

Secure Cloud Access

Airship securely provisions and manages runners in your account.

pending
launching
running
busy
finished

finished, and why

completed
cancelled
idle
launch_failed
lost
max_lifetime

Automatic Runner Cleanup

Airship automatically cleans up idle or orphaned machines.

AWSEC2 · S3 cacheconnected
Google CloudCompute Engine · GPUsconnected
AzureVirtual Machinesconnected

runs

ubuntu2404
Windows Server
arm64
nvidia-l4
spot
custom AMI
gallery image

Multi-Cloud Support

Configure runner machine types, regions, operating systems, and images to match your workloads.

Security

Secure by Design

Run GitHub Actions within your own cloud environment, without exposing your code or secrets to third-party runners.

ISOLATED BUILDSEach job runs on its own machine
YOUR NETWORKRun within your own VPCs and subnets
EPHEMERAL RUNNERSAutomatically terminated after each job
SCOPED CACHE ACCESSTemporary access to designated cache storage
SELF-HOSTED CONTROL PLANEDeploy the control plane in your environment

Get started

Your first runner in four steps.

1Install the GitHub App
2Connect a cloud
3Activate a repository
4Commit airship.yaml

Get started

airship.yaml

runners:
  - name: build
    cloud: aws
    instance_type: [c7i.xlarge, m7i.xlarge]
    preemptible: [true, false]
    labels: [airship-build]
    extra_config:
      cache: true