Skip to content
HIPS
  • Earn with your GPU
  • Pricing
  • Docs
Sign inJoin early access
⌘K

Get started

  1. 01Developer hub
  2. 02Quickstart
  3. 03Migrate to HIPS

Guides

  1. 04HIPS SDK
  2. 05Import and run your model
  3. 06Model and task guides
    1. ATask guides
    2. BLanguage (chat)
    3. CClassification
    4. DImage
    5. EVideo
    6. FAudio
    7. GDocument processing
  4. 07Batch jobs
  5. 08Prompt caching
  6. 09Coding-tool setup
    1. AClaude Code
    2. BOther coding tools and editor integrations
  7. 10Command line
    1. ASign in
  8. 11Console
    1. AAccount
    2. BWorkspaces
    3. CAPI keys
    4. DSettings
    5. EUsage
    6. FModels
    7. GPlayground
    8. HDeployments
  9. 12Billing
  10. 13Provider setup
    1. AWhen it works
    2. BCommands
    3. CSettings
    4. DProvider Console
    5. EEarnings
    6. FCrash reports
    7. GData centers
  11. 14Router
  12. 15Guardrails
  13. 16Knowledge

Reference

  1. 17API reference
    1. AAuthentication
    2. BChat completions
    3. CResponses
    4. DMessages
    5. ECount tokens
    6. FModels
    7. GTasks
    8. HEmbeddings and rerank
    9. IJobs
    10. JUploads
    11. KFiles
    12. LBatches
    13. MWebhooks
    14. NVector stores
    15. ODeployments
    16. PRequirements and headers
    17. QErrors
    18. RUsage
    19. SVersioning
  2. 18Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 19Changelog
Sheet indexProvider setup

Get started

  1. 01Developer hub
  2. 02Quickstart
  3. 03Migrate to HIPS

Guides

  1. 04HIPS SDK
  2. 05Import and run your model
  3. 06Model and task guides
    1. ATask guides
    2. BLanguage (chat)
    3. CClassification
    4. DImage
    5. EVideo
    6. FAudio
    7. GDocument processing
  4. 07Batch jobs
  5. 08Prompt caching
  6. 09Coding-tool setup
    1. AClaude Code
    2. BOther coding tools and editor integrations
  7. 10Command line
    1. ASign in
  8. 11Console
    1. AAccount
    2. BWorkspaces
    3. CAPI keys
    4. DSettings
    5. EUsage
    6. FModels
    7. GPlayground
    8. HDeployments
  9. 12Billing
  10. 13Provider setup
    1. AWhen it works
    2. BCommands
    3. CSettings
    4. DProvider Console
    5. EEarnings
    6. FCrash reports
    7. GData centers
  11. 14Router
  12. 15Guardrails
  13. 16Knowledge

Reference

  1. 17API reference
    1. AAuthentication
    2. BChat completions
    3. CResponses
    4. DMessages
    5. ECount tokens
    6. FModels
    7. GTasks
    8. HEmbeddings and rerank
    9. IJobs
    10. JUploads
    11. KFiles
    12. LBatches
    13. MWebhooks
    14. NVector stores
    15. ODeployments
    16. PRequirements and headers
    17. QErrors
    18. RUsage
    19. SVersioning
  2. 18Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 19Changelog
13
  1. Docs/
  2. Provider setup/
  3. When it works
(Detail A)
llms.txt

When your computer works

On this sheet8 sections
  1. Three levels
  2. Auto and Always
  3. What Always lifts
  4. What still pauses work in Always
  5. Every reason
  6. What you may lift
  7. When you come back
  8. Your limits

HIPS Provider reads the computer every second and decides how much HIPS work may run right now. It never names what you are doing: HIPS receives only the level, the reason codes below and numeric readings such as GPU and CPU use, never an application, a window, a game or a process.

Fig. 1, sheet 13Provider setup

Three levels

LevelIn My GPUsWhat runs
HIGHFull workFull jobs
LOWLight workLight work only while you use the computer lightly: small models, low priority, a capped GPU share. Nothing at all where you turned light work off
NONENo workNothing
  • Level
    HIGH
    In My GPUs
    Full work
    What runs
    Full jobs
  • Level
    LOW
    In My GPUs
    Light work
    What runs
    Light work only while you use the computer lightly: small models, low priority, a capped GPU share. Nothing at all where you turned light work off
  • Level
    NONE
    In My GPUs
    No work
    What runs
    Nothing

