Run & terminal
Runtime hours
How runtime hours are counted, what each plan includes, what happens when they run out, and how to top up.
1 min readUpdated 26 Oct 2026
A runtime hour is an hour that a runtime (Run or a terminal) is running in a workspace. They're counted while it runs, every 30 seconds, and shown in Billing and the dashboard.
| Plan | Included each month |
|---|---|
| Free | 5 hours |
| Pro | 40 hours |
| Team | 20 hours per seat, shared by the whole team |
The month starts on the day your plan renews (the 1st of the month on Free).
When they run out
- You're warned when a workspace is running low, and again when it's out.
- Free: runtimes stop when the hours run out.
- Pro and Team: you get 5 minutes' grace, then runtimes stop.
Editing, saving, collaboration and Git never use runtime hours and keep working.
More hours
Buy an add-on — 20 or 100 hours, one time, never expiring. Add-on hours are used after the month's included hours.
Still have a question about this?
Assist answers from this article — in any language.
Was this helpful?
More in Run & terminal
Run your projectHow Run works in your own browser, which browsers support it, the Preview, dependency caching and run settings.The live preview — devices, inspector and moreSee your running app beside the code, at any device size, with its console, network, storage, Web Vitals, an accessibility check and an element picker that jumps to the code.Terminal, Python and sharing a terminalOpen terminals instantly, use 76 extra commands and Python, search your command history, and share a terminal with teammates.Webhook links and the request logGive your running app a public URL for test webhooks from GitHub, Cashfree, Stripe and others — then see every request, its headers and body, and replay it.