Skip to main content
HopX runs secure, isolated cloud sandboxes with dedicated kernels (hardware-level isolation) that AI agents use to execute code. 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

Connect HopX on Integrations, and CostGraph starts sandboxes in your HopX account. You don’t run anything yourself.
  1. In CostGraph, go to Integrations > Sandbox > HopX.
  2. Enter these fields:
    • API key (HOPX_API_KEY, required): A HopX API key from the HopX console.
  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 hopx and the preceding fields as environment variables, as described in Run your own dispatcher.

​
Key and permissions

HOPX_API_KEY is a HopX API key (hopx_live_<keyId>.<secret>). Get it from the dashboard at console.hopx.dev; it is shown once when created. HopX names no key scopes. Its docs mention limited keys only where your organization supports them. Sources: docs.hopx.ai: api key, docs.hopx.ai: authentication, docs.hopx.ai: timeout, docs.hopx.ai: create sandbox, docs.hopx.ai: build template.

​
Limits

  • timeout_seconds is an auto-kill timeout. When it expires the sandbox is destroyed and its data is lost. It can be extended with set_timeout. If no timeout is given, the sandbox runs indefinitely. No maximum is documented. (source)
  • Resources come only from the template; you cannot set them per sandbox. Template memory is 512-64000 MB, disk 1-250 GB, and the vCPU range depends on your plan. (source)
  • You can pick a region, for example us-east or eu-west. The docs do not state the CPU architecture. (source)
  • Rate limits: 20 sandbox creations per minute, 100 control-plane requests per minute and 300 VM agent requests per minute. (source)