Don’t spend money on CI if you already have the compute.

Run your GitHub Actions jobs on the Macs, Linux machines, and cloud accounts you already pay for. Amika charges $100/mo for orchestration and networking, with up to 50 builds at once.

Change one line: runs-on: amika

You already have the compute.

Most teams already pay for machines and cloud capacity. GitHub-hosted runners charge again, by the minute. Amika runs your jobs on what you have.

Hardware

Desktops, racks, and Mac Minis.

Cloud credits

AWS, GCP, and sandbox providers.

Committed spend

Reserved instances and committed-use discounts.

Pay $100/mo. Not per minute.

The $100 covers orchestration and networking. Your jobs run on your compute, so a busy month costs the same as a quiet one.

Monthly CI bill, by build minutes

$0$200$400$600025k50k75k100k min$600GitHub-hostedAmika+ your compute$100pays for itself at ~20k min/mo
GitHub-hosted Linux, 2-core

$0.006 / min

100k minutes a month is $600.

GitHub-hosted macOS

$0.062 / min

10k minutes a month is $620.

Amika

$100 / mo

Any number of minutes, on your compute.

GitHub list prices for private repositories, as of January 2026. GitHub plans include some free minutes each month.

50 builds at once.

An isolated VM for every job, started when GitHub queues it.

0 / 50 running

queued: 0

  • One job, one VM

    Each job gets a new VM, so jobs never share state or step on each other.

  • Up to 50 at once

    Fan out a test matrix across your machines instead of waiting in a queue.

  • No runners to babysit

    Amika starts a runner for each job and deletes the VM when it ends. Nothing to patch, scale, or clean up.

Run macOS or Linux VMs.

Jobs always run in a VM, never on the host's own OS. Pick the machine with a label.

macOS

On your physical macOS machines.

runs-on: [amika, amika.host.studio-mac, macos]

Linux

On machines you already own.

runs-on: [amika, amika.host.build-box]

Cloud

On your existing cloud accounts.

runs-on: [amika, amika.host.ec2-ci]

Switch with one line.

Keep your existing GitHub Actions workflows. Put amika in a job's runs-on, and GitHub runs that job on your compute.

  • Steps and actions/checkout stay in GitHub
  • Secrets stay in GitHub
  • Logs stay in GitHub
  • Pull request checks stay in GitHub
.github/workflows/ci.yml
jobs:  test:    runs-on: ubuntu-latest    runs-on: amika    steps:      - uses: actions/checkout@v4      - run: pnpm install && pnpm test
amika.host.<name>
Run on one of your machines.
amika.size.<name>
Pick the VM size.
amika.on-failure.stopped
Keep a failed job's VM so you can look inside.

FAQ

Do I have to change my workflows?
Only runs-on. Steps, actions, secrets, logs, and checks work as they do today.
Do jobs run directly on my machines?
No. Each job runs in a new VM on the host, never on the host's own OS. Amika puts none of its own credentials in the VM. The job gets its secrets from GitHub.
Can pull requests from forks run on my machines?
No. Amika refuses jobs from fork pull requests, and GitHub shows the reason on the job. This is a safety precaution so external contributors can't access your GitHub environment.
Can I debug a failed job?
Yes. Add amika.on-failure.stopped to runs-on, and Amika keeps the failed job's VM so you or an agent can look inside.
Do you support Windows?
Not yet. Amika runs Linux and macOS jobs today.
Rather not run hardware?
Leave out the host label, and the job runs on Amika's hosted sandboxes. See pricing for hosted compute rates.

CI on compute you already have.

$100/mo. Up to 50 builds at once.

Get started