Blocks come first: any one of them makes the level NONE, and each one that holds is listed. Then the load rule: with no block, the level is HIGH while your own GPU and CPU use stay under the HIGH limits, LOW under the LOW limits, and NONE above them.

Auto and Always

ModeIn the appWhat it means
scheduledAutoWorks when you are not using this computer. HIPS checks whether you are at the keyboard, watching video, gaming or in full screen, and follows your schedule if you set one. Recommended for a computer you also use yourself
alwaysAlwaysThis computer is always available for work, even while you use it. Work still pauses for heat, your battery and low-power settings, heavy load from other programs, the daily cap or a pause. Meant for a dedicated machine. Not recommended for a computer you sit and work at
  • Mode
    scheduled
    In the app
    Auto
    What it means
    Works when you are not using this computer. HIPS checks whether you are at the keyboard, watching video, gaming or in full screen, and follows your schedule if you set one. Recommended for a computer you also use yourself
  • Mode
    always
    In the app
    Always
    What it means
    This computer is always available for work, even while you use it. Work still pauses for heat, your battery and low-power settings, heavy load from other programs, the daily cap or a pause. Meant for a dedicated machine. Not recommended for a computer you sit and work at

In Auto you count as away once there has been no input for the idle threshold (at least 120 seconds), the screen is locked, or nobody is signed in. A pause is not a mode: pause from the tray menu, in My GPUs or with hips-provider pause.

Auto is unchanged: every reason on this page can hold work in Auto. Always counts you as away whatever you do and ignores the schedule.

What Always lifts

Note

Coming in the next app release. In HIPS Provider 0.1.22, Always leaves out only your input and the schedule, and every other reason on this page still stops work, as in Auto.

Always gives the computer to HIPS even while you use it, so the signs that someone is at the computer no longer hold work back. None of these stops work in Always:

  • The microphone or the camera in use (microphone_in_use, camera_in_use).
  • An app in full screen, or a game running (fullscreen, game_running).
  • A video playing, or video being encoded for a recording or a stream (video_playing, video_encoding).
  • A remote session, Do Not Disturb or Focus, and the app's session helper not running (remote_session, do_not_disturb, helper_missing).

The app still reads each of them on the computer, and shows one that is on as "Active, not pausing work in Always". A lifted sign stays on the computer: it is never sent to HIPS, as a reason or as a signal, so My GPUs and the rest of the Console never show it, and in Always it is never the reason a computer is not working.

What still pauses work in Always

  • Heat: a GPU at its temperature limit, or the CPU throttled, which allows light work at most (thermal, cpu_throttled).
  • The wait after a display-driver reset (driver_reset).
  • Battery and low-power mode, each by its own setting (on_battery, low_power_mode).
  • The daily cap, once today's work time is used up (daily_cap).
  • A pause, yours or HIPS's (paused, operator_paused).
  • Other programs already loading the GPU or the CPU: the load rule, another program using the GPU for compute, and on a machine with no desktop session your own workload (gpu_load, cpu_load, gpu_compute_in_use, owner_workload).

These protect the computer, your battery and the buyer's request: a GPU or CPU that another program already loads would slow the job down or make it fail. A computer held in Always shows the reason that holds it, in My GPUs and in hips-provider status.

A machine with no desktop session, such as a DGX Spark or a Jetson, works by the owner-workload rule: no input gate, and the load of every process but HIPS's own decides, so an administrator's SSH login counts only through the load it makes. A data-center server reads no user signal and no load rule: it works whenever it is healthy, unless it is paused or in a maintenance window, a GPU is at its thermal limit, the CPU throttles or a driver reset holds it.

Every reason

What it does is what a reason does in Auto. The last column says whether it applies in Always, where Lifted comes with the next app release.

The reason codes, in the order the app lists them, and what each does in Always

