Limits & Fair Use
LiteLambda is designed to be highly reliable. To protect the platform and ensure consistent performance for all users, we enforce certain technical limits on code execution.
Execution Limits
| Resource | Free Tier Limit | Description |
|---|---|---|
| Maximum Runtime (Timeout) | 30 seconds | If your script runs longer than this, it is forcefully terminated and marked as a TIMEOUT. |
| Memory (RAM) | 64 MB | Maximum memory allocation per execution. Exceeding this causes an Out-Of-Memory error. |
| Ephemeral Storage (/tmp) | 64 MB | Temporary disk space available during execution. Destroyed after the run. |
| CPU Share | 0.1 vCPU | Compute power allocated to the container. |
| Pip Package Size | 10 MB | Maximum compressed wheel size per imported pip package. |
Paid Tier Limits
Users on the Starter and Pro plans can configure higher limits per cron job, up to:
- Timeout: 300 seconds (5 minutes)
- Memory: 512 MB
- CPU: 1.0 vCPU
Note that increasing resource limits will consume credits at a proportionally faster rate.
Fair Use Policy
While we offer a generous permanent free tier, any account found to be using LiteLambda for malicious purposes—including but not limited to DDoS attacks, crypto-mining, spam email generation, or hosting phishing endpoints—will be permanently banned without warning.