Deploy to Vercel

Deploy an eve agent with Vercel Workflow, Sandbox, Cron, and project credentials.

Deploy eve to Vercel when you want the framework’s managed build and runtime integrations. Vercel runs the web service, workflows, sandboxes, schedules, and deployment observability.

Prepare the Vercel project

Link the agent directory to a Vercel project:

eve link

The command links an existing project or creates one, then pulls its environment variables. For non-interactive use, name the project instead of picking it:

eve link --project your_project_name --non-interactive

Use --team as well when the account has access to more than one team. eve link creates the project if it doesn't exist yet.

Configure credentials and auth

A string model ID routes requests through the Vercel AI Gateway. The deployment authenticates through project OpenID Connect (OIDC), so you don’t need a provider API key for that path.

Add credentials for direct model providers, tools, and connections to the Vercel project environment. Add any signing keys or passwords required by your route authentication policy. Replace placeholderAuth() before a browser sends a production request.

Select the sandbox backend

Leave the sandbox backend unset to use defaultBackend(). On Vercel, it selects Vercel Sandbox. You can also select the backend explicitly:

import { defineSandbox } from "eve/sandbox";
import { vercel } from "eve/sandbox/vercel";

export default defineSandbox({
  backend: vercel(),
});

See Sandbox for resource limits, network policy, and lifecycle hooks.

Sandbox prewarming

During a Vercel build, eve automatically creates or reuses a sandbox template when your sandbox has bootstrap() or seed files. The build needs permission to create Vercel Sandbox templates, and a prewarm failure stops the deployment. See the sandbox lifecycle for template and session setup.

Deploy the agent

Deploy the linked project to production:

eve deploy

eve deploy installs dependencies, runs vercel deploy --prod, and pulls the project environment after deployment. You can also push to a Git-connected Vercel project. Hosted Vercel builds set VERCEL, so eve build writes the deployment bundle under .vercel/output.

For non-interactive use, confirm the production deploy up front. --project links first, so a new project needs no separate eve link:

eve deploy --project your_project_name --non-interactive --yes

Vercel uses the generated output to configure these services:

Web runtime: serves health, session, stream, channel, callback, and schedule routes
Vercel Workflow: persists and resumes durable runs, with optimistic replay preconditions enabled so stale event-log snapshots reload before they can commit
Vercel Cron: invokes authored schedules
Vercel Sandbox: runs sandbox sessions selected by defaultBackend()

Verify the deployment

Check the health route and connect the development TUI:

curl https://your_agent.vercel.app/eve/v1/health
eve dev https://your_agent.vercel.app

Set VERCEL_AUTOMATION_BYPASS_SECRET locally before connecting if the deployment uses Deployment Protection.

Inspect agent runs

Vercel detects eve and can add an Agent Runs tab under the project’s Observability view. Use it to browse sessions and inspect each conversation trace.

The Agent Runs tab requires enablement for your Vercel team. Contact your Vercel representative if the tab doesn’t appear. For third-party tracing backends, configure OpenTelemetry instrumentation.

Continue configuring production

Use these guides to secure and observe the deployed agent:

Authentication: configure who can call the deployed agent
Observability: export traces and diagnose runtime failures
Sandbox: configure resources, isolation, and network access