Sizes & Costs
Choose an orb size based on the work it needs to do. Smaller orbs are inexpensive and work well for focused tasks. Larger orbs can run bigger builds, more services, and parallel test workloads.
Available Sizes
Every current orb size includes 60 GB of disk.
| Size | CPUs | Memory | Standard price |
|---|---|---|---|
a1.tiny | 1 | 2 GB | $0.08/hour |
a1.small | 2 | 4 GB | $0.17/hour |
a1.medium | 4 | 8 GB | $0.33/hour |
a1.large | 8 | 16 GB | $0.66/hour |
a1.xxlarge | 16 | 32 GB | $1.32/hour |
Enterprise workspace prices are 50% higher.
Billing
Orb usage is billed by the minute. A paused orb costs nothing. Amp automatically pauses an orb after five minutes without activity and pauses it when its thread is archived.
Opening a portal or sending another message wakes the orb. Billing resumes while the orb starts and handles the request, then stops when it pauses again.
Orb subscriptions and allowances are explained on the Pricing page.
Choose a Size
- Use tiny for research, small scripts, and focused edits with light checks.
- Use small for most single-package projects and routine coding tasks.
- Use medium for moderate builds, local services, and test suites.
- Use large for monorepos, several services, or CPU-heavy tests.
- Use xxlarge for unusually large builds and parallel workloads.
Start small when you are unsure. You can choose a larger size for the next thread without changing the project default.
Set the Project Default
Open Projects, select the project, and choose its default orb size. Personal projects
for Megawatt subscribers use a1.small by default.
The default applies to new threads. Changing it does not resize an orb that is already running.
Size per Orb
Select a size in the new-thread dialog on the web when one task needs more or less compute than usual.
From the CLI, pass --orb-size with amp -ox:
amp -ox "Run the full browser test matrix" --orb-size a1.largeWhen Amp delegates work to another agent, include the size in your request: