Repository navigation
Run configurations
Python 3.15
Run configurations now accept python: "3.15":
type: dev-environment
python: "3.15"
ide: vscodeThe default Docker image now preinstalls Python 3.11 to 3.15. Runs use the preinstalled build instead of downloading Python on every container startup. See python.
Backends
Lium
The release adds experimental support for Lium. The lium backend supports GPU runs, private Docker images, and volumes.
projects:
- name: main
backends:
- type: lium
creds:
type: api_key
api_key: ...dstack offer -b lium --group-by gpu
# GPU SPOT $/GPU BACKENDS
1 RTX3090:24GB:1 on-demand 0.4 lium
2 RTX5070Ti:16GB:1 on-demand 0.4 lium
3 A6000:48GB:1..5 on-demand 0.42..0.55 lium
4 RTX6000Ada:48GB:1 on-demand 0.8 lium
5 RTXPRO6000:96GB:8 on-demand 1.88..2.09 lium
6 H100:80GB:8 on-demand 1.97..3.75 lium
7 H200NVL:141GB:4 on-demand 4.5 lium
8 H200:141GB:1..4 on-demand 5.36..5.58 lium
9 B200:180GB:1..8 on-demand 5.5..7.5 lium
10 B300:270GB:1..8 on-demand 8..10 liumLium volumes use S3-backed storage, grow with usage, and can be mounted in any Lium region, so size and region are omitted:
type: volume
backend: lium
name: my-volumeGCP TPUs
Important
TPU offers are no longer suggested by default. If you use TPUs with the gcp backend, enable them with tpu: true before upgrading.
TPU support is experimental, and TPU offers used to appear for anyone with a GCP backend. It is now opt-in:
projects:
- name: main
backends:
- type: gcp
project_id: my-project
creds:
type: default
tpu: trueSee GCP.
UI
Offers
The Offers page now shows CPU offers as well. Turn off the new GPU toggle to see CPU cards, group offers optionally, and filter by GPU vendor. Each offer shows its hourly price, with price ranges for grouped offers.
The Fleet page has a new Offers tab with the offers matching the fleet, which helps check available capacity, including for CPU-only SSH and Kubernetes fleets. Fleet instances are now shown below the General section.
User projects
The Projects tab on a user page now lists the projects the user owns or has joined, with their role in each.
Blog
Qwen3.8-Flash-Next coding agents
A new post shows how a single 4xH200 node, optimized with dstack presets, serves 16 concurrent Qwen3.8-Flash-Next coding agents with roughly 3x lower latency than the available providers.
What's Changed
- Add the Qwen3.8-Flash-Next coding agents benchmark post by @peterschmidt85 in #4375
- Fix CloudRift API compatibility by @peterschmidt85 in #4380
- Make experimental GCP TPU support opt-in by @peterschmidt85 in #4376
- [UI] Add fleet offers and CPU cards by @peterschmidt85 in #4378
- Add Lium backend by @peterschmidt85 in #4377
- Wait for other jobs only before submitting to the runner by @un-def in #4390
- [UI] Show owned and joined projects on user pages by @peterschmidt85 in #4394
- Preinstall Python 3.11-3.15 into base Docker image by @un-def in #4393
- Bump base Docker image to 0.16 by @un-def in #4395
- Support Python 3.15 by @un-def in #4396
- Migrate Runpod backend to REST API v2 by @un-def in #4397
- Fix concurrent AWS security group creation by @jvstme in #4399
- Don't count requests rejected before routing as service hits by @vitostrokov in #4387
- Resend gateway config before re-registering services by @vitostrokov in #4388
New Contributors
- @vitostrokov made their first contribution in #4387
Full Changelog: 0.22.4...0.22.5