Setup

Everything you need before deploying to Cloudflare: the alchemy package, a Cloudflare account, and stored credentials.

Install

Install alchemy@latest and effect@rc in your project:

bun

bun add "alchemy@latest" "effect@rc" "@effect/platform-bun@rc" "@effect/platform-node@rc"

npm

npm install "alchemy@latest" "effect@rc" "@effect/platform-bun@rc" "@effect/platform-node@rc"

pnpm

pnpm add "alchemy@latest" "effect@rc" "@effect/platform-bun@rc" "@effect/platform-node@rc"

yarn

yarn add "alchemy@latest" "effect@rc" "@effect/platform-bun@rc" "@effect/platform-node@rc"

Tip

We recommend Bun for the best development experience, but Node.js 22+ works too.

Create a Cloudflare account

If you don’t have one yet, sign up for Cloudflare — the free plan is enough for everything in the tutorial.

Connect alchemy to Cloudflare

Connect Cloudflare (the default profile is created automatically on first use):

alchemy profile edit --add Cloudflare

For Cloudflare you can:

• Sign in with OAuth — opens the browser, no tokens to manage.
• Paste an API token — if you prefer explicit, scoped tokens.

The OAuth flow asks whether you want to customize scopes — answer yes to pick exactly which ones to grant at a multiselect prompt (the default set covers typical use).

Either way the result is saved to your default profile at ~/.alchemy/profiles.json — no environment variables and no wrangler login required.

To re-run the flow later:

# Re-run the interactive setup (e.g. switch from OAuth → API token)
alchemy profile edit --reconfigure Cloudflare

# Or manage every account in the profile from one menu
alchemy profile edit

profile edit imports your stack file to discover which providers are available, so the menu matches the providers you actually use.

Profiles

A profile is a named bundle of credentials. Commands use the built-in default profile unless you name another one explicitly. Pass --profile <name> or set $ALCHEMY_PROFILE to select one — handy for separating work and personal accounts, or staging and prod credentials:

# Log into a separate profile
alchemy profile create prod
alchemy profile edit --profile prod

# Deploy with it
alchemy deploy --stage prod --profile prod

Inspect what’s stored (credentials are redacted) with:

alchemy profile show

See Profiles for the full picture.

Running in CI?

CI environments can’t do interactive logins. There, alchemy reads credentials from the environment instead: CLOUDFLARE_ACCOUNT_ID plus either CLOUDFLARE_API_TOKEN or CLOUDFLARE_API_KEY + CLOUDFLARE_EMAIL (or CLOUDFLARE_ACCOUNT_EMAIL). See the CI guide for the full GitHub Actions setup.

Where next

• Tutorial part 1 — create a Stack, deploy your first resource.
• Cloudflare overview — the map of resources and guides.
• Secrets & env — wire .env values and secrets into your Workers (deploy credentials live in your profile; app secrets are bindings).