---

title: “Limits” description: “Understanding WithGiga’s usage limits and how to manage them” icon: “gauge”

​

Limits

WithGiga implements safeguards to ensure platform stability and prevent accidental over-usage.

​

Types of Limits

​

⏱️ Session Duration

- Maximum Runtime: To prevent accidental infinite loops, deployments have a default maximum runtime (e.g., 4 hours). You can adjust this when launching a deployment. - Idle Timeout: Computers that receive no interaction or commands for a set period may be automatically suspended.

​

💻 Concurrent Deployments

- Active Computers: Your plan determines how many AI computers you can have running simultaneously. - Total Deployments: Limits on the total number of stopped/archived deployments you can keep.

​

💾 Storage & Resources

- Disk Space: Each computer has a maximum disk allocation. - CPU/RAM: The maximum tier (e.g., 4 vCPU, 16GB RAM) available to you depends on your subscription plan.

​

⚡ API Rate Limiting

- Request Limits: Standard rate limits apply to API calls to prevent abuse.

​

Managing Your Limits

​

Monitor Usage

Check the Dashboard to see your current concurrent usage and active sessions.

​

Upgrade Options

Higher tiers unlock: - More concurrent agents (run parallel tasks). - Longer session durations (for complex, multi-hour workflows). - Larger, more powerful computer instances.

​

Best Practices

- Always set a timeout on your deployments. - Terminate sessions programmatically when the task is done. - Reuse deployments if possible, rather than spinning up new ones for every micro-task (though starting fresh ensures a clean state).