At what volume does self-hosting video generation start saving money?

Open weights are free to download, but running them is not. GPUs, power, and day-to-day operations all land on the bill, while API paths grow linearly with every output second.

What determines the cost of one second of video?

This estimate looks at four things: resolution, workload, hardware profile, and the operational work needed to keep a deployment running.

Method & assumptions

How the estimate works — the assumptions behind every number on this page.

• Workload is measured in seconds of output video: clip duration × clips per month. API prices are published per output second by resolution tier.
• Self-host throughput is an estimate: public samples report roughly 13–74 seconds to generate a 5-second 768p clip on 4× H100 80GB (BF16, SGLang). We use the conservative end-to-end figure and assume generation time scales approximately linearly with output duration at fixed resolution and step count. Treat all throughput-derived numbers as directional estimates.
• Local purchase cost = one-time hardware (× system multiplier) depreciated over the chosen period + electricity (GPU-hours × power × PUE × rate) + operations labor. Cloud rental bills only the GPU-hours actually spent generating.
• Hosted API cost = monthly output seconds × the per-second price of the selected resolution tier. Reference input materials (images, reference video) may be billed separately by the provider.
• Break-even months ≈ one-time local investment ÷ (cheapest API monthly cost − local monthly operating cost), shown only when the difference is positive. Directional only.
• License restrictions are displayed as facts (territory, revenue threshold, open checkpoint scope) and are not legal advice. They do not block the estimate.

• •This is a planning estimate, not a vendor quote.
• •Generation quality, prompt adherence, and aesthetics are outside the price estimate — the post-training gap of fal H3 Max cannot be measured in price alone.
• •Content moderation, safety, and compliance costs are not included.
• •Video storage, delivery bandwidth, and asset management may add to the monthly bill.
• •Compute burned on failed generations and retries is not modeled separately.
• •Throughput is based on sparse public samples; real speed varies with steps, framework, and load.

How to estimate the cost of self-hosted video generation

Set your workload, pick a hardware profile and assumptions, and get a shareable number you can take to a budget discussion.

1. 01

   Set the workload

   Enter clip length, clips per month, and target resolution to fix your monthly output seconds.

2. 02

   Pick hardware and assumptions

   Choose owned or rented GPU profiles, then adjust electricity, labor, and other cost assumptions for your region.

3. 03

   Compare the four paths

   See monthly and per-output-second costs for local purchase, cloud rental, the official API, and fal H3 Max — then share the URL with your team.

Should you self-host video models?

The calculator shows you the self-hosting side of the bill first; the final call also depends on your volume, budget, region, and whether the team can run the infrastructure.

Both approaches can be right. The calculator places the self-hosting estimate next to the published prices of the official MiniMax API and fal H3 Max, and shows break-even months against the cheapest API path.

Supported video models

Open-weight video generation models you can self-host, with their license terms and open checkpoint scope.

Data sources

Every price and throughput figure on this page traces back to a public source.