Runtime monetization infrastructure

Valqio decides before billable work runs.

Call Valqio before an AI generation, API call, export, seat change, or paid job. It resolves plans, credits, quotas, and customer terms, then manages the usage lifecycle with evidence.

Node SDKStripe targetFree sandboxEvidence export
Valqio runtime decision flow showing request inputs, policy checks, an allow decision, evidence, usage state, and billing export

Preflight

Allow or deny before the costly action starts.

Reserve + retry

Hold credits and make repeated requests idempotent.

Commit or release

Close the lifecycle after success or failed work.

Evidence

Keep the reason, state, and export trail together.

Runtime path

Ask Valqio before monetized actions run.

Before generation, exports, paid jobs, invites, or billable usage, Valqio resolves customer context and returns the allow or deny answer your app can enforce.

Request preview

POST /api/generate

Inline

Subject

org:acme

Meter

api_requests

Quantity

1

Product asks

Can org.acme run api_requests?

Valqio returns

ALLOW - evidence ev_9K2

1

Your app asks first

Can this customer run the API call, generate a response, export a report, invite a user, or spend credits right now?

2

Valqio resolves state

The runtime reads the plan, entitlement, meter, credit balance, contract override, usage window, and request idempotency.

3

Work runs or stops

The SDK returns allow or deny with remaining balance, reason code, reservation context, and an evidence ID.

4

The lifecycle closes

Commit successful work, release failed work, replay safe retries, and export the evidence when billing or support needs it.

Why Valqio

Billing records revenue. Valqio tells your app what to allow.

Billing systems collect payment and invoice usage. Metering systems count. Feature flags toggle paths. Product code still needs to handle plan gates, credit checks, contract exceptions, retries, and failed work. Valqio moves that enforcement into one runtime decision path.

Billing systems

Invoice usage, collect payment, and store commercial records.

Metering systems

Count and aggregate usage after product events happen.

Feature flags

Toggle access paths, usually without credit holds or usage settlement.

Valqio runtime

Decides before billable work starts, then manages reserve, commit, release, and evidence.

Versioned pricing inputs

Version the plan, contract, usage, and billing inputs behind every decision.

Plans change. Contracts override plans. Credits expire. Usage windows reset. Valqio versions the inputs that affect a decision so every answer can be explained later.

Runtime model

published v42
Inputorg:workspace_acmeSubject-bound request
MeterapiRequests1 unit, idempotent
RuntimeenforceAllow, deny, reserve
Evidencetrace + usageSupport and finance evidence

Decision inputs

Plan, contract, usage, credits, and billing context resolve before the answer.

Current for request

Action

api_requests

Runtime action

The product work Valqio decides before it starts: API request, AI generation, export, seat, storage write, or custom action.

Declaredfeeds decision

Plan

v2.1.3

Plan version

A published package of action rules, credits, limits, meters, and billing cadence that feeds runtime decisions.

Versionedfeeds decision

Override

Enterprise

Contract override

Customer-specific terms without forking the product code path.

Versionedfeeds decision

Hold

hold_42

Reservation

A hold for costly or prepaid work that can be committed after success or released after failure.

Reservedfeeds decision

Retry

req_9K2

Idempotency key

Retry context that prevents a duplicate request from double-spending credits or usage.

Dedupedfeeds decision

Evidence

ev_9K2

Evidence record

Decision evidence for the inputs, output, reason, and export context.

Recordedfeeds decision
Input snapshot
Runtime policy
Decision + evidence

Developer experience

One runtime decision path before and after work runs.

Ask before paid work starts. Valqio can allow, block, reserve, commit, or release usage, then give your app the evidence behind the decision.

See pricing
app/routes/generate.tsNode.js
import { createValqioClientFromEnv } from "@valqio/sdk-node"

const valqio = createValqioClientFromEnv()
const decision = await valqio
  .forSubject({ type: "org", key: workspaceId })
  .withRequest({ requestId })
  .meters.enforce("apiRequests", {
    quantity: 1,
    idempotencyKey: requestId,
  })

