Usage & Billing
The Usage tab in Organization Management lets you monitor resource consumption and understand billing.
Summary Cards
At the top of the Usage tab, four cards show totals for the selected period:
| Card | Description |
|---|---|
| Total CPU Hours | Cumulative CPU time consumed |
| Total Memory (GB-Hours) | Cumulative memory usage |
| Credits Used | Total credits consumed (for billing) |
| Total Runs | Number of lab runs executed |
Usage Charts
Three interactive charts visualize usage over time:
- CPU Hours: Bar chart showing CPU consumption per period
- Memory (GB-Hours): Bar chart showing memory consumption per period
- Credits: Bar chart showing credits consumed per period
Hover over any bar to see the exact value for that period.
Filters
Customize the view with these controls:
Granularity
Choose how data is aggregated:
| Option | Best for |
|---|---|
| Hourly | Detailed analysis of recent activity |
| Daily | Standard monitoring (default) |
| Weekly | Long-term trends |
Period
Select the time range:
| Option | Duration |
|---|---|
| Last Week | 7 days |
| Last Month | 30 days (default) |
| Last 3 Months | 90 days |
| Custom | Pick specific start and end dates |
Billing Information
At the bottom of the Usage tab:
| Field | Description |
|---|---|
| Billing Mode | paygo (pay-as-you-go) or prepaid |
| Credits Balance | Available credits (for prepaid mode) |
Billing Modes
| Mode | Description |
|---|---|
| Pay-as-you-go | Usage is tracked and billed based on consumption |
| Prepaid | Organization has a credits balance that depletes with usage |
Understanding Resource Usage
How Usage is Calculated
Resources are metered while labs are running:
- CPU Hours = CPU allocated (cores) × duration (hours)
- Memory GB-Hours = Memory allocated (GB) × duration (hours)
- Credits = Weighted combination of CPU and memory usage
Typical Resource Consumption
| Scenario Type | CPU per Hour | Memory per Hour |
|---|---|---|
| Simple (2-3 components) | 1-2 CPU-hours | 2-4 GB-hours |
| Medium (4-6 components) | 2-4 CPU-hours | 4-8 GB-hours |
| Complex (7+ components) | 4-8 CPU-hours | 8-16 GB-hours |
Cost Optimization Tips
Reduce TTL
Shorter default TTL means labs expire sooner, reducing idle resource consumption.
Right-size Scenarios
Don't over-provision components. Use the minimum resources needed for the learning objective.
Monitor Active Runs
Check the Dashboard regularly. Stop idle or forgotten labs.
Review Usage Patterns
Use the Usage tab to identify:
- Peak usage times
- Heavy-consuming scenarios
- Users with unusually high usage
Next Steps
- Organization Settings - Configure default TTL
- User Management - Manage members