Skip to main content
bunny.net sandboxes are on-demand isolated Ubuntu containers run as bunny.net Magic Containers apps, created and controlled over SSH/SFTP by the bunny sandbox SDK and CLI. The following table shows what CostGraph runs on this provider.

​
Connect

Connect bunny.net on Integrations, and CostGraph starts sandboxes in your bunny.net account. You don’t run anything yourself.
  1. In CostGraph, go to Integrations > Sandbox > bunny.net.
  2. Enter these fields:
    • API key (BUNNYNET_API_KEY, required): The bunny.net account API key from Account > API Key.
    • Region (BUNNY_REGION, optional): The bunny.net region sandboxes run in, if not the default.
  3. Click Connect.

​
Your own dispatcher

To keep the key out of CostGraph or reach a private network, run your own dispatcher instead. Set provider to bunny and the preceding fields as environment variables, as described in Run your own dispatcher.

​
Key and permissions

BUNNYNET_API_KEY is the bunny.net account-level API key, found at Account > API Key (dash.bunny.net/account/api-key); it can be revealed or regenerated there. Keys are not scoped: full access to the bunny.net account. The API keys page says ‘Your API key has full access to your account.’ Sources: bunny.net: api keys, bunny.net: sandbox, bunny.net: limits.

​
Limits

  • Per pod: 8 CPUs, 32 GiB memory, 10 GB ephemeral storage (trial accounts: 1 CPU and 4 GiB). (source)
  • Sandboxes are removed only by an explicit delete; no expiry is documented. Default region AMS. Architecture and preview status are not documented. (source)
  • Exceeding 10 GB of ephemeral storage evicts and restarts the pod, losing ephemeral data. (source)