Infrastructure-as-Effects — cloud infrastructure and application logic as a single, type-safe Effect program.
- One program, one language. Resources, Lambdas/Workers, IAM, and SDKs live in the same Effect program — no YAML, no second runtime.
- Bindings, not glue code.
S3.GetObject.bind(bucket)wires the IAM policy, env var, and a typed SDK call in a single line. - Errors in the type system. Every cloud API failure is a tagged Effect error you handle — or don't — on purpose.
- AWS + Cloudflare today. S3, SQS, DynamoDB, Kinesis, Lambda, EC2 / Workers, R2, D1, Durable Objects, Containers.
- Same code, every stage. Local dev,
plan/deploy, smoke tests, and CI all share one mental model.
bun add alchemy effectPaste this into Claude Code, Cursor, or any agent that can fetch a URL:
You are an Alchemy expert. Read https://v2.alchemy.run/llms.txt to load the
full documentation index, then act as my pair on this project.
Goal: help me set up, build, test, and deploy a cloud application with
`alchemy` (Infrastructure-as-Effects, powered by Effect).
Follow the patterns from the docs and the /examples folder. Stay idiomatic
to Effect: use Layers for wiring, return Effects from lifecycle code, and
keep infra and runtime in the same program. Ask before introducing new
dependencies or breaking conventions.
- What is Alchemy? — the framework in 2 minutes
- Getting Started — your first Stack
- Tutorial — five-part walkthrough to a tested, CI-deployed app
- Examples — runnable projects on AWS and Cloudflare
- llms.txt — agent-ready documentation index
alchemy is in alpha. Expect breaking changes. Come hang in our Discord.
Apache-2.0