Configuration modes
The monitor operates in two modes:🛑 Auto-Stop mode
Automatically stops (not terminates) Pods when utilization falls below defined thresholds for a specified duration.- Saves: GPU/CPU compute costs
- Preserves: Pod /workspace storage
📊 Monitor-only mode
Tracks and alerts on idle Pods without taking action.- Purpose: Surface idle Pods for manual review
- Benefit: Visibility into resource utilization patterns
Quick deployment for team level monitoring
Deploy the team monitor on Runpod: Deploy template Make sure to select CPU pod and not GPU pod, when deploying for the template to show up. For the cheapest option, run on a CPU Pod. The monitor automatically excludes itself from monitoring.Quick deployment for self-Pod monitoring
For individual Pod monitoring without external dependencies, use the self-contained CLI version that runs directly in your Pod.How it works
Define idle thresholds for your Pods (e.g., ≤1% GPU, CPU, or memory usage). The monitor samples utilization every minute:- Below threshold: Counter increments toward your defined duration limit
- Above threshold: Counter resets, monitoring continues
- Duration reached: Triggers auto-stop or alert based on your configuration
Team level monitoring feature preview
Home dashboard

Configuration management

Monitoring table

Performance metrics
