Skip to main content
Islo runs isolated sandbox VMs (used by its agent ‘factories’) that you create, exec in, pause and delete through its API, SDKs and CLI. The following table shows what CostGraph runs on this provider.

​
Connect

Run the dispatcher with provider set to islo and these variables:
  • ISLO_API_KEY

​
Key and permissions

ISLO_API_KEY is an Islo API key (islo_key_…), created with islo api-key create <name> (optionally --expires <days>); shown once. Keys are not scoped: an API key inherits the permissions of the user who created it. No per-key scopes are documented. Sources: docs.islo.dev: api keys, docs.islo.dev: sandbox lifecycle, docs.islo.dev: create sandbox.

​
Limits

  • Lifecycle policy (pause_after_idle, pause_after, delete_after) is opt-in and disabled when omitted; it cannot be changed after creation. (source)
  • No max vCPU/memory, max lifetime, region or architecture limits are documented on the create-sandbox reference. (source)