sandbox · example data only · not your workspace
← all scenarios

Pricing & Usage Demo

See plan limits · AI usage · token consumption · overage alerts.

How operators stay inside their plan + when to upgrade.

Steps
5
Est. time
~4 min
Audience
client
Reviewed
2026-05-23

read first

FAQ— Quick answers about safety, data, and pricing.
Execution Plans

data flow

scenario architecture


   UsageEvent rows ──aggregate──▶ quota gauge
                                        │
                              70/90/100% alert thresholds
                                        │
                                ▼              ▼
                          email alert    in-app banner
step 1/5·No approval needed

Plan tier

Current tier + entitlements.

visionxixlabs.com/dashboard/billing
AAxiom
Sign out

step 1 · preview

Plan tier

Current tier + entitlements.

Plans before applies

Every recommendation generates a Terraform diff + a separate rollback plan. The apply button stays disabled until the rollback plan validates against a digital twin of your cloud.

safety invariants in play

  • ✓Rollback verified — Every recommendation ships with a pre-validated rollback plan before the apply button is enabled.

expected result

Tier card + month-to-date usage.

platform route

/dashboard/billing →

read more

Execution Plans

engineering principle

Quota is enforced at the API boundary with a fail-open guarantee on the billing-DB path. The 70/90/100% alert thresholds run on the same UsageEvent rows you see in the gauge — no separate cron, no separate aggregation.

Platform reference →Architecture overview →← Back to all scenariosSet up your real workspace →