The provider Console

The provider side of the Console is where you see your machines and GPUs, change what the app lets you change, and follow what they earn. Its pages: My GPUs, GPU earnings, Work history, Payouts and Settings.

Opening the provider side for the first time starts Becoming a provider. Its steps, in order:

• Country: the country where you are paid. Your payouts and taxes follow it; a business chooses the country where it is registered in the next steps.
• Kind: a personal GPU owner, with your own computers, or a data-center provider, which continues into an application an administrator approves before any device may enroll.
• Status: whether you supply GPU time as a business (an organization or a sole proprietor, with its name and registration) or as a private individual. In Estonia a person supplies GPU time only as a registered sole proprietor (FIE) or through a company.
• Agreement: read the Provider Agreement in full, accept it with the Common Clauses, and confirm separately the clauses its section 1.6 lists.
• Payout country: where your payouts are made. You choose the payout method later, on Payouts.
• Done: the provider account is open. Connect your first device.

The country locks at your first payout; after that only HIPS support changes it.

My GPUs lists your machines and, under each, its GPUs, with what each is doing right now. Each machine shows five conditions, apart, never folded into one:

A machine that has not reported for over a minute shows its conditions as last reported, marked stale. Pause all stops new jobs on every device at once, each running job finishing within its device's drain window; Resume all returns each device to the mode it held before its pause.

Each GPU is its own unit: it has its own state, its own check as a new GPU, and its own values of five settings. Pause this GPU stops new jobs on that GPU alone while the machine's other GPUs work on.

Above the list, the gates count your GPUs: how many report, are online, eligible, available and working now, each count holding the gates before it, and what your machines earned this period. Under them, each GPU is one hexagon in the lane of the state it is in, in the order of the gates: working, offered and waiting for work, not available now, paused, being checked, needing your action, not eligible, stale and offline. A machine's GPUs sit together with its name beside them, so a server whose GPUs are in different states appears in several lanes. Lanes with no GPU fold into one line, such as "None being checked or offline".

Each lane counts its reasons, and each reason says who acts on it and what ends it: you (a microphone in use, on battery, full screen, a pause you set, with Resume beside it), HIPS (a GPU being checked), buyers (a GPU waiting for work), or nobody, for a block that ends by itself, such as a GPU too warm. The working and waiting lanes list the models loaded instead. Choosing a gate, a lane or a reason lights up its GPUs; pointing at a hexagon names its GPU and lights up its machine in every lane, and choosing it opens that machine beside the lanes, with where it stops, what each GPU holds, what it earned this period and its card in the list. With one machine, it is open from the start.

Every new GPU is tested before HIPS counts it fully. What My GPUs says while that happens, and what it asks of you:

When a check waits, the GPU's page says on what: its machine offline (connect it and start the app), not available right now (the check runs when the machine is idle, on power and within your hours), the engine not installed yet (the app installs it by itself), no room on disk for the smallest model it can run (free some space or raise the cache budget), or something on HIPS's side, with nothing for you to do.

A machine or GPU that is not eligible says why, in these words, beside it:

Connect a device walks through three steps: get the app, connect in the app, and wait for the device to appear. On macOS and Linux it offers the one-line installer first and a package as the other way; on Windows, the package. In the app, choose Connect this device; it shows a code, a QR code and a link, which you approve at console.hips.com/device for your provider account. If the approval was denied or the code expired, start again in the app: it asks for a new code.

Coming with the next Console release: Connect many machines, where a provider creates an enrollment code (with an optional label, an expiry and a maximum number of machines), adds it to an install script, and every server that runs it joins the provider account with nobody approving each one; its GPUs go through the same checks. The code is shown once. Revoking it stops new servers from joining and leaves the connected ones as they are. End all machines, on a code that connected any, signs out every machine it connected after a confirmation in the code's row that gives the count; each stays in My GPUs, signed out, until it is connected again or removed, and the code stays as it is. Revoke all on your account page never signs out a machine connected with a code. The app takes codes from HIPS Provider 0.1.22.

A device's page shows its hardware, the app and engine versions, its connection and certificate, its location as HIPS read it from its network address, its level and the reasons behind it, the work it runs and the models in its cache. A GPU's page shows the same for one GPU: its state, its check, its own settings and what it earned. A GPU removed from its machine keeps its history and earnings, read-only.

A device's controls in the Console are the same settings as in the app: the availability mode, the weekly windows and time zone, the idle threshold, the drain window, the temperature limits, excluded models, the model cache's folder and budget, and the minimum price, with a pause for 1, 8 or 24 hours or until you resume. A change in the Console reaches the computer, and each control says whether it is applied on the device or still pending there. Customer models show as not yet available in the Community pool. Every setting, the ones the Console does not show included, is on the settings reference.

Settings also holds your defaults for new devices, among them light work and the daily work cap, so each computer you connect starts with your values.

The minimum price is set on the account, on a machine and on a GPU, each overriding the one above: a GPU uses its own price, else its machine's, else the account's. Use my account setting and Use my machine setting make a machine or a GPU follow again. Buyers never see it.

The provider's Settings hold the provider name, the country where you are paid, the notifications (device offline, device stops reporting, update available, settlement, payout status), by email or in the app, the Provider Agreement, the data-center application, and help.

Remove a device in My GPUs to stop it for good: HIPS revokes its certificates, and its history and earnings stay. Then remove the app from the computer (hips-provider remove). Removing the app alone leaves the device in My GPUs until you remove it there.