Alchemy binds infra to tools

Interesting direction: this is less about another IaC syntax and more about making infra a native dependency of the tool itself. If the abstraction stays clean, it could fit AI-built apps especially well, where agents need durable state and cloud bindings without glue code.

• –The R2 example is concrete: a tool can own storage directly instead of shelling out to separate infrastructure scripts.
• –Alchemy’s “resource is just a function” model matches agentic IDEs and codegen workflows better than traditional declarative IaC.
• –TypeScript-native bindings lower friction for teams already building in JS/TS and Cloudflare’s ecosystem.
• –The upside is less configuration drift; the downside is another opinionated control plane if portability and edge cases get messy.
• –This is strongest as infrastructure plumbing for AI/devtools, not as a generic cloud abstraction layer.