Deploy

This release supports one local Node 24 Runtime process with SQLite, a connected customer executor, and optional local Studio.

Your clients  ──HTTP / SSE──►  Runtime (persistent)
Your executor ──claim/result─►  Runtime
Studio        ──local proxy──►  Runtime

Runtime owns sessions, checkpoints, the model vault, and action leases. Your application owns agent implementations and talks to Runtime as a client and as an executor. There is no “your code hosts the Runtime” model for generated projects.

Host Runtime, then attach

nylorun up
npm run build
nylorun serve --no-autostart

nylorun serve loads dist/agents/index.js, attaches to the local Runtime on loopback port 8787 (--port or PORT override), and connects the SDK executor. It does not start Studio or watch files. If no Runtime is listening it starts one in the background and leaves it running unless you pass --no-autostart.

For a container or any supervised deployment, start the host explicitly — nylorun up, or run @nylorun/runtime/server as its own process — and pass nylorun serve --no-autostart so a missing Runtime fails the process instead of spawning an unsupervised one.

npm start is nylorun serve. A fuller production install looks like:

npm ci
npm run build
npm ci --omit=dev
nylorun up
npm start -- --no-autostart

Keep dist/, the package manifest and lockfile, production dependencies (@nylorun/agents, @nylorun/cli and their tree), and .nylorun/. Studio is a development dependency and is not started.

If you run that process on a machine you own:

• Use Node 24 or newer.
• Keep .nylorun/ private and persistent across ordinary restarts. It contains local credentials, the model provider vault, SQLite, and the Runtime log.
• Honor PORT (local default 8787).
• Keep one process per SQLite file.
• Leave Studio off this process.
• Authenticate any public endpoint yourself. Local CLI credentials are not a public auth system.

This path is the local OSS Runtime (beta). Cloud Runtime is coming soon. There is no verified Docker, Vercel, Workers, or Railway recipe in this release. Do not reuse old Hono, Worker, Vercel, or exported-fetch recipes with this Runtime.

Historical 0.13 hosting steps are on Migrate from 0.13.

Next step