Amp lets enterprises self-host orb sandboxes for its coding agent
Amp Chronicle says users can now self-host orbs, supplying their own compute for Amp to turn into orbs. Running `amp orb provider` inside their infrastructure, the provider contacts Amp and waits for requests to spawn, pause or delete orbs, then dispatches those operations to a program the user supplies. Amp says the option is intended for enterprises with regulatory, internal-network or custom-hardware constraints and that most users probably shouldn't self-host; self-hosted orbs are free for individuals and teams, with enterprises charged standard orb pricing starting October 29.
Amp says self-hosted orbs are aimed at enterprises whose code cannot run on Amp-hosted infrastructure because of regulations, internal-network needs or custom hardware.
You can now self-host orbs. You provide the compute and Amp turns it into orbs.
If you have compute that can
- quickly start new machines
- put them to sleep and resume them equally fast
- keep them around for a long time
- scale them to zero, so no one has to worry about having a lot of them sleeping
then you are now able to replicate the orb experience within your own infrastructure.
How It Works
You run amp orb provider inside your infrastructure. The orb provider then reaches out to Amp and waits for requests to spawn, pause, or delete orbs. Like this: