Jio preview access is issued by an operator. There is no public price sheet or self-service billing flow today. Your account's enforceable quotas are the source of truth.
Check account limits
jio usageThe command reports:
| Field | Meaning |
|---|---|
| CPU | vCPU quota and current reservations |
| Memory | Memory quota and current reservations |
| Disk | Retained-disk quota and current reservations |
| Compute sessions | Sessions currently reserving CPU and memory |
| Retained sessions | Sessions currently reserving disk |
| Session lifetime | Operator-defined expiry, when configured |
All API keys on one account share these limits. Stopping a retained VM releases compute but can continue to reserve disk. Destroying it releases retained resources after cleanup completes.
VM sizes
| Size | vCPU | RAM |
|---|---|---|
| Small | 1 | 2 GiB |
| Medium (default) | 2 | 4 GiB |
| Large | 4 | 8 GiB |
The endpoint advertises available sizes. If the requested size is unavailable or would exceed quota, creation fails; Jio does not silently downgrade it.
Client limits
| Boundary | Limit |
|---|---|
jio exec default timeout | 120 seconds |
jio exec maximum timeout | 1 hour |
| SDK command input | 16 MiB |
| SDK file transfer | 16 MiB per file |
Legacy jio run instances | 1–64 |
Service-side capacity and account policy can impose lower limits. Use
jio usage before dispatching parallel work and handle quota failures without
blind retries.
Billing questions
Contact your Jio operator for pricing, quota changes, and expiry policy. Include
your account ID from jio usage; never send an API key.