Edge runtimes

The Vendo server targets Web-standard JavaScript, not Node. A CI gate bundles the server entry for a Worker target and boots it under workerd on every change, so the wiring below stays supported.

Wiring

Run npx vendo init --framework custom (detection lands here automatically when the host is neither Next.js nor Express). It generates vendo/server.ts: a lazy composition that takes Request in and returns Response, with the environment passed per call. Route your runtime’s requests through it:

// Cloudflare Workers (wrangler.toml: compatibility_flags = ["nodejs_compat"])
import { handleVendoRequest } from "./vendo/server";

export default {
  fetch: (request: Request, env: VendoEnv) => handleVendoRequest(request, env),
};

// Bun / Deno / Hono — serve /api/vendo/* through the same function
app.all("/api/vendo/*", (c) => handleVendoRequest(c.req.raw));

The client side is unchanged: mount <VendoRoot components={registry} theme={theme}> with <VendoOverlay /> in your SPA entry.

The three rules

Construct lazily. createVendo() performs no I/O and starts no timers at construction, but the generated lazy-singleton shape is still the contract: Workers forbids async work in module scope, and env vars only exist per request there.
Pass adapters explicitly. The dev credential ladder and the local PGlite/Postgres store engines are Node-only and refuse with guidance on edge runtimes. With VENDO_API_KEY the generated wiring fills every seam with the Cloud adapters — the model is the stock @ai-sdk/anthropic provider pointed at the console gateway. Without a key, pass your own model, store, connections, and sandbox.
Set VENDO_BASE_URL to the deployed origin. Present-credential forwarding fails closed without it, and vendo doctor checks it (E-AUTH-001).

What works where

Seam	Node	Edge
Store	PGlite / Postgres / hosted	hosted (`VENDO_API_KEY`) or custom
Model	dev ladder / any AI SDK model	explicit model (gateway or BYO)
Sandbox	e2b / Cloud / custom	Cloud or custom
Telemetry	anonymous, opt-out	no-op

vendo doctor judges unknown-framework hosts by their wiring (E-WIRE-007/E-WIRE-008), never by another framework’s file layout.

Start here

Bring your own agent

Use Vendo's agent

Connect your app

Make it yours

Give it reach

Ship it

For coding agents

Reference

Changelog

Edge runtimes

Wiring

The three rules

What works where

​Wiring

​The three rules

​What works where

Wiring

The three rules

What works where