For Vercel Eve your Cloudflare

Same project.
New home.

NoRewriteneeded

Eden 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 deploy

A real run, not a mockup

One command. About two minutes.

eve 0.66.3 · check lines trimmed
› 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
› 
112shealthy · promoted
01 · How it runs

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.

  1. 01 · your machine

    Eve project

    Your agent code, pinned pnpm and root lockfile. Eden doesn't edit them.

  2. 02 · local docker

    Eden builder

    Frozen install, your own Eve build, a linux/amd64 runtime image.

  3. Your Cloudflare account
    1. 03 · edge

      Worker

      Serves your workers.dev URL and routes requests inward.

    2. 04 · 1 GiB

      Container

      Your real Node/Nitro Eve server, started by Eve itself.

GET /eve/v1/health → 200

Eden promotes the deployment only after the new URL answers healthy.

02 · What stays yours

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
03 · The whole CLI

Three commands. That's it.

every command takes --json
  • eden preflight

    Read-only check of your Eve project, Cloudflare access and target name. Optional; deploy runs the same checks.

  • eden deploy

    Builds, publishes and health-checks one exact target. Preview by default, named from package.json.

  • eden destroy --name

    Removes one exact Eden-owned deployment after checking its ownership record. Never touches look-alikes.

04 · Before you deploy

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
Eve's new home is one command away

Deploy the Eve agent
you already have.

npm install --global @moinulmoin/eden