Can a renter misuse my DGX Spark?
A renter cannot log into your Spark, and what they do online does not come from your IP address. GPUwerk Platform installs GPUwerk's system, the Spark dials out through an encrypted tunnel, and renter traffic leaves from GPUwerk's address. Renters are GPUwerk's customers. A complaint about that use comes to GPUwerk. The safeguards below are what the installed software does, and where its limits are.
Six safeguards
- No open ports
- The Spark connects out over an encrypted tunnel; its firewall drops connections from your network, IPv4 and IPv6
- Renters kept off your LAN
- Blocked, and tested during burn-in
- Renter traffic exits through GPUwerk
- From GPUwerk's address, never yours
- Locked system
- No local login; SSH only for GPUwerk's operators, with short-lived certificates
- Wiped between renters
- One renter at a time on the whole machine
- TPM attestation
- Boot state checked at registration and on every boot
Does renting out a Spark open up my network?
No. The Spark needs no public IP address and no port forwarding. Once installed, its firewall accepts only DHCP, IPv6 neighbour discovery and replies to its own connections. Your other devices can't reach it, including SSH and the DGX dashboard that stock DGX OS opens; GPUwerk's tests cover this for IPv4 and IPv6.
Renters run in containers on a separate network inside the Spark. Those containers are refused private address ranges and the local network the Spark detects itself on. One burn-in test starts a container and tries to reach your router from it; the Spark is listed only if that fails and the container's public address differs from yours.
Renters' internet traffic goes through the tunnel and leaves from GPUwerk's address, so nothing a renter does online is traced to your IP. If the tunnel goes down, renters lose internet access rather than falling back to your line. The tunnel itself and the Spark's housekeeping (software updates, model and container image downloads, DNS and time) use your line, and renter traffic inside the tunnel counts against your bandwidth.
For extra separation, put the Spark on a guest network or its own VLAN if your router supports it. On a company network, ask IT for a separate VLAN that allows the outbound HTTPS and UDP the Spark needs.
How is the Spark locked down?
The install erases the drive and writes a fresh DGX OS with GPUwerk's setup. Every interactive account is locked, the local console logins and the desktop are off, and SSH is open only on the tunnel address, only to GPUwerk's operators, with certificates that last 30 minutes by default and an hour at most. The screen shows the status and "No local login; managed by GPUwerk."
The Spark's TPM proves its boot state to GPUwerk at registration and on every boot. Its secrets, such as the tunnel key, sit on an encrypted volume that opens only after that check passes. If the boot measurements change, the Spark is suspended and GPUwerk investigates.
Pairing is tied to the machine in front of you: the six-letter code appears on the Spark's own screen, and the console shows the serial number and a TPM fingerprint to compare before you confirm. Ten wrong codes within an hour lock pairing for an hour.
Whoever holds the machine controls its firmware and its install media. The TPM measurements cover the boot chain, not everything that runs afterwards. The locked system deters casual access. A breach of the partner agreement lets GPUwerk suspend the machine at once.
What can a renter do on my Spark?
Run their own workload in their own container, on the whole machine, one renter at a time. The Spark is wiped between renters. You never learn who the renter is and can't see their workload or data; the console shows only that the Spark is rented, since when, the hours and your earnings. Renters choose the location of their instance, and the partner agreement forbids tampering with the Spark or inspecting renter workloads.
GPUwerk is responsible for the renter
GPUwerk is responsible for what a renter does with the machine. The rental is GPUwerk's contract, under GPUwerk's customer terms. Those terms forbid unlawful content, attacks on other systems, unsolicited bulk email, phishing, malware and fraud, and GPUwerk can suspend the instance or the account. You are not a party to that contract. A complaint about something a renter did online, or a request about the address that traffic came from, goes to GPUwerk, because that address is GPUwerk's.
What GPUwerk can see
- Your business details: legal name, address, VAT ID if any, and the payout account.
- The machine: model, serial number, TPM fingerprint, the public address it connects from, its heartbeats, and the burn-in and network test results.
- Everything on the Spark itself, since GPUwerk administers it as root while it's listed. After the wipe there is nothing of yours on it.
GPUwerk installs nothing on your other devices, and the Spark's software doesn't connect to them beyond what any networked machine does, such as getting an address from your router.
What stays yours
The hardware stays your property, and so does the risk of damage or failure. Whenever it is idle, you can use the Spark yourself through "Use my Spark" in the partner console, at no charge. To take it back, unlist it and restore the stock system with the maker's recovery USB. Unlisting during a rental forfeits that rental: you lose the earnings from its last 24 hours, and the Spark stays paused for 24 hours so the renter can copy data off.
Questions owners ask before listing
Is it safe to let strangers run code on my GPU?
Yes. A renter's code runs in a container on a separate network inside the Spark, refused private address ranges and the local network the Spark detects itself on. Before the Spark is listed, a burn-in test confirms that a container can't reach your router and that its public address differs from yours.
Can GPUwerk or the renter see my files?
Renters can't: they can't reach your other devices, and nothing of yours is on the Spark, because the install erases it. GPUwerk installs nothing on your other devices and the Spark's software doesn't connect to them; GPUwerk does administer the Spark itself as root, so use a guest network or its own VLAN if your router allows.
Do I need to open ports to rent out my DGX Spark?
No. The Spark connects out through an encrypted tunnel, so there is no port forwarding and no public IP address. Some other hosting programmes do need open ports; the platform comparison lists their rules.
Can renter traffic be traced to my IP?
No. Renters' internet traffic leaves from GPUwerk's address, and if the tunnel goes down they lose internet access rather than falling back to your line. The tunnel itself and the Spark's housekeeping, such as updates and model downloads, use your line, and renter traffic inside the tunnel counts against your bandwidth.
Some GPUwerk guides mention a Spark's public IP. Is that my home IP?
No. The public address renters get belongs to GPUwerk, not to you. Your Spark has no public IP address of its own: it connects out through an encrypted tunnel and opens no ports, and renters' internet traffic leaves from GPUwerk's address, never yours.
Who patches a listed DGX Spark when NVIDIA publishes a security bulletin?
GPUwerk installs and updates the operating system while the Spark is listed. You don't update firmware yourself unless GPUwerk announces a security advisory.
What if a renter damages my hardware?
Under the partner agreement the hardware stays your property and your risk, whether or not the Spark is rented at the time. Check what your own insurance covers before you list it.
What if a renter misuses my Spark?
The Spark runs GPUwerk's locked system, with no local login. Renter traffic leaves through an outbound tunnel from GPUwerk's address, not yours. Renters contract with GPUwerk, and complaints about that use go to GPUwerk. The hardware itself stays yours.
Ready to list? The requirements and setup page has the checklist, and the earnings calculator runs the numbers with your own hours and power price. Earnings depend on renter demand and are not guaranteed.