Antfly Cloud billing combines organization-level billing state with instance-level capacity and usage records.
Billing Model
Each Cloud instance has a tier, mode, and node configuration. Those fields define the requested shape and are used for committed-capacity billing.
| Field | Purpose |
|---|---|
tier | Customer-facing package baseline: starter, standard, or pro. |
mode | Deployment topology: single or replicated. |
node_config | CPU, memory, node counts, storage, and replication settings. |
Replicated mode has a higher commitment multiplier because it provisions separate metadata and data node groups for high availability.
Estimates
Use the estimate endpoint before creating or resizing an instance. Estimates are designed for dashboards, preflight checks, and automation that must understand spend-limit impact before a change is applied.
Commitments
Committed-capacity records explain billing changes for instance shape transitions. Common reasons include:
- creating an instance
- changing package tier
- enabling replicated mode
- scaling up CPU, memory, or storage
- refunding capacity after scale-down
Use the Cloud Billing reference for commitment records and history.
Usage Records
Cloud usage records capture metered resource and product usage. Resource billing is calculated from node configuration in normalized units:
| Metric | Stored unit |
|---|---|
cloud_cpu_core_hour | millicore-hours |
cloud_memory_gib_hour | MiB-hours |
cloud_disk_gib_hour | MiB-hours |
The API converts stored units back into readable core-hour and GiB-hour values for summaries.
Spend Limits
Spend limits are organization-level guardrails. They help prevent accidental capacity changes or automation loops from creating unexpected spend. Configure limits before granting broad management API access to automation.