Private beta
Backtester.app is in a limited beta. Accounts are activated manually so that processing capacity and data access stay under control while the engine is validated.
Request access
- Register with a valid email address.
- Open Telegram and message @backtester_admin.
- Include the email address you registered with and, if you like, the channel you want to test.
- Wait for confirmation. Accounts are reviewed by hand; there is no automated approval.
Until activation, the dashboard only shows a pending notice. You can sign in, sign out and manage your password.
Beta limits
Defaults for an activated beta account. Administrators can raise them for individual accounts, and full-access accounts get larger defaults.
| Limit | Default |
|---|---|
| Distinct channels per day | 1 |
| Historical months per day | 1 |
| Maximum range per run | 1 month |
| Queued or running jobs | 2 |
| Concurrent jobs | 1 |
| Daily reset | 00:00 UTC |
Quota is consumed when a job is accepted. Re-running a period you already covered that day does not consume extra quota. Failed jobs can be retried by an administrator without counting again.
Fair queueing
Backtests run on a small processing node. When it is busy, your job waits in a persistent queue and the dashboard shows its state and queue position. Jobs survive restarts: an interrupted job is retried automatically, and no request can start the same job twice. During peak load an administrator may enable slow mode, which lowers concurrency rather than dropping work.
Queued
Waiting for capacity. You see the position, but no completion time is promised — processing depends on the jobs ahead.
Processing
Running in an isolated workspace. You can cancel; the workspace and its temporary data are deleted.
Completed
The report is available for a limited time (24 hours by default), then deleted automatically.