Last modified 2025-06-27 |
Understand HISE Billing
 | Abbreviations Key | |||
| AIFI | Allen Institute for Immunology | HISE | Human Immune System Explorer | |
| CPU | central processing unit | IDE | integrated development environment | |
| GB | gigabyte | USD | U.S. dollars |
At a Glance
This document explains which components contribute to your personal and team IDE billing expenses. It also describes the three HISE billing roles, explains budget quotas, and outlines some best practices for reducing your IDE expenses.
Components of IDE Billing Expenses
You incur cloud computing costs when you use HISE IDEs to store and process data. Even a stopped IDE incurs costs. Specific items that contribute to your monthly computing expenses are shown in the following table.
| Item | Costs based on |
| CPUs | Processing time (sec) in a running instance |
| Data-disk storage | Amount of provisioned space (GB), even if the storage is unused or the instance is stopped |
| Memory | Amount of memory allocated to a running instance (GB/sec) |
To minimize your personal IDE billing expenses, use the cost management tools outlined in this document. Stop IDE instances when possible and at the end of each workday, since stopped instances incur cloud computing costs only for disk space—not for CPUs or memory. Delete idle instances when they're no longer needed, since Google storage bucket space costs less than disk storage in the IDE.
For detailed cost management advice from Google, see the recommendations in Cloud Billing Overview. For questions about your individual or team quota, contact a billing user or administrator, or use the Support button to file a ticket.
Billing Roles
The information visible to you in HISE depends on your role. In granting permission to access IDEs and other cloud resources, administrators follow the principle of least privilege, giving users only as much access as they need perform their respective tasks. The following table summarizes the roles associated with IDE billing.
| Role | Description |
| Individual user (analyst) | Incurs individual IDE expenses, including memory, storage, and pipeline costs. Can view and track their individual and team quotas. |
| Billing user | Tracks expenses for an organization. Each organization has multiple accounts, and each account might have multiple projects. |
| Manager | Tracks organizational expenses as well as information on IDE billing for their direct reports and team. |
Quotas
A quota is the maximum amount (in USD) an individual, program, or organization is allowed to spend on cloud computing within a given time period. To monitor your quota, read your email notifications, and compare your personal IDE spending with the median team spending.
HISE users are notified by email as they approach various individual and team monthly caps. For example, you're notified by email when you reach 50% of your monthly quota. If you max out your monthly quota, you can't start a new IDE instance. In addition, any running instances are stopped, and active notebook jobs are canceled and returned to the queue, where they remain until the following month.
Related Resources
Manage NextGen IDE Instances (Tutorial)