Why Per-Task VM Provisioning Changes the Cost and Security Calculus for Cloud Agent Fleets
Destroying a VM after each task cuts idle compute and cross-task risk.
Sofía Rentería
7 stories
Destroying a VM after each task cuts idle compute and cross-task risk.
Shared agent pools beat per-developer VMs, but review becomes the limit.
Move agent work to isolated cloud runs, one layer at a time.
Owning your key is not enough; custody and feature limits matter.
Matching agent VMs to developer toolchains stops failures before CI.
Scope each agent to one package, its dependencies, and its credentials.
Local agents assume one developer, and teams expose the cracks.