For Vercel Eve your Cloudflare
Same project.
New home.
NoRewriteneededEden deploys the Eve agent you already built to your own Cloudflare account. One command, about two minutes, and your Eve source stays exactly as you wrote it.
npx @moinulmoin/eden deployA real run, not a mockup
One command. About two minutes.
› eden deploy --env-file ~/.config/my-eve-agent.env eden deploy — my-eve-agent-9e510242 (preview) ... validating environment file ... packaging project — snapshot, frozen install, eve build ... checking Cloudflare access and exact target ... building linux/amd64 runtime image, booting eve, checking health ... pushing container image to the Cloudflare registry ... publishing Worker and Container application ✓ VAL-BUILD-001 — The exact pnpm pin and one matching regular root lockfile were verified. ✓ deployed my-eve-agent-9e510242 (preview) · eve 0.66.3 https://my-eve-agent-9e510242.moinulislammoin2019.workers.dev done in 112s ›
› export URL=https://my-eve-agent-9e510242.moinulislammoin2019.workers.dev › curl -s $URL/eve/v1/health {"ok":true,"status":"ready","workflowId":"workflow//eve//workflowEntry"} ›
› eden destroy --name my-eve-agent-9e510242 eden destroy — my-eve-agent-9e510242 (preview) ... verifying the immutable ownership record ... reading the exact remote inventory ... deleting Worker my-eve-agent-9e510242 ... deleting Container application my-eve-agent-9e510242-container ... deleting 1 registry image ... verifying the exact target is absent ✓ VAL-LIFE-006 — Exact absence was verified; clearing this target's CURRENT pointer only. ✓ destroyed my-eve-agent-9e510242 (preview) in 23s retained: local deployment records under .eden/eve-deploy › curl -s -o /dev/null -w '%{http_code}' $URL/eve/v1/health; echo ' <- gone' 404 <- gone ›
Your real Eve server,
in a Cloudflare Container.
Eden doesn't translate your agent into something else. It builds the Eve app you run locally and hosts that same server on your account.
- 01 · your machine
Eve project
Your agent code, pinned pnpm and root lockfile. Eden doesn't edit them.
- 02 · local docker
Eden builder
Frozen install, your own Eve build, a linux/amd64 runtime image.
- Your Cloudflare account
- 03 · edge
Worker
Serves your workers.dev URL and routes requests inward.
- 04 · 1 GiB
Container
Your real Node/Nitro Eve server, started by Eve itself.
GET /eve/v1/health → 200Eden promotes the deployment only after the new URL answers healthy.
Eve stays in charge.
Eden hosts the app. It doesn't rewrite your project or quietly swap its providers and services. Everything your agent depends on keeps working the way you set it up.
Eden never edits your code- These stay in Eve
- Model providers and credentialsstays in Eve
- Databases, queues and external APIsstays in Eve
- Channels, schedules and authstays in Eve
- Sandbox and Workflow Worldstays in Eve
- Values from
--env-filenever in args, image layers or logs
Three commands. That's it.
eden preflightRead-only check of your Eve project, Cloudflare access and target name. Optional; deploy runs the same checks.
eden deployBuilds, publishes and health-checks one exact target. Preview by default, named from package.json.
eden destroy --nameRemoves one exact Eden-owned deployment after checking its ownership record. Never touches look-alikes.
What you need, and what to expect.
You'll need
6 things- macOS or Linux with Node 24.17 or newer
- A Cloudflare account on Workers Paid, which Containers require
- Wrangler signed innpx wrangler@4.120.0 login
- Docker or OrbStack that builds linux/amd64
- An Eve project with an exact pnpm pin and its root lockfile
"packageManager": "pnpm@…" - just-bash as a production dependencypnpm add just-bash
Honest limits
in 0.2.0- Disk and memory reset when the Container sleepsKeep durable state in a Workflow World such as Postgres
- Schedules don't fire while the Container sleeps
- One 1 GiB Container instanceNo horizontal scaling or custom domains yet
- pnpm projects onlyBun lockfiles and native Windows aren't supported yet
Deploy the Eve agent
you already have.
npm install --global @moinulmoin/eden