CudaPad hosts

Your machines

Put a GPU you own on the registry. A small agent runs on the machine, reports the card it actually has, and keeps it visible as online.

Connect to manage your machines

Machines belong to the wallet that registered them. This signature manages hardware only — it cannot spend the compute pool.

What running a machine does today

Jobs sent to your machine are billed to the shared pool at your SKU's catalogue price. When a job finishes, 70% of what that job actually cost is recorded as owed to your machine. The rest stays in the pool — it is not a fee you pay.

Nothing is paid automatically. There is no transfer on this platform: an operator pays what is owed by hand and records it. Until that happens the figure is a debt to you, not a balance you hold and not something you can withdraw here.

Two words that are not the same

Verified: The card the agent reported matches the SKU you claimed. It stays verified through a power cut — it is a fact about hardware, not about being awake.
Online: The agent sent a heartbeat recently. A machine that heartbeats perfectly never becomes verified by doing so.

Up to 20 active machines per wallet. Setup, the opt-in flag for running jobs, and what the agent does when something goes wrong are in scripts/host-agent/README.md. Community machines also appear in the GPU catalogue.