Bring your own sandbox server

Run goblins on your own infrastructure for $0.10 a minute — paired with your own LLM account, because TaskGoblin never puts its provider credentials on machines you control.

You can register your own sandbox server and have goblins do their work inside your environment — your machines, your network, your boundary. Combined with your own LLM account, that is the lowest rate we offer: $0.10 a minute.

Registering a server

An organisation Owner or Admin registers a sandbox server in the organisation's settings with its URL and API key. The key is encrypted at rest, the server joins the same health-check schedule as our own fleet, and it becomes available to that organisation's runs — and to no one else's.

  • The server belongs to one organisation. Containers on it are only ever claimable by that organisation; no other tenant can be scheduled onto it.
  • Health is checked continuously. If your server is unhealthy or at capacity, runs fall back to TaskGoblin infrastructure rather than queueing behind it — never to another customer's server.
  • Removing a server stops new work being placed on it and stops its containers being claimed.

The control plane still schedules the work, drives the agent, and records the run history. What moves to your side is the container where your code is checked out and executed — so source, build artifacts, and run state stay inside a boundary you operate.

Why there is no infrastructure-only rate

This is the part worth reading twice, because it is a security guarantee before it is a pricing rule.

TaskGoblin will never inject its own provider credentials into infrastructure a customer controls. A platform LLM key placed on a machine we do not operate is a key we can no longer protect: we cannot guarantee who can read the environment, inspect the process, or capture traffic on hardware that is not ours. So we simply do not do it — not for a large customer, not for a trusted one, not as an exception.

The consequence is the pairing rule:

  • Your LLM account and your server → the run executes on your infrastructure with your credentials, at $0.10 a minute.
  • Your server, but no usable LLM account of your own → the run needs one of our provider accounts, so it stays on our infrastructure at $0.40 a minute. Your server is simply unused for that run.

There is no "bring only your own infrastructure" discount, because there is no arrangement in which we would put our credentials there. If your own LLM account becomes unavailable mid-thread, the next run falls back to our account and our infrastructure together — the pairing holds for every run individually.

What this is good for

Teams reach for their own sandbox server when "in the cloud" has to mean their cloud: data-residency requirements, private networks and internal package registries the agent must reach, compliance regimes that require execution inside an audited environment, or simply spare capacity they would rather use than rent.

Where to go next