CodeIn My GPUsWhat it doesIn Always
pausedPaused by youNo work until you resume, or the pause endsApplies
operator_pausedPaused by HIPSNo work until HIPS lifts itApplies
outside_hoursOutside your scheduleNo work outside the schedule's windowsNot used: Always has no schedule
daily_capToday's work time is used upNo work until the next local dayApplies
on_batteryOn batteryNo work; you may allow work above a charge levelApplies, by its own setting
low_power_modeLow power mode is onNo work; never liftedApplies
driver_resetWaiting after a GPU driver resetNo work for the back-off after a display-driver reset; a safety block nobody liftsApplies
thermalToo warm: paused until it coolsNo work while a GPU is at its limit or throttled; a safety block nobody liftsApplies
cpu_throttledThe CPU is throttledLight work at mostApplies
remote_sessionA remote session is openNo workLifted
camera_in_useThe camera is in useNo workLifted
microphone_in_useThe microphone is in useNo workLifted
do_not_disturbDo not disturb is onNo workLifted
game_runningA game is runningNo workLifted
fullscreenAn app is in full screenNo work; you may lift itLifted
video_encodingVideo is being encodedNo workLifted
video_playingVideo is playingLight work at mostLifted
gpu_compute_in_useAnother program uses the GPU for computeNo workApplies
user_activeYou are using the computerLight work at mostNot used: Always counts you as away
gpu_loadThe GPU is busy with your own workThe level your GPU use allowsApplies
cpu_loadThe CPU is busy with your own workThe level your CPU use allowsApplies
helper_missingThe app's session helper is not runningNo workLifted
owner_workloadYour own workload is runningThe level your own work allows, on a machine with no desktop sessionApplies
  • Code
    paused
    In My GPUs
    Paused by you
    What it does
    No work until you resume, or the pause ends
    In Always
    Applies
  • Code
    operator_paused
    In My GPUs
    Paused by HIPS
    What it does
    No work until HIPS lifts it
    In Always
    Applies
  • Code
    outside_hours
    In My GPUs
    Outside your schedule
    What it does
    No work outside the schedule's windows
    In Always
    Not used: Always has no schedule
  • Code
    daily_cap
    In My GPUs
    Today's work time is used up
    What it does
    No work until the next local day
    In Always
    Applies
  • Code
    on_battery
    In My GPUs
    On battery
    What it does
    No work; you may allow work above a charge level
    In Always
    Applies, by its own setting
  • Code
    low_power_mode
    In My GPUs
    Low power mode is on
    What it does
    No work; never lifted
    In Always
    Applies
  • Code
    driver_reset
    In My GPUs
    Waiting after a GPU driver reset
    What it does
    No work for the back-off after a display-driver reset; a safety block nobody lifts
    In Always
    Applies
  • Code
    thermal
    In My GPUs
    Too warm: paused until it cools
    What it does
    No work while a GPU is at its limit or throttled; a safety block nobody lifts
    In Always
    Applies
  • Code
    cpu_throttled
    In My GPUs
    The CPU is throttled
    What it does
    Light work at most
    In Always
    Applies
  • Code
    remote_session
    In My GPUs
    A remote session is open
    What it does
    No work
    In Always
    Lifted
  • Code
    camera_in_use
    In My GPUs
    The camera is in use
    What it does
    No work
    In Always
    Lifted
  • Code
    microphone_in_use
    In My GPUs
    The microphone is in use
    What it does
    No work
    In Always
    Lifted
  • Code
    do_not_disturb
    In My GPUs
    Do not disturb is on
    What it does
    No work
    In Always
    Lifted
  • Code
    game_running
    In My GPUs
    A game is running
    What it does
    No work
    In Always
    Lifted
  • Code
    fullscreen
    In My GPUs
    An app is in full screen
    What it does
    No work; you may lift it
    In Always
    Lifted
  • Code
    video_encoding
    In My GPUs
    Video is being encoded
    What it does
    No work
    In Always
    Lifted
  • Code
    video_playing
    In My GPUs
    Video is playing
    What it does
    Light work at most
    In Always
    Lifted
  • Code
    gpu_compute_in_use
    In My GPUs
    Another program uses the GPU for compute
    What it does
    No work
    In Always
    Applies
  • Code
    user_active
    In My GPUs
    You are using the computer
    What it does
    Light work at most
    In Always
    Not used: Always counts you as away
  • Code
    gpu_load
    In My GPUs
    The GPU is busy with your own work
    What it does
    The level your GPU use allows
    In Always
    Applies
  • Code
    cpu_load
    In My GPUs
    The CPU is busy with your own work
    What it does
    The level your CPU use allows
    In Always
    Applies
  • Code
    helper_missing
    In My GPUs
    The app's session helper is not running
    What it does
    No work
    In Always
    Lifted
  • Code
    owner_workload
    In My GPUs
    Your own workload is running
    What it does
    The level your own work allows, on a machine with no desktop session
    In Always
    Applies

