Skip to main content
Buddy Sandboxes are isolated Ubuntu Linux machines in Buddy’s cloud with their own CPU/RAM, a persistent 50 GB disk and public endpoints, managed over REST, SDK, MCP or the bdy CLI. The following table shows what CostGraph runs on this provider. CI runners: no. AutoPilot compares runners by price, and this provider publishes no sandbox price.

​
Connect

Run the dispatcher with provider set to buddy and these variables:
  • BUDDY_TOKEN
  • BUDDY_WORKSPACE
  • BUDDY_PROJECT

​
Key and permissions

BUDDY_TOKEN is a Buddy personal access token (app.buddy.works/my-id/tokens). BUDDY_WORKSPACE is the workspace domain/name and BUDDY_PROJECT the project name in which sandboxes are created. Token scopes: SANDBOX_WRITE (create, exec), SANDBOX_READ (list, get command results) and SANDBOX_MANAGE (delete). The SDK docs: ‘The token needs the SANDBOX_READ and SANDBOX_WRITE scopes (add SANDBOX_MANAGE if you also delete sandboxes or snapshots).’ Sources: buddy.works: sdk, buddy.works: create, buddy.works: exec, buddy.works: list, buddy.works: delete.

​
Limits

  • No inactivity timeout by default. If one is set, a command resets it only when it starts: a process left running in the background afterwards does not keep resetting it. (source)
  • Resources from 1 CPU / 2 GB up to 12 CPU / 24 GB (default 2x4); disk fixed at 50 GB; Ubuntu 22.04 or 24.04. (source)
  • Regions: US (default), EU and AS. (source)