Billing

Lyceum Cloud is credit-based. You top up your balance through Stripe and the platform deducts credits as you run jobs, host VMs, or serve models. Credits don’t expire and there’s no monthly minimum — what you put in is what you have to spend.

​

How charging works

Every billable action — a serverless run, a VM hour, an inference replica hour — generates an entry in your execution history with the credit cost attached. Charges are pulled against your balance in real time, so you can watch your spend during long jobs and abort if needed. The balance is split into two pots:

• Free credits — granted by Lyceum (signup bonus, vouchers, support credits). Spent first.
• Purchased credits — bought through Stripe Checkout. Spent after free credits are exhausted.

Both kinds of credit are interchangeable from a usage perspective; the split exists so the dashboard can show you what you’ve earned vs paid for.

​

Topping up

The POST /billing/checkout endpoint creates a Stripe Checkout session. Redirect the user to the returned URL; Stripe handles payment, and on success the credits are added to the balance via Stripe’s webhook.

​

Vouchers

Voucher codes can be redeemed for free credits — typically used for promotional credits, support credits, or migration grants. Validate a code before redeeming to surface a friendly error message.

​

REST API