Skip to main content
Compute uses prepaid credits held in an organization balance. Charges are deducted in real time while the organization runs Compute resources. Your role determines which billing information you can see and whether you can change payment settings.
Only the organization Owner can add credits, manage payment methods, or configure auto top-up. Admins have read-only access to organization billing. Members cannot view or manage billing.

​
Billing access by role

Members can still create and use organization resources. Their usage is charged to the shared organization balance, even though they cannot see its billing details.

​
Find billing in the console

Select Billing from the left sidebar. What appears depends on your role:
  • The Owner sees the balance, current spend rate, credit controls, auto top-up, billing details, and transaction history.
  • Admins can review spending, billing details, auto top-up status, and transaction history, but cannot change them.
  • Members see a notice that billing is managed by the organization Owner.
For an explanation of the role model, see How organizations work in Compute.

​
How the organization balance works

The balance belongs to the organization rather than to an individual person. Usage from running instances and Hivenet Inference API workloads draws from the same balance. The console shows:
  • Balance: Credits currently available to the organization, shown in EUR.
  • Current spend rate: The combined hourly rate of resources running at that moment.
  • Time remaining: An estimate based on the current balance and spend rate. It changes when resources start or stop.
The spend rate is shown per hour to make active costs easier to understand. Compute charges eligible usage per second, without an hourly minimum.

​
Add credits

Only the Owner can add credits.
  1. Open Billing.
  2. Under Add credits, enter an amount or choose one of the available credit packs.
  3. Select Complete payment.
  4. Complete the payment through Stripe.
  5. Return to Compute and confirm that the organization balance has updated.
Other Admins and Members cannot charge a payment method or add credits to the organization.

​
Configure auto top-up

Auto top-up adds credits when the balance falls below a threshold. Only the Owner can configure it.
  1. Open Billing.
  2. Find Auto top-up.
  3. Enable auto top-up.
  4. Choose the balance threshold.
  5. Choose how many credits to add when the threshold is reached.
  6. Save the configuration.
Transferring organization ownership turns off the existing auto top-up configuration. The new Owner must review the payment details and configure auto top-up again.

​
Review billing details and transaction history

Owners and Admins can review the organization’s billing details and transaction history. Transaction history records changes to the organization balance, including:
  • Credit purchases
  • Credits transferred when someone joins the organization
  • Other recorded credit transfers
Billing details and payment methods are managed through Stripe. Only the Owner can make changes, but Admins can view the information shown in Compute.

​
How charging works

  • Charges begin when an instance reaches Running and stop as soon as it leaves the Running state. Time spent stopping or terminating is not charged.
  • Running Hivenet Inference API endpoints also contribute to the organization’s live spend rate. See Understand Inference API billing for how replica charges start, change, and stop.
  • Stopping an instance pauses compute charges while preserving it for a later start.
  • Terminating an instance permanently deletes it and its local data.
If your organization has a contracted discount, the instance price reflects the effective hourly rate after that discount. A 100% discount therefore appears as €0 per hour.
If an instance runs for 12 minutes and 20 seconds, Compute charges for 740 seconds at that instance’s active price.

​
What happens when credits run low

Compute prevents workloads from starting without enough credits. As the organization balance approaches zero, running workloads may stop or be terminated to prevent a negative balance. Running Hivenet Inference API endpoints stop automatically when the organization reaches zero credit. The Owner can add credits or enable auto top-up to reduce the risk of an interruption.
Stopped and terminated workloads behave differently. Stopping preserves an instance temporarily; termination deletes its local data. Back up important files before the balance runs out.

​
Payments, receipts, and taxes

  • Payment methods: Available credit and debit cards are processed through Stripe.
  • Receipts: Stripe sends a receipt after a successful credit purchase.
  • Currency: Compute balances and prices are shown in EUR. Stripe may handle currency conversion for cards billed in another currency.
  • Taxes and VAT: Applied where required using the billing information supplied through Stripe.

​
Troubleshoot a payment

  • Card declined: Check the available funds, complete any required 3-D Secure prompt, or use another card.
  • Payment completed but credits are missing: Refresh Billing after a short wait. If the balance still has not changed, contact Support with the date, amount, and last four digits of the card.
  • Billing information is incorrect: Ask the organization Owner to update the details through Stripe.
  • You cannot add credits: Confirm that you are the organization Owner. Admins and Members cannot add credits.
Purchased Compute credits are non-refundable. If a payment error or confirmed technical fault caused an incorrect charge, contact Support so the case can be reviewed.

​
See also