Practical overview
When it fits
Use Dstack when AI development, training or inference workloads need GPU compute provisioned and coordinated across cloud, Kubernetes, virtual-machine or on-premises environments.
Who it is for
- AI developers who need managed GPU development environments.
- Teams running training or batch jobs across GPU clouds, Kubernetes or on-premises compute.
- Operators deploying model inference services on GPU infrastructure.
- Teams managing GPU resources across more than one infrastructure environment.
Documented uses
- Provision and manage compute fleets across supported infrastructure.
- Launch development environments for IDE or agent access.
- Run training, batch and other jobs on a node or across clusters.
- Deploy model inference as endpoints.
- Manage instance and network volumes for persistent data.
Requirements & limits
Dstack is available as a public-source repository under the Mozilla Public License 2.0.
- A Dstack server must be set up before using the CLI or API.
- GPU cloud and Kubernetes use requires backend configuration; on-premises servers can be managed as SSH fleets without backend configuration.
- The documented server and CLI prerequisites include Git and OpenSSH.
- The project lists NVIDIA, AMD, Google TPU and Tenstorrent accelerator support.
- Presets for agent-driven inference optimization are identified as experimental.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up a local Dstack server and connect the CLI
Install the Dstack server and configure the CLI to address it.
Before you start
- Git and OpenSSH
- Linux, macOS or Windows with WSL 2
- The documented server installation uses uv
Steps
Install Dstack with the command below.
uv tool install "dstack[all]" -UStart the server with
dstack server.Install the CLI separately with the command below if it was not installed with the server.
uv tool install dstack -UConfigure the CLI with the server address, user token and project name using
dstack project add.
Expected outcome
A running Dstack server and a CLI project configuration pointing to that server.
Guide limitations
- This covers server and CLI setup only; it does not configure a compute backend or run a workload.
- The server address and token must correspond to the server being configured.
Compare options for Model inference and serving
These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.
| Project | Documented purpose | Platform | Access and requirements |
|---|---|---|---|
| Dstack | Provision and manage compute fleets across supported infrastructure. | Cloud, Docker, Self-hosted, Server | Dstack is available as a public-source repository under the Mozilla Public License 2.0. |
| Morphingdb | Import a libtorch model and create predictions from values in a PostgreSQL table. | Docker, Linux, Self-hosted, Server | The README documents a Docker image and a build-from-repository option, followed by connecting to PostgreSQL and enabling the pgdl extension. |
| Gateway — pyadav | Send chat-completion requests to a provider through a common server endpoint. | Server | The repository is public and identifies the project as Apache-2.0 licensed. README installation instructions include binaries, platform package managers and Docker. |
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- dstackai/dstack · Official homepage title · retained in its source language

