Local runtimes
Where a sandbox runs changes the business case.
GlobalStacks centralizes orchestration without forcing every agent workload through rented cloud compute.
The default cloud pattern
Easy to start. Expensive to leave on autopilot.
Agent sandboxes are not just web requests. They clone, build, test, wait, retry, stream logs, and sit close to private systems. If every session becomes rented cloud compute, the runtime bill becomes part of every workflow.
Do not turn every agent session into rented compute when the workload is steady.
Keep runtime execution inside customer-approved hosts, networks, and storage paths.
Run near repositories, build caches, databases, and internal services.
Placement run
sandbox.create()
Before
One sandbox. Four meters.
With GlobalStacks
Place the runtime before the meter starts.
Not anti-cloud
Cloud is a placement option, not the default tax.
Use cloud capacity when elasticity is the point: bursty demand, managed regions, or teams without available hosts. Use local runtimes when execution is predictable, sensitive, close to private systems, or already backed by hardware you operate.
GlobalStacks keeps identity, lifecycle, placement, logs, access, and networking in one control plane. Runtime execution stays movable across connected hosts, Proxmox nodes, local labs, private clusters, and approved managed pools.
The operating model