Become a host In testing

Your machine keeps being yours. The agent builds virtual machines on it when you let it, hands them to renters or to a model pool, and stops the moment you say so. During the open test, hosts receive test credits only: no money is paid, and credits have no monetary value.

What your machine needs

• A machine without the pieces above still registers and still works for you — it is simply not offered to renters, and the panel says which requirement is missing.
• NVIDIA cards are what the network offers to renters today. AMD cards are recognised but not offered In development.
• Guests need the machine to stay on and connected while they run. A machine that goes quiet is marked offline and stops receiving orders.

Install the agent

1. Download it

   Sign in to the panel and open the Host agent card. It lists every download for this release — system, kind, version, size and SHA-256 — with the recommended one for each system marked: the installer for Windows, the app for macOS. For Windows there is also a plain archive, for machines where an .exe does not get through or for installing by hand.

2. Run it

   On Windows the installer shows the terms, puts the agent into Program Files and sets up the service, a tray icon and a desktop shortcut. Neither the installer nor the macOS app is signed yet, so Windows SmartScreen and macOS Gatekeeper warn before the first start. Check the file against the SHA-256 the panel shows; the README in the macOS archive says how to open the app. The agent asks for your ServerShare login once, keeps a renewable token afterwards and never stores your password.

3. Leave it running

   On Windows it runs as a service, so it comes back after a reboot, and it updates itself: it stops taking new work, waits for what is running, swaps itself and restarts. On macOS a new release is installed from the panel.

Nothing else is needed from you — there is no approval queue and no interview. Your machine appears in the catalogue as soon as it reports that it can build virtual machines.

What the agent reports

• Your operating system and its version, the processor, memory and disk it can offer.
• The accelerator: model, vendor, memory, driver version and what it supports. This is what decides which renters and which pools your machine fits.
• A network speed measurement, taken regularly, and a short heartbeat every few seconds. The heartbeat is what makes the catalogue show you as online.
• Which build of the agent it is running. That is how we can retire a bad build quickly — it tells us what is deployed, it does not prove that the agent is unmodified.

What stays under your control

• Pause. Stop accepting new orders with one switch. Rentals already running keep running — you are not cutting off somebody mid-work — and resume when you are ready.
• Your own machines. Stop or delete any machine you hold on your hardware, including one serving a pool.
• Your terms. Every rental on your machine is a contract you sign. You can decline, and you can let standard terms be accepted automatically if answering each one is tiresome.
• Your hardware. The agent builds and runs virtual machines; it does not take your machine over. Nothing of a guest's is left behind: the system disk is rebuilt from the shared image on every start, and the guest's data volume becomes unreadable when the session ends.

Renting your machine out

1. An offer arrives

   Someone orders a machine on your host. The panel shows the contract: what they asked for, the price, and the trust level it is signed under. If you have linked Telegram, the bot tells you about it.

2. You answer

   Accept and the build starts; decline, with a reason if you want. An offer you leave alone expires within a day, and nothing was created in the meantime.

3. The machine runs

   It is billed by the minute, or for a fixed term agreed up front, and only for the minutes it was actually reachable.

The price comes from the platform's formula for the hardware you offer, adjusted for the quality of your host. You do not set it yourself Planned.

What you earn

• For renting a machine out you receive the full per-minute rate, credited every minute the machine served, with no platform commission.
• For serving a model pool, what the requests are worth is credited to you minus the platform's commission — see Model pools.
• Your balance and every entry behind it are in the panel. Entries are the record; the balance is computed from them, so it can always be explained.
• Test credits only. Nothing is paid out, and credits have no monetary value. Paid hosting is Planned for after the test.

What hosting does not give you

Renting out your machine does not give you a way into what runs on it:

• You cannot open a renter's console, move their files, or reach the services they published from their machine — those answer to the renter.
• You cannot read their data volume: its key is issued to the machine, never to your agent. The same goes for the results they ship to platform storage, which are encrypted before they leave the machine.
• Your agent's one channel into a guest is delivering the GPU driver.

The honest other half: because the machine runs on hardware you control, nothing stops you from watching it while it runs. We tell renters exactly that, which is why they accept a trust level before ordering, and why hardware attestation is In development and not shown to renters rather than claimed.

Next

• Model pools — keep a model loaded and serve the network instead of waiting for a renter.
• Host Terms — what you accept when your machine joins.
• Rent a machine — the same story from the renter's side.