Amp lets users run its orbs on their own infrastructure
Overview
Amp announces self-hosted orbs, which run on the user's own infrastructure through a self-hosted orb provider.
The provider forwards spawn, pause and delete requests to a dispatch program the user writes, and Amp publishes examples for Docker, E2B, Modal, Vercel, Daytona and exe.dev.
Amp says self-hosted orbs are free for individuals and teams. Enterprises will be charged standard orb pricing starting October 29.
Amp later adds that any user, not only workspace admins, can add a self-hosted orb provider in personal Settings → Orbs. Threads created with a personal provider appear under Self-Hosted and are marked Personal.
Written by AI from the articles below · updated Oct 28, 9:56 AM ET
Check the sources:
Developments
2 developments
- Oct 27, 8:00 PM ET · 1 articleAmp lets personal users add self-hosted orb providers outside workspacesAmp News: Amp lets users self-host orbs in personal settings without a workspace
- Oct 21, 8:00 PM ET · 1 articleAmp lets enterprises self-host orb infrastructure via a dispatch programAmp News: Amp lets enterprises self-host orbs on their own infrastructure
Article timeline
The articles in this story. Times are ET.
- Amp NewsOfficialAmp lets users self-host orbs in personal settings without a workspace
AIAmp now lets any user add a self-hosted orb provider in personal Settings → Orbs, not only workspace admins. Threads created with a personal provider appear under Self-Hosted and are marked Personal.
- Amp NewsOfficialAmp lets enterprises self-host orbs on their own infrastructure
AIAmp now lets users run its orbs on their own infrastructure through a self-hosted orb provider. The provider forwards spawn, pause, and delete requests to a dispatch program the user writes, with examples for Docker, E2B, Modal, Vercel, Daytona, and exe.dev. Enterprises are charged standard orb pricing from October 29, and self-hosted orbs are free until then.
Heat Trend
Not enough continuous observations to show a trend yet.