Documentation
Plans & Limits
Astral applies daily usage limits, capacity limits, and feature gates. Your in-app account response is the source of truth because trials, grandfathered plans, staff access, promotions, and rollout grants can change what is available to a specific account.
Pro is the public paid planStandard plan summary
The public offering is Astral at $30/month, with an eligible new-customer introductory first month at $9. Astral Basic is the free account tier. Astral Plus is a legacy tier for grandfathered subscribers and is not presented as the standard public purchase option.
For the latest marketing comparison and offer terms, use Pricing. The app’s subscription settings show your actual tier, status, and effective access.
Common standard limits
| Capability | Basic | Legacy Plus | Pro |
|---|---|---|---|
| AI prompts | 10 daily | 45 daily | Unlimited |
| Backtests | 10 daily | 45 daily | Unlimited |
| Saved strategies | 3 | 25 | Unlimited |
| Historical bars | Up to 5,000 | Up to 20,000 | Up to 40,000 |
| Price and condition alerts | 2 | 20 | Unlimited |
| Broker connections | None | 1 | Unlimited |
| Broker trading | Not included | Manual | Automated eligible deployments |
| Paper deployments | 1 | Up to 5 | Unlimited paper trading |
| Broker-connected deployments | Not included | Not included as standard | Up to 10 |
| SMS notifications | Not included | Included | Included |
Some comparison copy groups alert and paper deployments for legacy Plus. The feature-access panel in Settings is authoritative when a legacy account’s exact allowance differs.
How limits behave
Daily usage
Capacity
Entitlements
Temporary access
When you reach a limit
Astral can show a limit or upgrade dialog. For capacity limits, removing an unused saved item, alert, watchlist, connection, or deployment may free a slot. For daily limits, wait for the reset shown by the product or change plans. Do not delete consequential data simply to free capacity without first confirming what will be lost.
Downgrades
A downgrade can schedule changes to features whose current usage exceeds the new allowance. Broker-connected strategies can be undeployed when the required entitlement is lost. Undeployment does not automatically close broker positions; check the broker directly and manage any remaining positions yourself.
Reading a feature gate
A gate should explain the capability, current allowance or entitlement, and available next action. Before upgrading, identify whether the restriction is caused by the plan, daily usage, current capacity, a missing verification step, asset or broker support, or a rollout that no plan can unlock yet.
| Gate type | Typical response |
|---|---|
| Daily usage exhausted | Wait for the displayed reset or review a plan with a larger allowance. |
| Capacity reached | Archive or remove an unused eligible record after confirming dependencies. |
| Entitlement unavailable | Review the plan comparison and account-specific upgrade offer. |
| Verification required | Complete the relevant email, phone, broker, or account verification. |
| Unsupported workflow | Choose a supported asset, broker, mode, or interval; upgrading may not change support. |
| Temporary grant ended | Review the effective tier and any pending demotion actions in Settings. |
Effective tier and grants
The effective tier is the access level the application currently enforces after considering the subscription and valid grants. A trial or promotion can temporarily raise access without changing the underlying long-term subscription. A scheduled downgrade can leave a period in which access and future state differ.
Do not build a live workflow around temporary access without knowing the end condition. Before a grant expires, review connected deployments, saved capacity, alerts, and broker access.
Capacity cleanup
Removing a saved strategy can affect your ability to inspect or revise a deployment even if the deployment record remains. Removing a broker connection affects account data and connected operations. Deleting an alert permanently removes that monitoring rule. Capacity cleanup should be deliberate, not a blind response to an upgrade modal.
Where possible, stop dependent activity first, record anything needed for audit, then remove the unused item and confirm the capacity counter refreshes.
Plan changes and active workflows
After upgrading, refresh Settings or the gated action if access does not appear immediately. After downgrading or cancellation, inspect pending actions and every active broker-connected strategy. A product access change cannot guarantee liquidation or cancellation at the broker.
Legacy Plus accounts should use their live feature-access panel rather than assuming every historical Plus comparison applies unchanged.