Skip to content


Runners are machines that run submitted workflows and their jobs. dstack supports two types of runners: on-demand runners and self-hosted runners.

On-demand runners are created automatically by dstack (in the computing vendor, configured by the user, e.g. AWS) for the time of running workflows. Self-hosted runners can be set up manually to run workflows using the user's own hardware.

On-demand runners

To use the on-demand runners, go to the Settings, then AWS.

Here, you have to provide AWS Access Key ID and AWS Secret Access Key that have the corresponding permissions to create EC2 instances in your AWS account:


Once you've provided credentials, use the Add limit button to configure limits:

The configured limits represent the maximum number of EC2 instances of the specific Instance type and in the specific Region, that dstack can create at one time to run workflows.

Note, using certain Instance type with your computing vendor may require you to request the corresponding service quotes from their support.

Self-hosted runners

As an alternative to on-demand runners, you can run workflows on your own hardware.

To do that, you have to run the following command on your server:

curl -fsSL -o
sudo sh
dstack-runner config --token <token>
dstack-runner start

Your token value can be found in Settings:

If you've done this step properly, you'll see your server on the Runners page:


Currently, dstack supports only AWS. If you'd like to use dstack with other computing vendors, please upvote the corresponding requests: GCP and Azure.

If you'd like to use dstack with your existing Kubernetes cluster, upvote this request.

Finally, if you'd like dstack to manage infrastructure on its own so you can pay directly to dstack for computing instances, please upvote this request.

Back to top