Skip to main content
Compute updates spending information as your organization starts and stops resources. Owners and Admins can use the console to see the organization’s current costs and review changes to its balance.
Members cannot see organization-wide billing. They can see the instances they created and the active price shown for those resources, but the organization Owner manages the balance and payment settings.

​
Check the organization overview

Owners and Admins can use Overview for a quick picture of organization activity. Depending on the available data, the dashboard can show:
  • Current balance
  • Today’s spending
  • Spending during the current month
  • Current spend rate
  • Active instances and models
  • GPUs and vCPUs in use
  • Total uptime
The dashboard changes as people in the organization create, start, stop, or terminate resources.

​
Open Billing for the full account view

  1. Select Billing from the left sidebar.
  2. Check the Balance to see how many credits remain.
  3. Check the Current spend rate to see the combined hourly rate of active resources.
  4. Review Transaction history for credit purchases and transfers.
  5. Review Billing details when you need payment or invoice information.
Only the Owner can add credits or change billing controls. Admins can use the same information for monitoring, but their access is read-only.

​
Check which instances are contributing to spend

Open Instances and review the running-instance list. Owners and Admins can see all instances in the organization. Members see the instances they created. The instance table shows the configuration and active price for each resource. Use it to identify:
  • Instances that are still running
  • High-cost configurations
  • Duplicate or forgotten workloads
  • The person who created an organization instance, when that information is shown
If the current spend rate looks higher than expected, start with the Running tab. A workload left running by another person still draws from the shared organization balance.

​
Understand the current spend rate

The current spend rate is the total hourly price of resources running at that moment. It is a live estimate rather than the billing interval. Compute charges eligible usage per second. For example, an instance priced at €0.75 per hour that runs for 30 minutes contributes approximately €0.375 before any other applicable usage. The spend rate changes when:
  • Someone starts an instance
  • A new instance reaches Running
  • A running instance leaves the Running state, including while stopping or terminating
  • Hivenet Inference API usage starts or stops
  • The active configuration changes

​
Understand the time-remaining estimate

The sidebar may show an estimated Time remaining based on the organization’s current balance and spend rate. This estimate is not a fixed deadline. It can increase or decrease when:
  • The Owner adds credits
  • Auto top-up adds credits
  • Resources start or stop
  • Another person in the organization changes their workload
  • Active inference usage changes
Use it as a warning signal rather than a guarantee of runtime.

​
Reduce active spending

When you no longer need a running resource:
  • Compute instance: Stop it if you expect to continue later, or terminate it when the work is finished and you no longer need its local data.
  • Inference API deployment: Stop it if you want to keep the deployment configuration for later, or terminate it when you no longer need the endpoint.
Terminating a Compute instance permanently deletes the instance and its local data. Terminating an Inference API deployment permanently shuts down that deployment and makes its endpoint unusable.
For the full lifecycle explanations, see How to stop or terminate a Compute instance and Manage an Inference API deployment.

​
Investigate an unexpected charge

If organization spending does not match what you expected:
  1. Check every running instance, not only the ones you created.
  2. Review the active price and configuration of each instance.
  3. Check whether Hivenet Inference API workloads are active.
  4. Review transaction history for recent credit purchases or transfers.
  5. Note the organization name, affected instance IDs, and approximate timeframe.
  6. Contact Support through the console if the discrepancy remains.
Admins can investigate organization usage and billing details, but only the Owner can add credits, change payment methods, or configure auto top-up.

​
See also