cf-orbs runs Amp orbs in your own Cloudflare account. An orb is the machine where an Amp agent runs its tools: it clones your repo, runs commands and edits files there. Amp runs orbs on its own servers by default. With cf-orbs, each orb is a Cloudflare Container in your account instead.
Why use it
- Your code stays in your account. The repo checkout, build output and saved disks stay in your Cloudflare account.
- You pay only for what runs. A paused orb has no compute charge. You pay $5 a month for the Workers Paid plan and about $2 a month for the provider (the always-on process that takes orb jobs from Amp). Each awake default orb costs $0.113 an hour. See Costs.
- One command to install.
npx cf-orbs initdeploys cf-orbs to your account.
Features
- It starts, pauses and resumes orbs when Amp asks, and keeps the disk across a pause.
- Each install has one orb size, up to 4 vCPU and 12 GiB memory.
- You can add your own toolchains to the orb image.
cf-orbs doctorand a self-test check the install.- The CLI handles upgrades, token rotation, snapshots and uninstall.
Where to go next
Quickstart
Install cf-orbs and run a first orb. Start here.
How it works
The parts and how a job moves through them. Read.
Limits and FAQ
What cf-orbs doesn’t do, and how it compares with Amp-hosted orbs. Open.
Troubleshooting
Real error messages, what causes them and how to fix them. Open.
cf-orbs is a community project. It is not affiliated with Cloudflare or Amp (Sourcegraph).