Skip to main content
Arker runs durable, forkable virtual machines for agent workloads, driven through fork, run and sync API primitives. 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 arker and these variables:
  • ARKER_API_KEY

​
Key and permissions

ARKER_API_KEY is an Arker API key (prefix ark_live_). Create it in the Arker console under Settings > API keys (arker.ai/console/settings/api-keys), with the CLI (arker api-keys create) or POST /v1/api-keys. A key acts with its creator’s organization role (admin or member); members can do everything except manage pools, billing and members. Optional scopes narrow a key to 1-16 specific VM ids or to one pool. For create/run/list/delete of fresh VMs use a member key with no scopes, or a key scoped to one pool (it forks into and lists only that pool; only admins can create pool-scoped keys). A key scoped to vm_ids cannot create new VMs. Sources: arker.ai: api keys, arker.ai: quickstart, arker.ai: vms, arker.ai: run, arker.ai: regions.

​
Limits

  • No fixed lifetime cap documented; per-run timeout is optional (‘Omit or set to 0 for no limit’). (source)
  • vCPU, memory and disk are resizable within per-machine min_vcpus/max_vcpus and min/max_memory_mib reported by the API; no fixed plan maximum is documented. (source)
  • Region and CPU architecture are set per placement: AWS eu-north-1 is graviton2 (arm64) only; aws us-east-1/us-west-2 offer graviton (arm64) and icelake (x86); arker eu (zen4), arker us-west (graniterapids, H200 GPU) and gcp us-central1 (sapphirerapids) are x86. Other regions on request. (source)