HyperView bills for connected time, so what you spend depends on how sessions are used, not on how many machines or users you have. These five controls keep it in check, most useful first.
Step 1 - Set an overage limit
Go to Admin > Account Settings.
Under General Settings, set Billing Overage Limit.
The limit is number 2.
Empty: no limit, so a script that never closes its sessions has no ceiling.
A number: the most overage hours you'll pay for each period.
0: no overage at all. Suits fixed budgets.
Step 2 - Close sessions you aren't using
An open session uses time even if nobody is in it.
Check Active Sessions on Admin > Billing. It should match the number of people working.
In Admin > Sessions, sort by Duration and check the longest.
In scripts, close the session in a
finallyblock, so an error can't leave it open.
Step 3 - Limit what each API key can reach
Give each integration its own API key, with access rules that only reach the systems it needs. A key that reaches five machines can't open sessions on five hundred, and Session Usage can then show each integration's time separately. See API keys and their permissions.
Step 4 - Know where the off switch is
Admin > Account Settings > Automation Enabled stops all automation in the account at once. If something is running away and you can't find which key, turn it off. See Secure the account.
Step 5 - Check usage weekly
Open Admin > Session Usage and group it By day, then By actor. Look for:
Time used on days nobody was working.
One API key growing faster than the others.
A jump that lines up with a deployment.
See Report on usage.