Compute usage

Automated runs are metered by daily compute time — the server time your runs consume, per UTC day. This page explains how to read the usage meter, what counts against the budget, and how to review your recent usage in Settings. For the full plan limits, see Compute time & limits and Plans.

The daily meter

The meter sits at the bottom of the Sessions panel's Automated tab. It shows:

• Used / total — today's consumption against your daily allowance, e.g. 2m 34s / 10 min. The allowance is Free 10 minutes per day or Pro 24 hours per day.
• Reset countdown — the budget window is the UTC day, so the meter counts down to the next reset at 00:00 UTC ("resets in 3h 12m").
• Warning tint — the bar changes color as you approach the limit, and the label switches to Quota reached once the day's budget is used up.

The ⓘ icon next to the label opens a short explanation with your plan's numbers. The same meter also appears in Settings → Plan, inside the server-compute card.

What counts

• Automated backtests — strategy runs, from start to finish.
• Filters & Signals runs — script-based timeline tracks, computed when a track updates.
• Manual-session statistics — the equity & drawdown calculation for a manual session.
• Failed runs — the time spent computing before the failure counts.

What doesn't count:

• Queue time — a run waiting for a free slot consumes nothing.
• Script compiles — never count, on any plan.

Usage is wall-clock run time on the server, and it's counted when a run finishes — a run that's still computing shows up in the meter once it completes.

Usage history in Settings

Settings → Usage shows your server compute over the last 30 days — UTC days, so the "Today" bar always matches the meter:

• Three summary numbers — Total across the window, Busiest day (with its date), and Today.
• A daily bar chart — one bar per UTC day; hover a bar for the date and the exact time used. Days without any billed compute show as empty slots.
• A daily-limit line — a dashed reference line marking your plan's daily allowance.

Common questions

"Why did a failed run consume compute time?"

Because the server replayed data and ran your script up to the failure point — that's real compute. A retry is a fresh run, metered like any other.

"What happens when I hit the limit?"

New runs wait for the 00:00 UTC reset, or an upgrade. Nothing is lost — your scripts, sessions, and finished results are untouched, and runs already in progress finish normally.

"Does watching a run live cost extra?"

No. Compute time is what the run itself consumes on the server — attaching to it, watching it stream, or opening the finished report doesn't add anything.