01
Faster model
We run few-step, speed-tuned builds, so eight RTX PRO 6000 GPUs render about 4,000 ten-second 768p clips with audio per day. More video per GPU-hour lowers the cost per attempt.
Blog · October 8, 2026
Teams compare video models by price per second. In production, the number that matters is cost per accepted clip: what you pay, including retries and rejects, for each clip that passes review. A dedicated, customized H3 deployment lowers both sides of that ratio.
The metric
Cost per accepted clip = total production cost ÷ clips that pass review.
Total cost includes every generated attempt, retries, review time and idle capacity. If only half of your clips pass review, your real cost per clip is double the list price. A lower price per second does not help if the acceptance rate falls.
List prices
| Model and tier | List price | 10-second clip |
|---|---|---|
| MiniMax-H3, 768P | $0.08 / s | $0.80 |
| MiniMax-H3, 2K | $0.13 / s | $1.30 |
| Seedance 2.0, 720p | $0.15 / s | $1.50 |
| Seedance 2.5, 720p | $0.231 / s | $2.31 |
Sources: MiniMax pricing and BytePlus pricing, read October 19, 2026. These are list prices for different models and resolutions, so they do not compare quality.
Dedicated host cost
Illustrative case: eight RTX PRO 6000 GPUs at $3 per GPU-hour cost $576 per day. At full use they render about 4,000 ten-second 768p clips with audio per day. That is about $0.0144 per second of video.
This is GPU cost only. It excludes service fees, storage and network. The host runs only your jobs, so you own all of its concurrency.
Two different products
| Stateless API | Nuva Lab dedicated host | |
|---|---|---|
| Who runs on it | Shared capacity for all customers | Private: only your workloads |
| Concurrency | Rate limits and queues set by the provider | Full concurrency: every GPU serves your jobs |
| Model | The provider's model versions | Your LoRAs, post-trained weights and speed-tuned builds |
| State | Each request stands alone | Your references, assets and review history stay with the deployment |
| Improvement | Does not learn from your reviews | Data flywheel: your approvals and rejects guide the next tuning round |
| Pricing | Per second generated | Fixed daily cost; about $0.014 per second at full use |
An API sells generated seconds. A dedicated host gives you a production system that you own and that improves with your work. How the feedback loop works.
Calculator
Defaults: the MiniMax-H3 768P list price and the illustrative eight-GPU host. The host cost here is GPU cost only. Change any value.
Where Nuva Lab lowers the cost
01
We run few-step, speed-tuned builds, so eight RTX PRO 6000 GPUs render about 4,000 ten-second 768p clips with audio per day. More video per GPU-hour lowers the cost per attempt.
02
A model customized on your brand and references aims to get more clips through review on the first try. We measure this on your own briefs. How customization works.
03
Agents run batches, retries and checks, so your team reviews results instead of operating tools. Agents and the feedback loop.
04
The host runs only your jobs. You own its full concurrency, so large batches do not wait in a shared queue.
FAQ
The MiniMax list price is $0.08 per second at 768P and $0.13 per second at 2K, read October 19, 2026. A 10-second 768P clip costs $0.80 per attempt.
The BytePlus list price for Seedance 2.0 at 720p is $0.15 per second, read October 19, 2026. A 10-second clip costs $1.50 per attempt.
At production volume, yes. At full use, the GPU cost is about $0.014 per second of 768p video. The MiniMax H3 API list price is $0.08 per second. The host is a fixed daily cost, so enter your own volume in the calculator.
The API is a stateless, shared service that charges per generated second. A dedicated host is private, gives you full concurrency, runs your customized weights and improves with your review data.
It is the total production cost divided by the clips that pass review. It includes retries, rejected clips, review time and idle capacity, so it shows the real cost of usable output.
Price per second ignores acceptance rate. If a cheaper model needs twice as many attempts to get a usable clip, it costs more per accepted clip.
Sources and further reading
Tell us your volume and review process. We'll size a dedicated deployment and compare it with your current API cost.
Get started · 1 min