What you may lift

  • The fullscreen block: set fullscreen_rule to false, and a fullscreen or presentation app in front no longer stops work.
  • The battery block: set power_rules to allow_above with a battery_min_percent, and work runs on battery above that charge. Low-power mode always stops work.
  • Nothing else in Auto. Always lifts the signs that someone is at the computer, as above, and leaves every other block in place.
  • In either mode, the thermal limit and the wait after a driver reset are safety blocks, and nobody lifts them: the driver's own temperature limit applies whatever your setting says, and the wait after a reset is at least an hour, longer if you set it so.

When you come back

The moment you return, or pause, HIPS stops sending new work, and a running job gets the drain window (drain_window_s) to finish before it is stopped. What a job cut short earns follows the Provider Agreement: a job ended by the device, its app or you earns nothing; one ended by HIPS, or canceled by a buyer after output began, earns the price of what it produced before it ended; one canceled before output, nothing.

Your limits

SettingWhat it limits
schedule and timezoneThe weekly windows, read in the computer's time zone or the one you name
idle_threshold_sHow long without input before you count as away; at least 120 seconds
load_limitsYour GPU and CPU use under which work runs at HIGH and LOW; each may be lowered, never raised above 30, 40, 20 and 30 percent
light_work_at_lowWhether light work runs at LOW at all
daily_cap_sThe most HIPS job time per local day
thermal_limitsYour GPU temperature at which work stops and below which it starts again
closed_lid_workOn a laptop, whether work goes on with the lid closed while it is plugged in; off unless you turn it on
  • Setting
    schedule and timezone
    What it limits
    The weekly windows, read in the computer's time zone or the one you name
  • Setting
    idle_threshold_s
    What it limits
    How long without input before you count as away; at least 120 seconds
  • Setting
    load_limits
    What it limits
    Your GPU and CPU use under which work runs at HIGH and LOW; each may be lowered, never raised above 30, 40, 20 and 30 percent
  • Setting
    light_work_at_low
    What it limits
    Whether light work runs at LOW at all
  • Setting
    daily_cap_s
    What it limits
    The most HIPS job time per local day
  • Setting
    thermal_limits
    What it limits
    Your GPU temperature at which work stops and below which it starts again
  • Setting
    closed_lid_work
    What it limits
    On a laptop, whether work goes on with the lid closed while it is plugged in; off unless you turn it on

Each setting, its bounds and where you change it are on the settings reference.

Related sheets

  • Settings reference
  • Command reference
Previous sheetProvider setup
Next sheetCommands
Sheet
13 of 19
Detail
A
Updated
2026-11-12
Sign in to the Console

On this sheet

  1. Three levels
  2. Auto and Always
  3. What Always lifts
  4. What still pauses work in Always
  5. Every reason
  6. What you may lift
  7. When you come back
  8. Your limits

Product

  • Inference
  • Models
  • Deploy your model
  • Always-on GPU capacity
  • How it works
  • Use cases
  • Pricing

Developer

  • Docs
  • Quickstart
  • Migrate to HIPS
  • HIPS SDK
  • Batch jobs
  • API reference

Provider

  • Earn with your GPU
  • Register GPU interest
  • Download for Mac
  • Download for Windows
  • Download for Linux

Resource

  • Security and Data
  • Resources
  • llms.txt

Compare

  • OpenRouter alternatives
  • Together AI alternatives
  • Groq alternatives
  • All comparisons

Company

  • About
  • Contact
  • Affiliate program
  • HIPS Payments

Legal

  • Legal
  • Consumer Health Data Privacy Policy
  • Report content
  • Cookie preferences

Support

  • Contact HIPS
  • Looking for payments support?

HIPS. AI inference for builders.

hips.com

Hyperscale Inference Processing Systems OÜ