Skip to main content
Tenki Sandbox provides disposable, full Linux virtual machines controlled from a CLI or Go, TypeScript and Python SDKs. The following table shows what CostGraph runs on this provider.

​
Connect

Connect Tenki Cloud on Integrations, and CostGraph starts sandboxes in your Tenki Cloud account. You don’t run anything yourself.
  1. In CostGraph, go to Integrations > Sandbox > Tenki Cloud.
  2. Enter these fields:
    • API key (TENKI_API_KEY, required): A Tenki workspace API key from Tenki Sandbox > API Keys.
  3. Click Connect.
For CI runners, CostGraph sets CPU and memory. providerTemplate takes an image reference.

​
Your own dispatcher

To keep the key out of CostGraph or reach a private network, run your own dispatcher instead. Set provider to tenki and the preceding fields as environment variables, as described in Run your own dispatcher. To see what Tenki Cloud costs, connect the Tenki Cloud integration.

​
Key and permissions

TENKI_API_KEY is a Tenki workspace API key (tk_…) created in the Tenki dashboard: Tenki Sandbox > API Keys > Create API Key (optional expiry). TENKI_AUTH_TOKEN is the SDKs’ auth-token variable, read before TENKI_API_KEY; both carry the same bearer credential. Keys are not scoped beyond the workspace: each API key belongs to exactly one workspace and sandbox requests infer it. No roles or permissions documented. Source: https://tenki.cloud/docs/account/api-keys Sources: tenki.cloud: api keys, tenki.cloud: quick start sandbox, tenki.cloud: sdk.

​
Limits

  • cpu_cores 1-16 (default 2); memory_mb 512-65,536 (default 4,096). (source)
  • Pause/Resume may not be available in every deployment; egress allowlists need SDK >= 1.1.0 and workspace enablement. (source)
  • Max lifetime, idle auto-stop, regions, sandbox architecture: not documented. (source)