Get your host ready.
Connect your Ubuntu NVIDIA machine directly to nafnaf. No other marketplace account or installation is required.
1. Install or update the agent
Get your install command from Provider setup and run it on your GPU host. Already connected? Run sudo nafnafd update. Updates wait for active nafnaf workloads to finish.
If a new NVIDIA driver needs a reboot, setup will show “Reboot required”. Reboot when ready and complete any Secure Boot enrollment requested on screen. Installation then continues automatically without rerunning the command.
The current agent checks the host automatically. Eligible, unallocated GPUs can accept bookings once the hardware and runtime checks pass. Keep Docker and existing workloads running.
The installer prepares rental storage automatically on Ubuntu, including hosts using ext4. It reserves up to 80% of free space, keeps at least 20 GiB available for your other applications, and needs at least 84 GiB free. Rental files have enforced disk limits.
2. Review your host and pricing
Open Your machines to check availability. Choose autopilot pricing or set your own rates and rental terms.
If setup is incomplete, run sudo nafnafd status on the host. Check runtime_ready, on_demand_ready and the reported diagnostic message. Incomplete host inspection retries automatically. If you previously disabled standalone bookings, review standalone_on_demand in your host configuration; its default is auto.
Keep tokens and full status output private. An idle GPU is only rentable when it is unallocated and the host is ready to accept a booking.
3. Understand availability
In use means a GPU is allocated, even if its utilization is zero. Finish host setup means a readiness check is blocking new bookings. Offline means recent heartbeats are missing.
Changing a listing price affects future bookings. Rentals keep their booked compute and storage rates. New rentals require enforced disk quotas and are billed for the full allowance the renter approves, including while paused, within their spending limit and available credit. If storage funding runs out, files are retained for 72 hours before permanent deletion. Data transfer is not billed. Deleting a workspace ends storage charges and removes its files.
Optional integrations
These settings apply only when you also offer the same host on a supported marketplace.
Co-hosting with Vast
The integration pauses new bookings there before starting a nafnaf rental, then restores your original listing afterwards. Existing rentals continue.
- In Provider setup, choose Connect Vast account.
- Create a Vast account API key with Machines Read and Write. Disable User, Instances, Billing/Earning and Miscellaneous permissions. Leave 2FA off for this key so agents can operate automatically; your account login can still use 2FA.
- Save the key once. The same key covers the machines it can manage in that Vast account. Nafnaf encrypts it on the backend and securely delivers it to your registered Vast hosts.
- Agents running 0.13.10 or later identify their machines and preserve the existing listing prices, volume settings and expiry automatically. Older agents need an update before they can sync.
The local credential is stored with root-only access. It is never included in installer commands or shown again in the dashboard. Hosts without Vast skip this integration. Disconnect in Provider setup to remove the backend credential; agents remove local copies after restoring active rentals. Revoke the key in Vast to invalidate every copy immediately.
New bookings on that marketplace pause for the whole machine during nafnaf rentals, including on other free GPUs. Existing allocations continue. A host with a detected or configured integration keeps those coordination checks across restarts.