SteadyEdge plan limits are not cosmetic. They directly affect which backtest periods you can run, how many runs you can create per UTC day, whether backtests are forced public, and what pricing you see in billing.

What this is

This article explains the plan catalog, the limits that matter in the product, and how those limits show up in everyday workflows.

When to use it

Use this article if:

you are choosing between Free, Basic, and Pro
a backtest option is disabled
you hit a daily backtest limit
you want to understand the current pricing logic

Before you start

Important current rules:

daily backtest limits are counted per UTC day
Free users are limited to shorter backtest periods
Free backtests are forced public
paid plans can use longer periods and choose visibility
the yearly checkout amount is currently calculated as 10 monthly prices charged at once

Step by step

Step 1: Understand the current plan catalog

The available plans are:

Step 2: Free plan

Price: $0
Performance fee: 10%
Daily backtest limit: 10
Bot limit: 1
Allowed backtest periods: 1 month, 3 months
Backtest visibility: public only

Step 3: Basic plan

Price: $19 monthly
Current yearly checkout price: $190
Performance fee: 8%
Daily backtest limit: 25
Bot limit: 10
Allowed backtest periods: 1 month, 3 months, 6 months, 12 months
Backtest visibility: public or private

Step 4: Pro plan

Price: $49 monthly
Current yearly checkout price: $490
Performance fee: 5%
Daily backtest limit: no numeric cap
Bot limit: no numeric cap
Allowed backtest periods: 1 month, 3 months, 6 months, 12 months
Backtest visibility: public or private

Step 5: Know where limits appear in the product

In day-to-day use, plan limits show up mainly through behavior:

a longer backtest period is disabled or rejected
a run is blocked because you reached the daily cap
Free forces public backtests
billing pages show the current plan, period, renewal state, and expiry

Step 6: Separate plan limits from launch gates

Some important blockers are not plan upgrades by themselves. A bot still will not start if:

your email is not verified
the bot has not passed a backtest
your available balance is 0 or below

What you should see

After reading this article, you should understand:

which periods your plan can run
when the daily limit resets
what the current monthly and yearly amounts are
why a disabled period or blocked run may be a plan issue rather than a technical failure

Common mistakes

treating local midnight as the daily reset time when usage is counted by UTC day
upgrading only for private visibility and forgetting that period access also changes
confusing plan limits with email verification or missing backtests
expecting yearly billing to equal 12 monthly charges in the current checkout logic