Frequently asked questions
Fit, plans, proof, billing, and the explicit trust boundary between research and execution.
Who This Is For: users deciding whether the research workflow fits before they spend more time or upgrade.
Fit and workflow
Use Alphrex when the hard part is deciding whether a strategy deserves trust, not when the only job is chart inspection or broker routing.
What is Alphrex?
A systematic trading research platform with backtests, comparison, bounded research, signals, and forward paper tracking.
Who is Alphrex for?
Self-directed traders and retail quants who want a more disciplined workflow than charting-only tools.
Who is Alphrex not for?
Not traders who mainly need broker routing, no-code bots, a live market cockpit, or a blank-slate quant engineering platform.
Where should I start?
Start in the Strategy Library or a concrete use case, pressure-test the idea in Backtest and Compare, then promote only the survivors into Paper.
Why not just use a charting platform?
Charting platforms are better when the chart is the main object. Alphrex is for when validation, benchmark context, and forward evidence need to stay in one workflow.
Plans and coverage
The paid boundary is about deeper operating room and broader support, not about locking away the basic research loop.
What changes with Pro?
Free keeps the core research loop usable. Pro adds extended best-effort ticker coverage, weighted benchmark baskets, public sharing, and deeper interpretation layers.
How broad is ticker coverage?
Free stays intentionally narrow around the core liquid universe. Pro expands into extended best-effort coverage, but it is not marketed as blanket long-tail support.
Can I use weighted benchmark baskets?
Yes. Alphrex supports benchmark inputs such as SPY:0.60,IEF:0.40 so benchmark design does not collapse into a single blunt proxy.
Can I share results publicly?
Yes, but the public-sharing layer is saved-result sharing, not raw-code community distribution. Public result sharing belongs to Pro.
When is Pro actually worth it?
Upgrade when benchmark baskets, broader coverage, public result links, or deeper diagnostics save recurring decision time rather than satisfying one-off curiosity.
What happens if I cancel Pro?
Your workspace is not deleted. Alphrex drops the account back to Free once Stripe marks the subscription canceled or expired, so core research surfaces remain available while Pro-only sharing, coverage, and diagnostics stop.
Proof and public artifacts
The acquisition layer should show research artifacts and forward evidence, not separate marketing claims.
What should a shared result actually prove?
At minimum: why the run looked interesting, what validation says, what benchmark-relative context says, and what the next action should be.
What should move from backtest to paper?
Only candidates that still look coherent after costs, validation pressure, and benchmark-relative interpretation. Paper should be a survivors-only layer.
Do scoreboards rank backtests or forward records?
Scoreboards rank stored forward paper histories, not saved backtests. They exist to compare ongoing evidence after the historical study phase.
What counts as public sharing?
Public sharing means saved-result artifacts with visible research context. It does not mean public raw-code distribution or a community strategy marketplace.
Billing and account
Billing is meant to be self-serve. The operational contract is explicit so users do not have to guess how cancellation or invoices work.
How do I cancel a subscription?
Use Manage Billing from Pricing or Settings. Alphrex opens Stripe's billing portal, where cancellation, invoices, renewal, and payment-method changes are handled. When Stripe sends the updated subscription state back, the account is synchronized automatically.
Do I need to contact support to stop renewal?
No. Cancellation is designed as a self-serve billing-portal action rather than a manual support workflow.
Where do invoices and card updates live?
Inside the same Stripe billing portal used for cancellation. Alphrex keeps plan state in the workspace, but card changes, invoices, and subscription-management actions live in Stripe.
Trust boundaries
The product is explicit about what it can help you study and what it still refuses to claim.
Is Research Lab arbitrary code execution?
No. Research Lab is bounded task-level Python on cached market data.
Is paper tracking the same as a live track record?
No. Paper tracking is useful forward evidence, but it is still a product-layer simulation rather than broker-audited live execution history.
Does Alphrex place live trades?
No. Alphrex stops at research, diagnostics, and paper tracking. It does not route broker orders.
Why stop before broker execution?
Because the product promise is governed research and forward evidence. Live routing introduces execution, infrastructure, and operational claims that Alphrex is deliberately not making yet.
Need Concrete Proof?
If the FAQ resolved the objection but not the trust question, go straight to a product-backed proof page.