We benchmarked AWS Lambda MicroVMs against Cloudflare Containers — 700 isolated cold boots, timed to first successful request. Every MicroVM boots in 2 to 4.5 seconds regardless of what's inside, because the workload's startup is paid once at image build and snapshotted. Opencode on Cloudflare Containers takes 10.5 seconds at the median, and the worst boots push a minute.
v2.0.0-beta.59 is a naming alignment release. Every Cloudflare service is now a proper namespace, every binding follows one {Verb}{Resource} convention across AWS and Cloudflare, and Binding.Policy is gone — collapsed into a single runtime-guarded Layer.
v2.0.0-beta.58 improves the ergonomics of Layers that contain Resources, so you can bundle infrastructure into a reusable service — like an agent tool — and provide it to a Worker, Container, or Durable Object.
v2.0.0-beta.57 runs Cloudflare Containers locally in alchemy dev, adds Cloudflare AI Search (AutoRAG) with a typed Worker binding, and lands a large AWS wave — CloudFront VpcOrigin, ELBv2 ListenerRule & TrustStore, Route53 HostedZone & HealthCheck, KMS keys, and Lambda aliases.
v2.0.0-beta.56 grows the Cloudflare provider from 22 resources to 230, each implemented and live-tested against the real Cloudflare API — plus alchemy unsafe nuke, GitHub webhook event sources, and an S3-backed state store.