Skip to main content
Northflank sandboxes are deployment services on Northflank’s managed cloud, running in microVMs (CPU) or gVisor (GPU), into which commands are run through Northflank’s exec API. 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 Northflank on Integrations, and CostGraph starts sandboxes in your Northflank account. You don’t run anything yourself.
  1. In CostGraph, go to Integrations > Sandbox > Northflank.
  2. Enter these fields:
    • API token (NORTHFLANK_API_TOKEN, required): A Northflank API token from Team settings > API > Tokens.
    • Project ID (NORTHFLANK_PROJECT_ID, required): The Northflank project sandboxes are deployed into.
    • Team ID (NORTHFLANK_TEAM_ID, optional): The Northflank team ID, needed with an organization token.
  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 northflank and the preceding fields as environment variables, as described in Run your own dispatcher. To see what Northflank costs, connect the Northflank integration.

​
Key and permissions

NORTHFLANK_API_TOKEN is a Northflank API token. A member creates it in the team’s settings (Team settings > API > Tokens) from an API role, which must first be created by a member with permission. Organization tokens also need the team ID. NORTHFLANK_PROJECT_ID is the project the sandbox services are deployed into. Documented per endpoint. Create an API role restricted to the sandbox project with: Project > Services > General > Create, Read, Update (update covers service ports) and Delete, plus Services > Deployment > Command Exec for exec. If volumes are used, also add Project > Volumes > General > Create, Read and Delete. A token inherits its role’s permissions. Sources: northflank.com: use the api, northflank.com: use role based access control, northflank.com: create deployment service, northflank.com: list services, northflank.com: delete service.

​
Limits

  • Default quota per instance is 8 vCPU, 16 GiB memory and 2 GiB ephemeral storage. There are 500 services per team and 10 instances per service; support can raise them. (source)
  • Plans run from nf-compute-10 (0.1 vCPU/256 MiB) to nf-compute-2000-40 (20 vCPU/40 GiB), but the default 8 vCPU/16 GiB quota caps them. Free projects have separate limits and no GPUs. (source)
  • A project’s region is fixed when the project is created. GPU sandboxes need a GPU-enabled region. (source)
  • No maximum lifetime or idle auto-stop is documented. Sandboxes run until paused or deleted, and pausing deletes ephemeral data. (source)