Deploy overview

One push and you're live: on the web, on mainnet, in front of users. Deploy isn't a chapter card: it lives behind the Deploy button in the hub's top bar, always available.

Push the frontend to Vercel or Netlify and let Modus inject the env vars your app needs automatically. Deploy from the modal or by asking in the Code chat; both run the same flow.

What it does

• Multi-provider deploy: Vercel and Netlify for frontends (Cloudflare Workers for backend services is coming soon).
• Framework auto-detection: Vite (React/Vue/Svelte), Next.js, static HTML.
• Env var automation: the vars your deploy needs, injected automatically, plus an env var editor in the modal.
• Deploy history: recent deployments with status, error reporting, and rollback on Netlify.
• Deploy by chat: the Code chat can deploy, check status, read logs, and roll back.

The layout

Deploy opens as a focused modal from the hub's header: a Vercel / Netlify switch at the top, deploy history and the env var editor in the body, and one Deploy action at the bottom. Backend services live in the Code IDE's Services view, not here.

The pages ahead

• Providers: connecting Vercel and Netlify
• Shipping a frontend: the deploy flow and frameworks
• Services & env vars: backend services and automated env