Console feature map

A public map of the hosted Console areas developers use to configure, integrate, test, and inspect Valqio.

Console is the hosted control plane for Valqio. Use it to model product behavior, publish runtime state, create SDK access, test decisions, and inspect evidence after your app calls the data plane.

Runtime integration path

Console area	Customer purpose	Use it when
Start	See setup progress, readiness, and recent runtime activity.	You need the next integration action or a quick health check.
Developers	Create API keys, view SDK setup, inspect developer activity, and configure webhooks.	You are wiring the SDK, rotating keys, or checking integration traffic.
Publish	Preview and publish runtime state for an environment.	You changed product actions, meters, plans, limits, or customer policy and need the data plane to serve it.
Decisions	Open Workbench, History, and decision detail.	You need to test allow and deny paths or explain a specific runtime decision.
Runtime Activity	Inspect usage lifecycle records, reservations, commits, releases, retries, and diagnostics.	You need to trace what happened after a decision entered the usage transaction lifecycle.
Draft Invoices	Review billing-sync previews, export readiness, usage source context, and Stripe export evidence.	Finance or operations needs to understand how runtime usage becomes billing-provider input.

Modeling areas

Console area	What it models	Runtime effect
Product Actions	Saved app-native names for work your product wants Valqio to guard, meter, reserve, or record.	Generated SDK helpers and action-level decision evidence.
Usage Controls	Meters, quotas, credits, reservations, and protective limits.	Runtime enforce, reserve, commit, release, and limit checks.
Plans	Product packaging and usage allowances.	Rules that grant actions, credits, quotas, or limits to customers.
Customers	Customer or workspace subjects, plan assignments, balances, and usage history.	The subject state Valqio evaluates when your app calls the data plane.
Features	Feature access checks.	Non-consuming allow or deny decisions for product access.
Parameters	Runtime configuration values.	Non-consuming values your app can read before choosing product behavior.
Segments	Customer groupings and targeting inputs.	Plan, feature, or configuration targeting context.

Settings areas

Console area	What it controls
Projects	Product workspace for a Valqio integration.
Environments	Separate runtime states for staging, production, or other release tracks.
Members	Team access to Console.
Account billing	Commercial account state for Valqio itself.

What to do first

Start with one product action:

Model or select the action and backing usage control.
Attach it to a plan or customer policy.
Publish the environment.
Create a server runtime key.
Generate or configure the SDK.
Run Workbench for a preview.
Run one real app request.
Inspect Decisions → History and Runtime Activity.

If you cannot find evidence for the request, the integration is not proven yet.

Outputs to look for

Area	Output that proves progress
Developers	Runtime key, SDK setup values, and recent API activity.
Publish	Published environment state and product actions available to the SDK.
Workbench	Preview or consuming decision result with reason and diagnostics.
Decisions → History	Decision evidence with request ID, subject, action, outcome, and reason.
Runtime Activity	Reservation, commit, release, usage, retry, or diagnostic trace.
Draft Invoices	Reviewable usage lines, export readiness, Stripe connection, and export evidence.

Billing providers invoice, collect payment, manage taxes, and hold commercial records. Console shows the Valqio side of that flow: decisions before work runs, usage lifecycle evidence, draft invoice previews, and Stripe export readiness.