Skip to main content
Before you can run production workloads on Trigger.dev, you need to deploy your tasks. The only way to do this at the moment is through the deploy CLI command: 
npx trigger.dev@latest deploy

​
Deploying 101

Let’s assume you have an existing trigger.dev project with a few tasks that you have been running locally but now want to deploy to the Trigger.dev cloud (or your self-hosted instance). First, let’s make sure you are logged in to the CLI (if you haven’t already): 
npx trigger.dev login
This will open a browser window where you can log in with your Trigger.dev account and link your CLI. Now you can deploy your tasks: 
npx trigger.dev deploy
This should print out a success message and let you know a new version has been deployed: 
Trigger.dev (3.3.16)
------------------------------------------------------
┌  Deploying project
│
◇  Retrieved your account details for [email protected]
│
◇  Successfully built code
│
◇  Successfully deployed version 20250228.1
│
└  Version 20250228.1 deployed with 4 detected tasks
Now if you visit your Trigger.dev dashboard you should see the new version deployed: