Why your Agentic Cloud runs on Fly.

Fly

Every Machine is a Firecracker microVM. Each agent gets one, with its own cores.¹

AWS

An EC2 instance is a whole computer. Fargate runs containers, and Lambda runs short functions of up to 15 minutes.^2,3

Google Cloud

A Compute Engine VM is a whole computer. Cloud Run runs containers.⁴

Vercel

Every Sandbox is a Firecracker microVM with sudo, for up to 24 hours a session on Pro.^5,6

Fly

Fly’s proxy starts a stopped Machine when a request comes in. Ours sleep after about three quiet minutes and wake in about ten seconds.⁷

AWS

You start a stopped EC2 instance yourself or on a schedule, and it can take a few minutes. Lambda MicroVMs do wake on traffic, but each lives at most 8 hours and takes no unauthenticated requests.^8,9

Google Cloud

You start a stopped VM yourself. Cloud Run scales from zero on a request, but a request can last at most 60 minutes.^4,10,11

Vercel

A stopped Sandbox starts again when your code calls Vercel’s SDK.¹²

Fly

A volume per Machine, kept while it sleeps, that Fly grows by itself as it fills.¹³

AWS

An EC2 instance keeps its EBS disk when stopped. A Fargate service deletes its task’s disk when the task ends.^14,15

Google Cloud

A VM keeps its disks when stopped, and they are billed while it sleeps.¹⁰

Vercel

A Sandbox saves its files when it stops, and a Drive keeps work across sandboxes.^12,16

Fly

There is nothing to run: Machines already are microVMs, on a private network with certificates for your domains.^17,18

AWS

Firecracker now runs on some EC2 types through nested virtualization. AWS points latency-sensitive work to bare metal.¹⁹

Google Cloud

Nested virtualization runs KVM on some machine types, and Google warns of a 10% or greater slowdown.²⁰

Vercel

Sandboxes already are microVMs. Their open ports are public addresses, and a private network, Secure Compute, is for Enterprise plans.^5,21