← All use cases Coming Soon

Local CI/CD

CI moved to the cloud back when a push was a human event. Your agent pushes forty times an hour. Paying a cold, metered runner to watch it think — while your source takes a round trip through someone else’s datacenter — is the slow, expensive way. Run the pipeline next to the agent, on your own metal.

The feedback loop got slower as the work sped up

Hosted CI made sense when humans handed work to a queue once a day. Agents iterate dozens of times an hour. Every one of those runs cold-starts a multi-tenant runner, ships your code and secrets somewhere you don’t control, and bills you by the minute to wait in line.

The machine that runs your pipeline should be a machine you own, sitting right next to the agent driving it.

A sandbox per branch, on hardware you own

01

Branch-paired

heyvm wt spins a worktree-backed sandbox per branch. Isolated state, zero cross-contamination between runs.

02

Your hardware

Your Mac, a home lab, your private cloud. Warm caches, no queue, no metered minutes.

03

Agent-native

The agent runs the suite, reads the failure, patches the code, and runs it again — without ever leaving the box.

# Spin up a branch-paired sandbox
heyvm wt feat/payments -b
✓ Sandbox "feat/payments" ready

# Run the pipeline inside it
heyvm exec feat/payments -- npm test
✓ 42 passed

# Preview the result on a real URL — still your hardware
heyvm bind feat/payments 3000
→ https://feat-payments.heyo.computer

Metered runner vs. your metal

Hosted CI is built for SaaS teams: ephemeral, billed by the minute, owned by the platform that holds your repo. Heyo runs the loop where your agents already are — on infrastructure you’d be paying for anyway.

A hosted runner

  • Billed per minute, cold every run
  • Source and secrets cross a shared cloud
  • Queue latency on every push
  • Agents read the logs; they can’t fix the box

Heyo local CI/CD

  • Your hardware — warm and unmetered
  • Code and secrets never leave your network
  • One isolated sandbox per branch, instantly
  • The agent runs and repairs the pipeline

Bring CI back to your machine

A clean sandbox per branch. The whole loop, on hardware you own.