How It Works
Every time you run a workflow or AI app on BizyAir, the task goes through three stages. Only the “Running” stage hits your bill — the other stages are free.This means no matter how long the queue gets, how large the model is, or how thick the image is, only the part that is “actually running on the GPU / CPU” is billed.
Billing for AI Applications & ComfyUI Workflows
Upon submission, tasks enter a shared queue. The system automatically allocates instances based on the workflow’s nodes and models used, meaning a single task’s execution time may span multiple instance types. Billable usage includes both GPU and CPU. All instances are billed per second. For concurrent tasks, charges accrue based on the cumulative execution time of each individual task, rather than the overall concurrent duration.GPU Billing Rates
CPU Billing Rates
Special Note
If a ComfyUI workflow uses Model API nodes (provided by the BizyAirCloudPlugin extension for ComfyUI), the execution time of these nodes will not be included in the CPU time billing. Billing for such nodes follows the Model API rules (see Node Pricing).Mixed Workflow Billing
When a workflow combines BizyAir infrastructure nodes with Model API (third-party API / LLM / VLM) nodes, multiple fees accrue in parallel:Failure Rules
What’s Never Billed
The following items will never appear on your bill:- ✅ Queuing time — time a task spends waiting in the queue for GPU scheduling
- ✅ Environment setup time — downloading model weights, pulling container images, initializing setup
- ✅ Network transfer time — uploading input files and downloading output results
- ✅ 5xx server errors — any HTTP 500+ error is never billed
- ✅ Platform-caused interruptions — forced interruptions due to platform maintenance or failure
For long videos or multi-step sampling tasks, try a small-resolution dry run first before scaling up the output, to avoid wasting compute.