CI Runners
Coming (phase 3)GitHub Actions jobs on a fresh machine each, from 2 to 32 vCPU, billed by the minute.
Platform
Everything after the code is written, on one platform
Coding agents now write much of the code, and the slow part is what comes after: CI, review, security and merging. OhMako gives every change fast CI, a senior engineer's review, a security test and a safe merge, and every agent a machine to work on.
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.
What every product shares
They aren't separate tools that happen to share a logo. Each one runs on the same machines and answers to the same account.
One bill, with hard limits
Every product bills to one usage ledger, under your Organization's monthly spend limit. Past it, jobs don't start and running work stops, and parallel jobs can't overrun it together.
No long-lived keys
Workloads and SSH sign in with short-lived OIDC credentials. Secrets are injected when a job runs and redacted from its logs.
Who did what
Roles are set for the whole Organization, and an audit trail records what each person and each agent did.
The same machines
Code Review, Security Testing and Merge Queue run on the machines your CI uses, each set up with its triggers, settings and permissions, not on a system of its own.
One API
The MCP server and the CLI are the main ways in, and the web app is for watching and steering. All three sit on one API.
GitHub first, then GitLab
Each product speaks its provider's language: pull requests and checks on GitHub, merge requests and pipelines on GitLab. GitHub comes first in each product. GitLab merge requests follow as the last milestone of phase 4, and GitLab CI runners in phase 9.