WFPricing / 03

Pay only while the world is alive.

A session is a held GPU, not a request. Credits move only while the runtime is ready and returning live frames.

Connectingfree
Queuedfree
Readymetered by second
Endedmeter stopped
01 · Live meter

One runtime.
One honest meter.

Choose a model, ready time, and concurrency. The estimate moves on the same unit as the API: session seconds.

Windflow runtime estimatorMeter online

Select runtime

Estimated burn

Helios

10,000 credits / USDReady state only

$0.102

1 × 1 min ready time · 60 session seconds.

Credits
1,020
USD / hour
$6.12
Free runs
49
1 min
01
01 session50 sessions
No generation-count abstractionIndicative private beta rate
02 · Access

Start free. Scale without changing the meter.

Every access mode uses the same ready-time billing model. Capacity changes; the unit does not.

Prototype01

Free credits

$5

on signup

Enough session time to connect a real prototype before adding a payment method.

  • 50,000 credits
  • All public models
  • 4 concurrent session
Request access
Production02

Pay as you go

$0.0017

per session-second, from

Buy credits and draw them down only while a session is ready. No subscription or seats.

  • Ready-time billing
  • Recoverable sessions
  • Concurrency on request
Sign in to buy credits
Design partner03

Reserved scale

Custom

reserved capacity

For teams shipping interactive video with dedicated capacity and private deployments.

  • Reserved GPUs
  • Private runtimes
  • Direct engineering access
Talk to us
Indicative private-beta rates · final GA pricing may shift ±15%Billing state · ready

03 · Billing FAQ

What changes a balance. What does not.

These answers mirror the current ready_session_second contract. Rates remain discoverable at the API instead of being hidden in plan fine print.

Q01

When does the meter actually run?

Billing starts when a session enters ready and stops when it is released or ends. Queued capacity, worker startup, and the documented reconnect grace are excluded. A ready session is billable even when nobody is watching its track.

Q02

Does pausing video stop the meter?

No. pauseTrack only stops delivery to that connection, and a generation pause can still leave the GPU reserved. Release the owner session when the experience is finished or idle.

Q03

Why can I get a 402 while credits remain?

Session creation reserves the model rate multiplied by its maximum session ceiling. Concurrent reservations reduce the spendable balance. When a session ends, actual ready seconds settle and the unused reservation returns.

Q04

Do additional viewers cost more?

No. One session is metered once regardless of how many authorized guests receive it. Separate concurrent sessions each carry their own meter and credit reservation.

Q05

Why do models have different rates?

Rates follow the GPU and runtime profile needed to keep each model interactive, not an output-count abstraction. 10,000 credits equal $1; current public rates are also exposed by GET /v1/pricing.

Q06

What happens to charges if a runtime fails?

Queue and startup never enter the ready meter. If a ready session fails, it ends and settles against the ready seconds already recorded; the unused reservation returns to the account balance.

Q07

Are uploads or recordings separate line items?

During private beta, the published public rate is the ready-session meter. Temporary recordings expire after 24 hours; high-volume exports, dedicated storage, or private delivery are scoped with Reserved scale.

Q08

Can I test a real session before paying?

Yes. Approved accounts receive 50,000 credits ($5) on signup, usable across public models. The estimator above shows how many runs fit inside that grant.