AWS Lambda MicroVMs vs Fly Machines
Choose AWS Lambda MicroVMs for AWS-native agent sandboxes and interactive sessions that need VM isolation, an inbound endpoint and cheap idle time via suspend; choose Fly Machines for teams that want raw, per-second-billed Firecracker VMs they orchestrate themselves rather than a sandbox SDK. AWS Lambda MicroVMs uses Firecracker microVM isolation; Fly Machines uses Firecracker microVM isolation.
Key differences between AWS Lambda MicroVMs and Fly Machines
- Type: AWS Lambda MicroVMs is a cloud or model provider service; Fly Machines is a hosted platform.
- SDKs and interfaces: Only AWS Lambda MicroVMs lists Python, JavaScript/TypeScript and PHP. Only Fly Machines lists Go.
What they have in common
- Both companies are based in the United States.
- Both use microVM isolation.
- Neither is open source.
- Both support snapshots.
- Both can pause and resume a sandbox.
- Both list CLI and REST API.
AWS Lambda MicroVMs vs Fly Machines at a glance
| Attribute | AWS Lambda MicroVMs | Fly Machines |
|---|---|---|
| What it is | A Lambda resource type that runs a full Amazon Linux 2023 environment in a Firecracker microVM, restored from a pre-built snapshot, with suspend/resume and an HTTPS endpoint per VM. | Fly.io's low-level API for Firecracker VMs that start and stop in under a second and can be suspended to disk; the primitive underneath Fly.io's Sprites product. |
| Type | Cloud or model provider service | Hosted platform |
| Isolation | Firecracker microVM per MicroVM ("VM-level isolation with full operating system capabilities"); each runs Amazon Linux 2023 and is restored from a Firecracker snapshot of the built image | Firecracker microVM per Machine ("Compute jobs at Fly.io are virtualized using Firecracker"); runs on Fly.io's own hardware in 17 regions |
| Open source | No | No |
| Self-host / BYOC | No / No | No / No |
| SDKs | Python, JavaScript/TypeScript, PHP, CLI, REST API | Go, CLI, REST API |
| Cold start (vendor claim) | Docs claim "near-instant launch and resume" from snapshot; the Claude Managed Agents integration page says "Resume from Firecracker snapshot in sub-second to single-digit seconds" | Docs: starting a created Machine "usually takes well under a second"; creating one (image fetch, rootfs build) "maybe low double digit seconds"; resuming a suspended Machine "takes a few hundred milliseconds"; marketing claims "sub-second starts and stops" |
| Max session | maximumDurationInSeconds is 1-28,800 seconds (8 hours) including suspended time; the quota page lists "Maximum execution duration per MicroVM: 8 hours", not adjustable | Not documented |
| Persistence | Suspend preserves memory and disk state (checkpointed), resume restores it; auto-suspend after a configurable idle period and auto-resume when traffic arrives; no compute charges while suspended; images are versioned Firecracker snapshots built from a Dockerfile | Stopped Machines keep their rootfs assembled on the host for fast restart (ephemeral storage is a clean slate on each start); suspended Machines "preserve memory and disk state" and resume faster than stopped; attach a Fly Volume for persistent storage; volume snapshots |
| Snapshots / pause | Yes / Yes | Yes / Yes |
| GPU | Not documented — sizes are CPU/memory only (0.25-4 vCPU baseline, burstable to 4x); GPUs are not mentioned in the docs | GPU Machines have been offered; the GPU docs URL now redirects to a blog post that says Fly is "scaling back our GPU ambitions" but "we're not getting rid of them"; no GPU rates appear on the pricing page |
| Networking | Inbound via a per-VM HTTPS endpoint requiring a JWE auth token (HTTP/1.1, HTTP/2, WebSockets, gRPC, SSE; default port 8080); NO_INGRESS connector disables inbound; outbound is public internet by default or a customer VPC egress connector; PrivateLink supported | Private IPv6 network per organisation (WireGuard access); public IPv4/IPv6 and Fly Proxy routing on request; static egress IPs available (fly ips allocate-egress); inbound services optional |
| Pricing | US East (N. Virginia), Arm: $0.0000276944 per vCPU-second and $0.0000036667 per GB-second while running; snapshot write $0.0038/GB (suspend), snapshot read $0.00155/GB (resume or launch); image and suspended-state storage $0.08 per GB-month (one-week minimum for images); billed per second at the baseline rate plus active use above baseline | Billed by the second while running; stopped Machines pay only rootfs at $0.15/GB-month. Monthly equivalents in the cheapest regions: shared-cpu-1x 256 MB $2.19, 512 MB $3.69, 1 GB $6.70; shared-cpu-2x 2 GB $13.39; performance-1x 2 GB $33.00; performance-2x 4 GB $66.00; extra RAM $6/GB-month; volumes $0.15/GB-month; snapshots $0.08/GB-month after 10 GB free; 40% off reserved compute blocks; prices vary by region |
| Free tier | Not documented | $1 trial credit for 7 days (no card required); personal organisations with monthly bills under $5 are waived; no ongoing free tier |
| Compliance | Not documented | SOC 2 Type 2; BAA and SOC 2 report available in the Compliance Package via the dashboard Trust Center; DPAs on request |
| Regions | 14 AWS Regions as of 22 Oct 2026: launched in US East (N. Virginia, Ohio), US West (Oregon), Europe (Ireland), Asia Pacific (Tokyo); later Mumbai, Singapore, Sydney, Frankfurt, Stockholm, Hong Kong, Malaysia, Thailand and Spain | 17 regions: Amsterdam, Stockholm, Paris, Dallas, Secaucus, Frankfurt, São Paulo, Ashburn, Johannesburg, Los Angeles, London, Tokyo, Chicago, Singapore, San Jose, Sydney, Toronto |
| Company headquarters | Seattle, Washington, United States | Chicago, Illinois, United States |
| Good fit for | AWS-native agent sandboxes and interactive sessions that need VM isolation, an inbound endpoint and cheap idle time via suspend | Teams that want raw, per-second-billed Firecracker VMs they orchestrate themselves rather than a sandbox SDK |
Verified November 14, 2026 from each provider’s documentation. Cold-start figures are vendor claims, not our measurements.
Which should you choose?
Reasons to choose AWS Lambda MicroVMs
- You want Firecracker-isolated sandboxes inside your own AWS account with IAM, VPC egress and PrivateLink
- You need sessions that sit idle for long periods without paying for compute (suspend/resume with state intact)
- You run inbound-facing workloads (dev servers, WebSockets, gRPC) that need a per-sandbox authenticated endpoint
- You are building self-hosted sandboxes for Claude Managed Agents on AWS
Reasons to choose Fly Machines
- You want per-second-billed Firecracker VMs with full control of lifecycle, region placement and networking
- You need suspend-to-disk and sub-second restarts for bursty or idle-heavy workloads
- You are already on Fly.io and want sandboxes on the same private network as your app
- You run long-lived or persistent workloads (volumes, no documented session cap)
Trade-offs to check first
- AWS Lambda MicroVMs: Hard 8-hour maximum lifetime per MicroVM, including suspended time
- AWS Lambda MicroVMs: GPU sizes are not documented; largest baseline is 8 GB / 4 vCPU (32 GB / 16 vCPU at peak) with 32 GB disk
- Fly Machines: No dedicated sandbox SDK: file-transfer and snapshot-fork APIs for agents are not documented, and command execution is offered through flyctl (
fly machine exec) - Fly Machines: Only an official Go client; other languages must be generated from the OpenAPI spec
Both are worth piloting with your own image and region. See the full AWS Lambda MicroVMs profile and Fly Machines profile, or the complete comparison.
More comparisons
Frequently asked questions
Is AWS Lambda MicroVMs or Fly Machines better for AI agents?
What is the difference between AWS Lambda MicroVMs and Fly Machines?
Which is open source, AWS Lambda MicroVMs or Fly Machines?
How do AWS Lambda MicroVMs and Fly Machines isolate code?
How does AWS Lambda MicroVMs pricing compare with Fly Machines?
Can you self-host AWS Lambda MicroVMs or Fly Machines?
How long can sessions run on AWS Lambda MicroVMs and Fly Machines?
Do AWS Lambda MicroVMs and Fly Machines support snapshots or pause and resume?
Sources
- docs.aws.amazon.com/lambda/latest/dg/lambda-microvms-guide.html
- docs.aws.amazon.com/lambda/latest/dg/microvms-how-it-works.html
- docs.aws.amazon.com/lambda/latest/dg/microvms-launching.html
- docs.aws.amazon.com/lambda/latest/dg/microvms-images.html
- fly.io/machines.md
- docs.fly.io/machines
- docs.fly.io/machines/overview
- docs.fly.io/machines/api
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 14, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
Agent Sandboxes. (2026). AWS Lambda MicroVMs vs Fly Machines. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/aws-lambda-microvms-vs-fly-machines/