Docs

Step-by-step guides for renting a dedicated DGX Spark and getting a model to answer on it, written by the founder who runs the fleet. New here? Start with the first evaluation. You need no SSH key: the browser terminal works as soon as the instance is running.

Renting from GPUwerk

Your first evaluation

Check compatibility, configure your rental, connect in the browser or over SSH, and export your results.

Start the rental guide

Start here

From the console to a shell on a Spark, in the browser terminal or over SSH with your own key.

First rental

Run your first model evaluation

Plan your spend, launch a preconfigured model, test it from a terminal, and export results before ending billing.

5 min read
Getting started

Use the in-browser terminal

A root shell on your instance from the console in one click, with no SSH client or key. How a session works and when it ends.

4 min read
Getting started

Create an SSH key and connect

ed25519 on macOS, Linux and Windows, the agent, a config alias, port forwarding, and fixes for the three errors everyone hits.

7 min read
Getting started

The tenant environment

Root in a Docker container, not a VM: the capability set, what /workspace survives, the startup hook, shared node storage and networking.

6 min read
Getting started

Connect to the VNC desktop

Optional graphical desktop: open it in the browser, or connect from Linux, macOS or Windows, directly or through an SSH tunnel.

5 min read
Getting started

DGX Spark setup: unboxing to first token

DGX OS first boot, drivers, and serving your first model on hardware sitting on your own desk.

4 min read
Models

Which models fit in 128 GB

The weights-plus-cache arithmetic, why MoE models win on this hardware, and current Hugging Face repos that fit. With the ones that do not.

10 min read
Reference

LLM and GPU terms explained

Prefill, decode, KV cache, unified memory, quantization, mixture-of-experts, active vs total parameters and memory bandwidth, defined plainly, with links to GPUwerk's measured numbers.

reference
Reference

API reference

Bearer token authentication, every customer-facing endpoint with request and response shapes, error codes, per-route rate limits, and the versioning policy.

reference

Serving models

Turning a box with weights on it into an endpoint other software can call.

Memory on DGX Spark is unified. The Spark's 128 GB is shared between GPU and CPU, so the OS, SSH, and any JIT compiler your server runs at startup all draw from the same pool as the model. Leave headroom rather than maxing out --gpu-memory-utilization or --mem-fraction-static; see the memory section on the vLLM page for the numbers.

Interfaces and gateways

The layer between your endpoint and the people who will use it.

Training and tuning

When prompting has run out of road and the model needs to learn your data.

Fine-tuning

Fine-tune a model on your company's data

LoRA on 70B-class models fits in 128 GB of unified memory, with the training set staying on the node's local NVMe.

11 min read
Fine-tuning

Serving a LoRA adapter with vLLM

Hot-swapping adapters on one base model, and when a merged checkpoint is the better answer.

coming soon

Choosing hardware

Whether this machine is the right one, argued honestly.

Background reading

Longer arguments about why any of this is worth doing on your own hardware.

First top-up: pay $10, get $20 in credit

Try the commands on a dedicated Spark.

$0.79/hour in EU-Central, billed per minute. $20 of credit is about 25 hours of compute. Start with the first evaluation guide.

Create account

Something missing?

If you hit a wall these docs did not cover, say so and I will write it up. The gaps customers find are the ones worth filling first.

Request a guide