Providers

Frontends ship to Vercel or Netlify. Providers are connected once on the Integrations page; tokens are stored encrypted, refreshed automatically, and disconnected if they go invalid.

Vercel

• Connect with a personal access token from your Vercel account; it's stored encrypted and only used at deploy time.
• Deploys are file-based to a project named after your draft, targeting production.
• Env vars are written to all targets (production, preview, development) at once.

Netlify

• Connect with a personal access token; Modus validates it when you save it.
• Deploys create or reuse a site and push files.
• Env vars are written at the site level.

Coming soon

• Cloudflare Workers: backend services on Cloudflare's edge runtime — Modus bundles the service into a Worker and injects its URL into your frontend as MODUS_SERVICE_{NAME}_URL. The pipeline is built; the integration shows as Soon until it opens.
• Railway: apps and databases with automatic environment sync. It shows as Soon on the Integrations page until it lands.

Connection status

The providers panel shows each as connected or not. If a token is revoked or expires, Modus disconnects it automatically and the UI shows "Not connected" with a reconnect link. Tokens are only ever decrypted at the moment of an operation.

Default selection

When you open Deploy, the modal lands on your first connected provider's tab.

Rollback

On Netlify, a previous production deploy can be restored in one click from the deploy history (or ask the Code chat to roll back).