CI Runners
Coming (phase 3)GitHub Actions jobs on a fresh machine each, from 2 to 32 vCPU, billed by the minute.
Coming (phase 3)CI Runners come first
The infrastructure behind autonomous software engineering.
One platform for everything after the code is written: CI, code review, security testing and merging. And a machine for every coding agent to work on.
Change one line in your workflow. Every job gets a fresh VM, billed per minute.
.github/workflows/ci.yml
-removed: runs-on: ubuntu-latest
+added: runs-on: ohmako-ubuntu-latest-x64-2x
- buildqueuedrunningpassed
- testqueuedrunningpassed
- lintqueuedrunningpassed
- e2equeuedrunningpassed
GitHub, 2 vCPU Linux x64$0.006/min
ohmako 2x$0.004/min
Private repositories. GitHub doesn't bill its standard runners on public ones.
Illustrative
02 The problem
Agents multiplied your pull requests. Your pipeline didn't grow with them.
Writing code is no longer the slow part. Everything after it is.
CI queues up
So many pull requests run at once that jobs wait for machines, and the bill grows with every push.
Reviews get thin
Nobody can read every agent's pull request as closely as it needs.
Merges stall
Green checks on a branch don't mean main stays green once it lands.
Security waits
Nobody tests each change for the holes it opens.
03 The platform
One platform, from push to merge.
Every product runs on the same machines, bills to one account under the same spend limits, and answers to the same MCP server, CLI and API.
Run
Agent Machines
Coming (phase 5)Machines for your coding agents that sleep when idle and wake where they left off.
Snapshots
Coming (phase 5)Prepare an environment once, then start every job and agent from it, warm.
Review and secure
Code Review
Coming (phase 4)A senior engineer's review on every pull request, and a fix for what it finds.
Security Testing
Coming (phase 6)An AI penetration test of each change, against a copy of your app in a sandbox, never production.
Ship
Merge Queue
Coming (phase 4)Tests pull requests against the latest main, in batches, and merges them in order, for free.
CI Optimization
Coming (phase 6)Finds what your CI wastes, and writes the fix for your coding agent.
04 How it works
From push to merge.
What happens to every change, whoever wrote it.
Coming (phase 5) An agent pushes
A coding agent on its OhMako machine, or a developer at a laptop, pushes a branch and opens a pull request.
Coming (phase 3) CI runs on fresh machines
Each job gets a new machine of its own, billed by the minute. A newer push cancels the runs it made pointless.
Coming (phase 4) A senior engineer's review
The reviewer reads the change across files, runs it, and comments in the pull request with what it found.
Coming (phase 4) It fixes what it found
Press Autofix, or reply to a finding, and the reviewer pushes the fix to the branch.
Coming (phase 6) Its security is tested
An AI penetration test attacks a copy of the app in a sandbox, and posts what it got into, with the fix.
Coming (phase 4) The queue merges it
The merge queue tests it with the latest main, batched with others, and merges it once everything passes.
Illustrative
Throughout, every agent has a machine to work on.
05 People and agents
Made for people and agents alike.
The same platform, through the doors each of them uses, on one API.
People
Watch and steer runs, machines and spend in the web app. Talk to the reviewer in the pull request on GitHub, and press Autofix there.
Agents
Run jobs, start machines and check spend through the MCP server and the CLI, both called ohmako.
ohmako --help
Usage: ohmako <command> [flags]
Commands:
runner CI Runners: jobs and logs
machine Agent Machines
security Security Testing
queue Merge Queue
usage Usage and spend limits
Illustrative
06 Integrations
Works where your code lives.
Each product speaks its provider's language: pull requests and checks, or merge requests and pipelines.
GitHub
Coming (phase 3)Move a GitHub Actions job by changing one line, its runs-on. Code Review, Merge Queue and Security Testing will work in your pull requests as each one arrives.
GitLab
Coming (phase 4)Code Review and Merge Queue on merge requests, as the last milestone of phase 4. GitLab CI runners come in phase 9.
07 Security and isolation
Every job starts clean.
Coming (phase 3) CI Runners
A fresh virtual machine per job
Each job gets a new virtual machine, terminated when the job ends. Nothing carries over to the next one.
Nothing reaches in
No inbound network access, and no cloud credentials the job can reach.
Attacks stay in the sandbox
Security Testing attacks only a copy of your app in a sandbox, never production.
08 Pricing
Pay by the minute. Keep the change.
Billed per minute, rounded up, with no minimum. You start with $10 of credit and no card. Add a card and every month includes 2,000 Linux 2x minutes.
Linux x64
Coming| Size | Machine | Per min |
|---|---|---|
| 2x | 2 vCPU, 8 GB | $0.004 |
| 4x | 4 vCPU, 16 GB | $0.008 |
| 8x | 8 vCPU, 32 GB | $0.016 |
| 16x | 16 vCPU, 64 GB | $0.032 |
| 32x | 32 vCPU, 128 GB | $0.064 |
Linux arm64
Coming| Size | Machine | Per min |
|---|---|---|
| 2x | 2 vCPU, 8 GB | $0.003 |
| 4x | 4 vCPU, 16 GB | $0.006 |
| 8x | 8 vCPU, 32 GB | $0.012 |
| 16x | 16 vCPU, 64 GB | $0.024 |
| 32x | 32 vCPU, 128 GB | $0.048 |
Windows x64
Coming| Size | Machine | Per min |
|---|---|---|
| 4x | 4 vCPU, 16 GB | $0.016 |
| 8x | 8 vCPU, 32 GB | $0.032 |
| 16x | 16 vCPU, 64 GB | $0.064 |
| 32x | 32 vCPU, 128 GB | $0.128 |
macOS
Coming| Size | Machine | Per min |
|---|---|---|
| 6x | 6 vCPU, 14 GB | $0.08 |
| 12x | 12 vCPU, 28 GB | $0.16 |
Mac and iOS work without owning a Mac.
Included every month Coming2,000 Linux 2x minutesWith a card on file, x64 or arm64. Other machines bill from the first minute.
Sign-up credit Coming$10, no card
Cache Coming$0.20 per GB-monthplus $0.0001 per operation
Snapshots Coming$0.04 per restoreplus $0.025 per snapshot-hour
09 The invite list
The only queue worth waiting in.
You start with $10 of credit and no card. Add a card and every month includes 2,000 Linux 2x minutes.