Choose a deployment path

Deploy a Convoy instance once for your team. Each developer who wants to execute AI threads then connects their own machine. People who only manage tasks can use the web app without the CLI.

Managed hosting

Use managed Convex for the backend and a Next.js host for the web app. The documented web-host example is Vercel. Follow this order so each credential is ready before the next step needs it:

1. Auth and Clerk. Create the Clerk app, configure the convex JWT template, and copy the issuer and app keys.
2. Deploy the Convex backend. Set the issuer, deploy the functions and schema, and record the deployment URL.
3. Deploy the web app. Configure the backend connection and Clerk keys on your web host.
4. Email and Resend. Configure email if your team needs invitation delivery.
5. Production checklist. Verify sign-in, permissions, uploads, and a connected runtime before launch.

Docker

Docker deployment runs the backend, dashboard, and web app using the bundled Compose setup. It still requires Clerk; Resend is optional. Follow that recipe directly instead of the managed Convex and Vercel steps above.

You own backups, upgrades, network access, and availability on this path. Read its validation status, then use the same production checklist.

After launch

Operations covers upgrades, migrations, monitoring, and recovery. The environment variable reference shows which settings belong in Convex, the web host, or a local environment.

The public docs site is a separate application. Contributors can follow Deploying the docs site when publishing it.