Billing And Balance

All billing objects in your namespace are view-only — they're written by the platform's billing engine, not by you. This page tells you what each one means and how to read it.

Your balance — CloudekaTenant

kubectl get tenant -n <your-namespace>

Shows Balance alongside your Billing/Charging type. This is the authoritative number:

• Prepaid: balance is credit you've topped up; usage draws it down. It can go negative — there's no automatic cutoff mid-hour, but the 48-hour look-ahead check (see Quota & Limits) prevents you from starting new resources once your runway is too short.

• Postpaid: balance accumulates as debt owed — it goes up as you use resources, and is the amount you'll be invoiced for.

Live per-resource cost

While a resource is running, its billing mirror shows the current hourly charge:

kubectl get container -n <your-namespace>   # Pods:  CPU, RAM, Charge, Status
kubectl get storage -n <your-namespace>      # PVCs:  StorageClassName, Size, Charge, Status
kubectl get cfip -n <your-namespace>         # Floating IPs: IP, Charge

These update automatically as workloads start, change state, or stop — you don't need to do anything to keep them current.

Daily statement — CloudekaCharge

kubectl get charge -n <your-namespace>

One object per calendar day, named after the date (e.g. 2026-07-24). It accumulates throughout the day as the platform bills each finished hour, showing:

• A line-item breakdown per product (cpu, ram, per-GPU-model, per-storage-class, floating IP, NVAIE).

• previousBalance / balance — your balance immediately before/after this charge.

• charge — the running total for the day so far.

kubectl get charge 2026-07-24 -n <your-namespace> -o yaml

The platform charges are computed hour by hour and only fold into this object as each hour closes — so a CloudekaCharge for "today" is incomplete until the day ends. Don't expect it to reflect the last few minutes of activity.

Top-ups — CloudekaTopup

kubectl get topup -n <your-namespace>

A history of prepaid credit applied to your balance, applied by the platform team (finance/ops), not created by you directly. Each object is an immutable ledger entry — one credit event, previousBalance → balance. To add credit, go through your normal Cloudeka billing/payment channel; it will show up here once applied.

Prices — CloudekaPrice

kubectl get price -n <your-namespace> -o yaml

Your negotiated unit price (hourly) and monthly price per product. This is what the platform multiplies your usage by to compute every charge you see above. View-only; contact the platform team for pricing changes.

Quick answers

Question	Command
What's my balance right now?	kubectl get tenant -n <ns>
Am I prepaid or postpaid?	kubectl get tenant -n <ns> (Billing/Charging columns)
What is this specific Pod costing me?	kubectl get container -n <ns>
What did I spend today?	kubectl get charge $(date +%F) -n <ns> -o yaml
When was my balance last topped up?	kubectl get topup -n <ns> (sorted by CreatedAt)
What are my unit prices?	kubectl get price -n <ns> -o yaml