Console
Documentation menu

Guides

Billing

Prepaid credits, per-second GPU billing, what is and is not charged, and what happens at zero.

How billing works

  • Prepaid credits. You buy credit in US dollars, and usage draws it down.
  • Per second. GPU time is billed by the second while a GPU is attached to your replica.
  • Scale to zero. No traffic means no GPU and no GPU charge.
  • No commitments. No reservations and no minimums beyond the minimum top-up.

Add credit

In the console, open Billing and choose a pack or a custom amount.

OptionAmount
Packs$20, $50, $100, $250 or $500
CustomAny whole-dollar amount from $10 to $10,000

Payment is handled by Stripe Checkout. Credit is added to your balance when the payment completes. ClockingCloud never sees or stores your card number.

What is charged

ActivityCharged
GPU attached to a replica (running, provisioning, scaling)Per second at the GPU rate
clockingcloud runPer GPU second until the job ends
clockingcloud dev CPU sandboxPer second at the CPU sandbox rate
Stopped or scaled-to-zero instanceNo GPU charge
clockingcloud plan, clockingcloud ls, clockingcloud logs, API readsFree
ClockingCloud Global VolumesFor provisioned capacity while the volume exists
Your own S3, Azure or GCS bucketBilled by your cloud provider

Current rates for each GPU and for volumes are shown in the console and by clockingcloud plan and clockingcloud models ls --prices. Rates are quoted in US dollars.

When credit runs out

When your balance reaches zero, running instances are stopped and new requests fail with insufficient_credits (HTTP 402, CLI exit code 4). Definitions, volumes and trained adapters are kept. Add credit and run clockingcloud start <name>.

Watch your spend

Terminal
clockingcloud balance
clockingcloud usage --since 7d --by model
clockingcloud top

Use idle_timeout, a conservative scale.max, and clockingcloud plan before deploying to bound spend. Credits and refunds are governed by the Terms of Service.

Something unclear or missing? Email hello@clockingcloud.com.