if (!decision.allowed) {
  return blockWithUpgrade(decision.reasonCode)
}

await runGeneration()

return decision
response.json200 OK
{
  "allowed": true,
  "reasonCode": "plan_allowance_available",
  "remaining": 12424,
  "evidenceId": "ev_8qK2z",
  "usage": {
    "limits": [{
      "meterKey": "api_requests",
      "hardCap": 15000
    }]
  },
  "source": "sandbox"
}

allowed

true

remaining

12,424

hardCap

15,000

evidenceId

ev_9K2z

Product moments

Use Valqio when pricing changes customer access.

AI usage and credits

Paid actions

Decide whether a customer can generate, transcribe, analyze, export, or start another paid job.

Budgets

Check model access, token budgets, and prepaid balances before work begins.

Feature and plan gates

Plan access

Allow features by plan, contract, customer segment, or environment.

Seat gates

Resolve named-seat access before invite, login, or activation paths.

Stateful limits

Allowances

Enforce monthly allowances, daily caps, fair-use rules, and credit balances.

Storage gauges

Read current usage and cap expansion before accepting more stateful usage.

Decision evidence

Exports

Export usage and decision evidence to Stripe, support, finance, or your warehouse.

Debugging

Give operators the reason, input snapshot, and evidence ID behind each outcome.

Integrations

Start with Stripe. Keep product enforcement out of billing.

Begin with Stripe-connected usage and evidence, then export decision context to support, finance, and data systems.

Your product

Product actions
Customers
Usage context
Backend services

Valqio Runtime

+Evaluate
+Reserve
+Commit or release
+Record evidence

Destinations

SStripeLive billing target
LRuntime ledgerDecision evidence
DData warehouseWarehouse export
?Support toolsSupport export
$Finance & analyticsFinance export

Pricing

Start free, then pay when Valqio gates real customer usage.

Plans scale by runtime decisions, usage events, projects, exports, and log retention. Start in the playground, then create a sandbox for your first runtime path.

Sandbox

Explore pricing behavior in the playground, then create a free sandbox when your first runtime path is ready.

Free

Includes

  • 100k runtime decisions
  • 25k usage events
  • 1 project
  • 2 environments
  • 7-day logs

Builder

For a first production integration with test billing, exports, webhooks, and audit logs.

$99

/mo

Includes

  • 1M runtime decisions
  • 250k usage events
  • Production access
  • Test billing
  • Exports and webhooks

Scale

For teams scaling runtime decisions across more projects, exports, and log retention.

$1,499

/mo

Includes

  • 100M runtime decisions
  • 20M usage events
  • Policy layers
  • Priority support
  • Reconciliation

Enterprise

For teams that need custom volumes, retention, projects, and implementation support.

From $4,000

/mo

Includes

  • Custom runtime decision volume
  • Custom usage-event volume
  • Custom projects
  • Custom log retention

What counts as a runtime decision?

A runtime decision is the answer your app requests before monetized work runs, with reservation and evidence context when the action needs a lifecycle.

Does Valqio replace Stripe?

No. Stripe remains the payment and invoice system of record; Valqio decides what the product should allow and records the evidence.

Can I run it in sandbox first?

Yes. Start in the playground or a free sandbox, then move the same request and evidence shape toward production.

Which integrations are live?

Stripe is live. Warehouses, support tools, and finance systems are export targets, while additional billing adapters are planned.

When to add Valqio

Add Valqio when pricing starts changing what customers can do.

Pricing checks keep spreading

Plan access, custom contracts, customer segments, and environments keep leaking into product routes and jobs.

Retries can spend twice

Balances, allowances, reservations, and failed work need one lifecycle instead of caller-specific patches.

Support needs the reason

Show why an action was allowed or denied without reconstructing plan, usage, and billing state by hand.

See a runtime decision before billable work runs.

Open the playground to watch Valqio decide, reserve credits, and keep the usage lifecycle and evidence trail together. No signup required.

Free sandboxSample scenariosDecision evidence