CloudThinker Engineering

Agentic infrastructure

  1. Sandboxes must run inside our own network. Hosted sandboxes offer that only on enterprise plans, from about $3K a month. (entry 1)
  2. Persistence comes first. A sandbox has to survive timeouts and node loss; one 11-hour session survived a spot instance termination. (entry 1)
  3. Design for idle time. Per 20 GB, a running sandbox costs about $5 a month, a paused one about $1.60 (resumes in about 5 seconds), an archived one about $0.50 (about 30 seconds). At 200 sandboxes with 80% idle, that is about $200 a month instead of $1,000. (entry 1)
  4. Build on Kubernetes (OpenSandbox on EKS), with a network policy per sandbox and agents running unprivileged. (entry 1)
  5. Detached agent work is a row in Postgres, not a process. A lease says someone is working on it; a fence stops a worker that lost its claim from writing. (entry 2)
  6. Put only an id on the broker. Rebuild the agent's authority from current state on every attempt, so a replay can narrow it but never widen it. (entry 2)
  7. Write the terminal status, the completion and the charge in one transaction. An outbox delivers the completion and a recovery sweep settles the charge; receipts keyed by run id make a second charge a no-op. (entry 2)
  8. Background agents share the interactive worker pool, bounded by per-tenant caps, until p95 time to first token passes 2 seconds. (entry 2)

All revisions:r2, r1


CloudThinker Engineering · engineering.cloudthinker.io · Last built 2026-11-08