Provider setup

HIPS Provider is the app that offers your computer's spare GPU time to HIPS. It watches whether you are using the computer, takes work only within your schedule and your minimum price, and stops new work the moment you come back, giving a running job a short window to finish. You see what each GPU does and earns in the provider Console's My GPUs.

• A computer with a GPU HIPS works on: NVIDIA, AMD, Apple Silicon or Snapdragon. Intel GPUs are not supported, and nothing runs on the CPU alone. Another GPU of the same machine works as usual.
• A HIPS account with a provider account: in the Console, open the provider side and follow Becoming a provider (the provider Console has the steps).
• An internet connection the app can keep open to HIPS.

The download page has every package of the newest release, and Connect a device, on the provider side of the Console, offers the package for each system and the one-line installer. A test build that is not yet signed opens on macOS with a right-click and Open, or in System Settings, Privacy & Security, Open Anyway; on Windows with More info, then Run anyway.

On Linux and macOS, one command downloads the newest release, checks that HIPS's release key signed it and that the package matches, installs it, starts the service and hands over to hips-provider setup, which links the computer to your account:

00000000000000000000000000000000000000001curl -fsSL https://hips.com/install.sh | bash

The script is plain POSIX sh, so | sh runs it too, and you can read it before you run it. It installs nothing if the signature or the checksum does not match. On Linux it uses apt or dnf only for a dependency the system lacks, and on an AMD GPU it installs the Vulkan loader and Mesa's Vulkan drivers where they are missing; it never restarts the computer itself.

00000000000000000000000000000000000000001curl -fsSL https://hips.com/install.sh | HIPS_MODE=auto bash

On Windows, run the .msi; it installs the service and the tray program.

Setup, or Connect this device in the app, signs the computer in to your account by device authorization: the app shows a code, a QR code and a link. Open the link, scan the QR code with your phone, or type the code at console.hips.com/device, and approve HIPS Provider for your provider account. A computer with no screen of its own runs hips-provider connect, which shows the same code, a QR code drawn in the terminal and the link. The computer then appears in My GPUs.

00000000000000000000000000000000000000001hips-provider connect

Before a new GPU takes paid work, HIPS tests it: My GPUs says "Being added to the network", which can take up to a few hours and needs nothing from you. A GPU may take work while it is checked, and what it earns meanwhile is held until the check passes. What each state and eligibility reason means is on The provider Console.

• My GPUs names, for each machine and each GPU, the reason it is not taking work and what to do about it; most reasons need nothing from you.
• hips-provider status prints the computer's sheet, with the level and its reasons; hips-provider logs shows the newest lines of each log.
• hips-provider support bundle saves a zip of the logs, the settings, the device facts, the versions and the crash reports on your computer, to attach to a support request. Nothing is sent to HIPS.
• The app sends crash reports unless you turn them off: Crash reports says what a report carries and never carries.

To stop for good, remove the computer in My GPUs, which revokes its certificates, then remove the app. hips-provider remove stops work, deletes the model cache and the crash queue, and has the updater remove the rest; the tray program and the menu-bar app offer the same. On Linux, sudo hips-provider service uninstall removes every service, the files, the state and the service account. Removing the app leaves the device in My GPUs until you remove it there.

00000000000000000000000000000000000000001hips-provider remove

• When your computer works: How HIPS Provider decides, second by second, whether your GPU may take work: the three levels, every reason, the blocks you may lift, and the drain when you return.
• Command reference: Every hips-provider command and flag: the terminal view, setup, status, pause and resume, GPUs, settings, the minimum price, the cache, crash reports, logs, the support bundle, services and removal, with their exit codes.
• Settings reference: The 25 settings of HIPS Provider, what each means and its bounds, the five you can set per GPU, and the places you change them: the terminal view, the Settings window, My GPUs, the command line and the configuration file.
• The provider Console: Becoming a provider, My GPUs and what each condition and reason means, a new GPU's check, connecting devices, the controls you share with the app, the minimum price, and removing a device.
• Earnings and payouts: How GPU earnings move from estimated to paid, what is held while a new GPU is checked, batch work, the work history, monthly settlement, payouts to a bank account through Stripe, earnings taken as Credits, and the monthly Settlement Statement and self-billed invoice.
• Crash reports: HIPS Provider sends crash reports unless you turn them off: what a report carries, what it never carries, where you turn it off, and how to read every report it sent.
• Data centers: Run HIPS Provider on your servers: install it on a server or in Docker, pause it and hand GPUs back to your own clients, automate it and monitor it.