Skip to content
DocsConsole

Billing & credits

Deposits, usage, receipts, and balance safeguards.

Add credits

Select Add credits in Billing and choose an amount from $5 to $5,000. Choose Card for Stripe Checkout or Crypto for Heleket. For crypto, select a coin and network on the hosted checkout and send the exact quoted amount before the invoice expires. Credits arrive after network confirmation. Pending crypto invoices can be reopened from deposit history. Underpaid or held payments may need support review. Automatic deposits still require a saved card. Credits appear only after the backend verifies a successful payment; returning from Checkout alone does not add funds. Deposit history includes pending, completed, and failed payments.

Open Billing

Compute usage

The hourly price is shown before you launch. Usage accrues from the provider’s creation timestamp, with the minimum charge disclosed at launch, until destruction is confirmed. The spend chart and machine breakdown include compute and bandwidth, so you can see which instances account for your charges. Reporting dates use UTC.

Only machines with a paid outbound transfer rate accrue bandwidth charges. For those machines, outbound transfer above the earned allowance is billed at the rate disclosed at launch. Machines with free transfer do not incur bandwidth charges. Inbound and private-network transfer are free. The full monthly allowance is shown at launch and accrues proportionally to runtime over 28 days, capped each UTC calendar month. Allowances are per instance, not shared between instances. Live transfer charges use sampled provider metrics and are provisional; missing readings are flagged, not guessed. Additional allowance automatically credits earlier overage charges. Provider reports can correct final usage after deletion.

Billing shows the bandwidth breakdown by instance and month. Paid-bandwidth machines start with a $0.50 reserve. It adjusts using recent outbound traffic, up to $2 per active machine, and is released when deletion is confirmed. It is not a charge or a limit on bandwidth costs. Late measurements can still result in charges and a negative balance. Delayed bandwidth readings are retried and do not by themselves terminate your instances. Normal balance limits still apply.

A ten-minute prepaid launch buffer is separate from any trusted negative-balance allowance. Running machines are scheduled for destruction before reaching the hard balance limit, leaving a reserve for deletion time. Provider delays and outages can still cause additional usage; deletion is not instantaneous.

Download a receipt

Completed deposits have a PDF download in the history table, including the payment reference, date, amount, and payment-method summary. These are credit-deposit receipts, not tax invoices. Refunds and disputes create balance adjustments instead of changing historical ledger entries.

Trusted account allowances

Eligible accounts with at least $500 in compute spend, 30 days of account and paid history, no chargebacks, and no failed payments in the last 30 days may have up to $30 in negative balance. The limits rise to $200 at $2,500 and 60 days, and $500 at $10,000 and 90 days.

These are maximum debt limits, not prepaid credits. They never replace the cash buffer required to start a machine. Risk changes can remove an allowance and trigger account-wide termination.

Automatic deposits and reminders

Save a card through Stripe in Settings, then explicitly authorize automatic deposits. Set the balance threshold, deposit amount, and daily limit. Failed payments or authentication requirements pause automatic deposits; add credits manually before instances reach their safety limit.

Email preferences cover deposits, low balance, automatic-deposit issues, instance changes, and security changes. The low-balance reminder threshold is configurable. Turning off email does not turn off safety actions.

Open Settings