Docs / Teams and account
Cloud credits
In development: cloud GPUs paid with prepaid credits, and how reservations, per-second charges and refunds of unused time will work.
Your own workers are always free. When you need more capacity, cloud jobs run on GPUs and accelerators that EsaSim rents from cloud providers. You pay for them with prepaid credits: you buy credits first, and each cloud job draws from that balance.
In development. EsaSim Cloud is not open yet: this page describes how it will work. To be among the first to use it, request cloud access. Until then, every run uses your own workers, free on every plan.
Buy credits
- Open Cloud credits in the dashboard. Owners and billing admins can buy; everyone with access to jobs can see the balance.
- Pick a pack or enter an amount, then pay with a card on Stripe Checkout.
- Credits appear as soon as Stripe confirms the payment. A receipt is added to Billing.
Credits belong to the workspace: your personal workspace, or an organization, on any plan. Organization admins can limit each member's GPUs per job, concurrent jobs and monthly GPU-hours.
What a cloud job costs
Each cloud class has a price per instance-hour, shown on the rates table. The price includes the EsaSim platform fee. A job is charged per second for the time it ran, with a minimum of one minute and a short start-up time per instance, multiplied by the number of instances it used.
| Example | Value |
|---|---|
| Class | 1 GPU per instance at $3.00 per hour |
| Job | 4 replicas, maximum runtime 60 minutes |
| Reserved at launch | 4 × (60 + 3 start-up minutes) × $3.00 / 60 = $12.60 |
| Job finished after 40 minutes | 4 × 43 minutes = $8.60 charged, $4.00 returned |
The numbers above illustrate the method; the rates table shows the real prices.
Reservations
When you launch, EsaSim reserves the cost of the job's maximum runtime from your balance. If the balance does not cover it, the job is not queued and nothing is charged: lower the maximum runtime or the replicas, or buy credits. While the job runs, the reserved amount is shown separately from your available balance. When it ends, is canceled or reaches its maximum runtime, the actual time is charged and the rest is returned at once.
A job never costs more than its reservation. It is stopped when it reaches its maximum runtime, so save checkpoints for long training runs.
Credit history
Every purchase, reservation, charge and adjustment is recorded on the Cloud credits page with the balance after it. Entries are never edited; corrections appear as new entries.
Expiry and refunds
Credits are in US dollars and are valid for the period shown on the Cloud credits page. If a payment is refunded or disputed, the unspent part of those credits is removed. Refund rules are in the terms of service.