Gen3 Admin Financial Controls - GT-Edge-AI/GT-AI-OS GitHub Wiki
Financial Controls
Start Here
- Open Financial Controls.
- Review Infra Credits posture separately from Base fees and variable usage pricing.
- Update model pricing tables when Models catalog changes.
- Lock or document explanatory notes before saving billing changes.
Why this matters
Financial controls affect chargeback and budgets—separate base fees from variable usage to avoid silent policy drift.
Details
Financial Controls is the active Gen 3 billing-policy workspace. It combines billing enablement, Infra Credits pool posture, Base fees, budget enforcement, model pricing, storage pricing, and allocation management on one Control Panel route.
What the current page supports
The live page includes:
- billing status review
- billing enable/disable control
- Infra Credits balance, warning/critical/hard-stop thresholds, and enforcement toggles
- Base fees amount, interval, start date, lock posture, and backfill behavior
- budget and enforcement policy
- model-pricing configuration
- storage-pricing configuration
- allocation creation and review
Terminology
| UI label | Meaning |
|---|---|
| Infra Credits | Deployment-wide infrastructure credit pool consumed by inference, storage, memory embeddings, and related meters |
| Base fees | Recurring base infrastructure fee (shown as Base fee on individual ledger rows) charged against the Infra Credits balance |
Major sections
Billing status
Use this section to confirm whether billing is enabled and whether the deployment has the license posture needed for billing-aware workflows.
Budget settings
Use budget settings to define warning, critical, or hard-stop posture and the general enforcement model for the deployment's Infra Credits balance. Tenant Observability billing views use the same remaining-credit language.
Model pricing
This section controls the prices attached to configured models. Keep it aligned with the actual provider catalog so observability and budget posture remain meaningful.
Deep-dive runbooks:
- Model Pricing workspace — statuses, online reset, CSV import/export, capability and compound rows
- Provider rate cards — vendor list-price URLs and mapping into input/output per 1M tokens or unit pricing
Storage pricing
Use storage-pricing controls when the deployment tracks retained content cost as part of billing posture.
See Storage pricing for dataset/document GiB-month meters and Tenant billing analytics for owner-facing Billing verification.
Allocations
Use allocations to divide or label spending posture in a more structured way than a single shared pool.
Recommended operator workflow
- Confirm billing is enabled only when the deployment is ready for it.
- Review the budget policy.
- Update model prices after any material provider-catalog change.
- Review storage-pricing assumptions.
- Create or adjust allocations only after the baseline policy is sound.
What this page does not do
- It does not activate the enterprise license. Use License.
- It does not manage the underlying inference provider connectivity. Use Models.
Best practices
- Change pricing soon after provider or model changes so analytics stay trustworthy.
- Treat enforcement posture as an operational policy decision, not just a UI toggle.
- Review Tenant billing analytics after major policy updates to confirm the outcome is understandable to tenant owners.