Decide before expensive work starts.
Valqio checks plans, credits, quotas, limits, and customer terms before an HD render starts, then helps your product reserve, commit, release, replay, and inspect the outcome.
Acme is about to start an HD AI video render that requires 120 credits.
Should the product start this billable job?
- Customer
- Acme Pro
- Required credits
- 120
- Credits remaining
- 4,243
One click runs the pre-work decision, reserves the credits, and shows the worker result, settlement, and runtime fields.
Credit hold
credits4,243
available balance
120 credits will be reserved only if the render is allowed.
See the exact call your product would make before billing kicks in.
Three short reads before you press Run decision — what teams usually write, what Valqio takes over, and how the proof is delivered in this demo.
Homegrown path
Plan checks, credit tables, retry guards, release paths, and support notes spread across product code.
Valqio path
One runtime call decides first, reserves credits or checks capacity, then commits, releases, or replays after the action finishes.
Proof path
After the first run, the edge cases show retries, failed workers, concurrency caps, overrides, and overage without signup.
Billing runs after usage
Invoices, collections, and payment state still live in your billing provider.
Valqio runs before work
Your product asks Valqio whether usage should happen before the action starts.
Runtime fields tie it together
Correlation headers, reservation metadata, settlement ids, ledger ids, and optional usage event ids remain explainable.