Billing & credits

Suji uses prepaid credits. Top up an organization and its billable resources draw from that balance. VM sizes are usage-based; they are not monthly subscription plans.

​

What consumes credit

• Compute: billed by the minute at the VM size’s hourly rate, with a one-hour minimum over each VM’s lifetime. Charges continue while the VM remains allocated, including while stopped or suspended.
• App installation: no separate Suji installation fee. Apps share the VM’s resources; external services and licences can have their own fees.
• Managed daily backups: optional, adding a 20% surcharge to the VM compute charge while enabled. They belong to the VM and are deleted with it.
• Snapshots: ready snapshots have a daily storage charge at one thirtieth of the monthly per-GiB rate.
• Volumes: billed by size and elapsed time whether attached or detached.
• Outbound traffic: usage above the included allowance is billed separately. Inbound traffic is not charged.

See VM pricing for current rates, units and traffic rounding. The monthly VM figures assume 730 hours and are estimates, not maximum bills. Stopping a VM does not stop compute charges. Delete a VM to stop its compute meter. Snapshots and volumes can remain after VM deletion and continue to incur their own charges.

​

Add credit

Organization owners and admins can use Settings → Payment methods → Add credits. Choose an amount, complete Stripe Checkout and check the balance after payment processing. See Top up & checkout. Eligible new customers can receive €5 of welcome credit after verifying their email, adding a payment method and topping up at least €10 net of refunds. The offer is once per customer and subject to eligibility checks. It is usage credit, not withdrawable cash. Paid credit has no scheduled expiry. Promotional credit can have expiry and eligibility conditions; referral credit is spent before paid credit and cannot be refunded for cash.

​

Auto-recharge and caps

Auto-recharge uses a saved default card to add the chosen amount when the balance falls below its threshold. Its optional monthly cap limits automatic top-up payments during a UTC calendar month. It does not include manual top-ups or stop already allocated resources from accruing charges. Usage spending caps are separate settings. Review the scope of the cap you configure; a payment limit is not a resource shutdown plan. If recharge fails or is blocked, review the payment error and add credit promptly. VMs can be suspended and remain billable. At zero credit, VMs can be terminated; recovery depends on a successfully created and still-available backup. There is no guaranteed grace window. Read When your credit runs low for retention deadlines and recovery steps.

​

Balances and records

Balances belong to organizations, not individual projects. Switching organizations changes the balance and payment settings you see. Resource creation also depends on your role, resource limits and spending controls. Use billing usage records to review charges and Payment methods to review top-ups and available invoice links. Configure the organization’s Billing details before payment. Invoice availability and tax treatment are shown on the issued payment documents.

​

Next