Account Limits
Understand the architectural boundaries, resource quotas, and execution capabilities of Python Online.
The Capability Matrix
Python Online allocates system resources to ensure a fast, stable experience for all developers. We divide our infrastructure into two distinct operational states: Guest (Unauthenticated) and Registered.
| Feature | Guest | Registered Account |
|---|---|---|
| Max Projects | 1 (Local Only) | 3 |
| CPU Allocation | 0.25 vCPU | 0.25 vCPU |
| RAM Allocation | 256 MB | 256 MB |
| Execution Limit | 60 Seconds | 60 Seconds |
| Cloud Storage | - | 512 MB |
| Web Hosting | - | 1 App (Hibernates) |
| Scheduled Tasks | - | 1 Task (Daily) |
| Internet Access | - | Secure Proxy |
1. The Guest Sandbox (Unauthenticated)
Designed for absolute zero-friction entry, the Guest mode allows anyone to start writing and running Python code instantly without handing over an email address.
- Storage: Files are stored entirely in your browser's local memory, meaning they are inherently temporary. To secure your data to our cloud, please Sign In.
- Execution Limits: Guest scripts and REPL sessions are given a hard 60-second execution window. Code runs in a disposable, stateless container that is instantly destroyed upon completion or timeout.
- Restrictions: Guests do not have outbound internet access from their code, nor can they host web applications or schedule background tasks.
2. Registered Accounts
Creating a free account unlocks cloud persistence and essential deployment capabilities.
- Storage & Projects: 512 MB hard quota. You can maintain up to 3 separate projects.
- Execution Limits: The 60-second execution wall remains in effect. Every run starts with a clean slate (fresh RAM), ensuring no data leaks between script executions.
- Network Access: Outbound network requests (e.g., using `requests`) are routed through a strict security proxy that only allows traffic to our verified domains whitelist.
- Web Hosting: You are granted 1 Active Web Application. Hosting utilizes an "auto-hibernation" lifecycle. If your site receives no traffic, the server sleeps to save resources. The next visitor will see a brief wake-up screen before the app loads.
- Automation: You can schedule 1 Automated Task to run daily. The task is strictly headless and given a 60-second execution window.