Platform / CI/CD Runners
Every job gets a fresh machine.
Available
OhMako runners execute your GitHub Actions and GitLab CI jobs on dedicated compute. Each job boots its own Firecracker virtual machine, runs, and is destroyed — no shared state, no noisy neighbours, no leftover credentials.actions · workflow ci.yml
jobs:
test:
runs-on: ohmako-arm64-4build · linux-x64-8
fc-vm ●
test (shard 1/3) · arm64-4
test (shard 2/3) · arm64-4
test (shard 3/3) · arm64-4
docker · linux-x64-16
Change one line
Point runs-on at an OhMako label. Your workflows, actions, and caches keep working.
Ephemeral by design
Machines are provisioned per job and torn down after. Secrets and workspace never persist across jobs.
Sized to the work
Choose CPU, memory, and architecture per job instead of overprovisioning a shared fleet.
Capabilities
What's in CI/CD Runners
- GitHub Actions-compatible runners
- GitLab CI support
- Linux x64 and ARM64 execution
- Fresh Firecracker VM per job
- Docker and service containers
- Configurable runner sizes
- Usage-based billing
- Isolated execution environments
Connected
How it fits the rest of OhMako.
RUN → SNP
Snapshots and Warm Pools
Restore jobs from warm snapshots to skip dependency setup.
RUN → MRGMerge Queue
Runners execute merge-queue validation builds.
RUN → OPTCI Optimization
Execution history feeds CI optimization.
Works with
GitHub ActionsGitLab CIDocker
Build the next generation of software delivery.
Give your developers and AI agents the infrastructure to build, validate, and ship software without the operational friction.