Can eve be self hosted?

[sadler-energycx]

Can i self host eve on my own infrastructure? What would i be missing out on? could Vercel expose that piece?

[ziggy-orbital]

ye, self-hosting is fully supported. eve build && eve start produces a standard Nitro Node server you can run anywhere (container, VM, behind your own proxy) see the Deployment guide . Every Vercel-coupled bit has a portable swap:

• Durability: off-Vercel the Workflow SDK uses its local world (run state on disk under .workflow-data), or you can point experimental.workflow.world at e.g. a Postgres world.
• Sandbox: defaultBackend() falls back to Docker / microsandbox / just-bash, or a custom SandboxBackend.
• Model: AI_GATEWAY_API_KEY for Gateway routing, or a direct provider model (@ai-sdk/... + that provider's key).
• Auth: httpBasic() / jwtHmac() / oidc() / custom instead of vercelOidc().

one thing tho: a reverse proxy must forward both /eve/ and /.well-known/workflow/. only proxying /eve/ lets sessions start but stalls runs (the workflow callbacks never arrive).

What you give up are the Vercel-only conveniences: the Agent Runs dashboard (use the OpenTelemetry exporters for tracing instead), Vercel Cron, sandbox prewarm, latest-deployment routing, and domain-level sandbox network allow-lists (the Docker backend is allow-all/deny-all only). Core runtime behaviour is identical either way.

Personally I would just run on vercel, I love the AI gateway for testing different models. In general tho I use a gemini api key. Running on vercel makes CI/CD and management super easy for me and doesn't cost anything for a small personal project. But that's just my opinion of course :)

[JesseXia]

Can I use eve with aws agentcore runtime?

[jjuanramos]

interested about this, too! will be easier to justify using eve inside my co if we know we're not locking us in Vercel

[HADIL19]

Yes, self-hosting eve would be interesting. The main things you would likely miss are the managed infrastructure pieces: sandbox provisioning, container lifecycle management, scaling, security isolation, and operational tooling.

It would be helpful if Vercel could document which parts are fully open-source and which parts rely on Vercel-managed services. That would make it easier to understand what a complete self-hosted deployment would require.