Host Terms
These terms apply when you connect a machine of your own to the platform, so that other participants can rent it or so that it serves models in a pool. They add to the Test Terms and the Acceptable Use Policy and do not replace them.
1. What connecting a machine means
1.1. You install the ServerShare agent on a machine you own or are entitled to use this way. The agent reports the machine to the platform and runs virtual machines on it when the platform asks.
1.2. You are responsible for being allowed to do this: by the owner of the hardware if it is not you, by your employer if it is theirs, by the provider of your network and power, and by the law where the machine is.
1.3. Electricity, network traffic, wear of the hardware and anything else the machine costs you to run are yours. During the test nothing is paid out: work done on your machine is accounted for in test credits, which have no monetary value (Test Terms, section 2).
2. What the platform collects about your machine
2.1. The agent reports what the machine is — processor, memory, disks, accelerators, driver versions, operating system — and its state: load, memory in use, temperature and power draw of accelerators, and the measured speed of its uplink.
2.2. A machine in a model pool may be benchmarked: the platform sends it test requests and records how fast it answers. The results are shown to you and used to choose machines for requests.
2.3. The agent presents a fingerprint of its own build. This is not proof that the agent is unmodified, and the platform does not treat it as such.
3. What you must not do
3.1. Do not try to observe, read, copy or alter what runs inside a machine rented from your hardware, or what it sends and receives: its memory, its disks, its traffic, the requests a pool machine serves and their answers. Technically you may be able to (Test Terms, section 5); these terms forbid it.
3.2. Do not modify the agent, the virtual machine images or the software inside them, and do not report false information about the machine or its work.
3.3. Do not connect a machine you cannot keep reasonably available while it is rented out, and do not stop a rented machine to get around these terms.
4. Availability and stopping
4.1. You may take a machine out of service. Pause a pool machine first, so it finishes the requests it is serving; check that nobody is renting a machine before you switch it off.
4.2. Machines go offline, and the platform accepts that during the test. A machine that repeatedly drops sessions or answers badly may be paused or removed from a pool by an administrator.
4.3. An administrator may pause or disconnect your machines at any time, including when your account is suspended. Sessions of tenants on your hardware are then not under your control until your account is restored.
5. Changes
5.1. These terms have a version. A new version is shown to you in the panel and has to be accepted before you continue. A machine already connected keeps working meanwhile; connecting a new one requires the current version.
Version 1