Always On – Lacking an Automatic Suspension Threshold

Always On – Lacking an Automatic Suspension Threshold

Goal: Determine whether Replit can automatically suspend an "Always On" repl when traffic falls below a certain threshold to reduce costs for low‑traffic workloads.

Constraint: Current documentation only allows manual enable/disable; no CPU or request‑based criteria for auto‑suspension.

Uncertainty: Does Replit support an external API or webhook to trigger suspension, or is there a planned feature to add automatic thresholds?

Questions:

• Is there an API endpoint or configuration flag that can automatically toggle "Always On" based on traffic metrics?
• Could a scheduled job or external monitoring service be used to suspend the repl when idle, and what are the rate limits or side effects?
• What is the minimum traffic threshold that Replit recommends for keeping a repl "Always On" to balance cost and latency?