Amp orbs, on machines you own.
An Amp orb is a cloud Linux machine where the Amp coding agent works on one thread. Amp also lets you bring your own machines. You provide the compute and Amp turns it into orbs. cf-orbs makes your Cloudflare account that compute, so your threads work the same way, but your code runs in your account.
One click. Cloudflare builds and deploys it in your account, and you paste one Amp token.
Or one command
npx cf-orbs init
Open source, Apache-2.0. Not affiliated with Cloudflare or Amp.
Your Cloudflare account
- Thread Aworking
- Thread Bworking
- Thread Cpaused
Is this for me?
You use Amp orbs
You like orbs, but you want them in your own account. Then you decide where your code runs, which image it starts from and who bills you. Self-hosting orbs used to mean running a server. With cf-orbs, it means your Cloudflare account.
You use Cloudflare
You want your coding agent to get a real Linux machine for each thread, in the account you already have. A paused orb has no compute charge, and there is no server for you to run.
What you get
Everything an orb gives
- A Linux machine for each Amp thread, which keeps working when your laptop is closed.
- The agent runs its tools there, on your repo with your toolchain.
- An idle orb pauses and wakes on the next message, with its files where you left them.
- New threads start from a snapshot (a saved copy of the disk) of your project, already set up.
Plus what self-hosting adds
- Code, snapshots and logs stay in your Cloudflare account. The provider connects out to Amp, and nothing connects in.
- Orbs start from your own image, with the toolchain you choose.
- You pay Cloudflare directly, and a paused orb has no compute charge.
- No server, VM or cluster to look after: Cloudflare runs the machines.
Three ways to get orbs
| Question | cf-orbs | Amp-hosted | Self-hosted, do it yourselfyour server or Kubernetes |
|---|---|---|---|
| Orbs run in your account | Yes | No | Yes |
| No server to run | Yes | Yes | No |
| Your own base image | Yes | Setup scripts on Amp's Debian image | Yes |
| Paused orbs stop compute | Yes | Yes | You build it |
| Setup | One click, or npx cf-orbs init |
None | You build it |
How it works
-
Install
One click, or
npx cf-orbs init, deploys a Worker (a small Cloudflare program that manages the orbs) and the orb image (the disk each orb starts from) to your account. Then it starts the provider, a small container that takes orb jobs from Amp. -
Pick it in Amp
In the thread composer, choose Orb, then Self-Hosted. From the command line, pass
--orb-provider <name>toamp. -
Work
Each thread gets its own orb in your account. When Amp pauses an idle orb, cf-orbs saves its disk and stops the machine.
Benchmarked as fast or faster than Amp-hosted orbs on first response and installs.
Good to know
- Needs Cloudflare Workers Paid ($5 a month).
- A paused orb keeps its files, but not its running processes.
- Community project. Not affiliated with Cloudflare or Amp.
Get started
With one click
You need:
- A Cloudflare account on Workers Paid
- A GitHub or GitLab account
- An Amp provider token: Amp, Settings, Orbs, Add Provider
Cloudflare copies the cf-orbs template into your Git account, asks for the token, then builds and deploys in your account. The first build takes 10 to 15 minutes. After it, the provider starts by itself. Nothing runs on your machine.
The one-click guide shows the setup page and what comes after.
Or with the CLI
You need:
- Node 22 or later, and Docker running
- A Cloudflare account on Workers Paid, with
npx wrangler logindone - An Amp provider token and its name: Amp, Settings, Orbs, Add Provider
# Deploy to your account; asks for the Amp token.
# Use the provider name you made in Amp.
mkdir my-orbs && cd my-orbs
npx cf-orbs init --provider-name YOUR_PROVIDER_NAME
# Start a thread on your orb
amp -ox "hello from cf-orbs" --orb-provider YOUR_PROVIDER_NAME
init builds the images on your machine and deploys them. It is safe to run again. When it finishes, npx cf-orbs doctor checks the install.
Want your coding agent to do the install? Point it at AGENTS.md.
Questions
What does it cost?
You pay Cloudflare. A default orb costs about $0.11 an hour while awake and idle, and $0.40 at full CPU. A paused orb has no compute charge. The provider container is always on, about $2.01 a month. init --vcpu 2 gives a smaller, cheaper orb.
Where does my code run, and who can see it?
In containers in your Cloudflare account, where the orbs, disk snapshots and logs stay. Amp has the same access as on a hosted orb, because the agent's tool calls run inside the orb. cf-orbs adds no other service, and its logs redact tokens.
What happens when an orb pauses or is lost?
On pause, cf-orbs saves the disk: the repo, installed packages and build caches. Running processes are not saved. If Cloudflare stops an orb in the middle of a turn, Amp starts it again, cf-orbs restores the last snapshot, and the agent runs the failed tool call again.
What about Amp Enterprise?
Amp bills Enterprise workspaces for self-hosted orbs, by the CPUs and memory each orb reports. So on Enterprise, cf-orbs costs more than an Amp-hosted orb. The reason to use it there is that your code stays in your account.