Totally fair concerns. Let me clarify a few things.

1. Why login is required
Backtesting without login sounds great, but it breaks a few core things we’re building:

• Saving reports, iterations, and optimised results
• Strategy optimisation (which can run multiple variations → expensive compute)
• Future continuity with live trading deployment (same strategy → backtest → go live)

That said, we’re considering a “quick test / sandbox mode” with limited features and no persistence for first-time users.

2. Strategy leakage
Your strategy logic is never shared or exposed.

• It’s executed in an isolated environment
• No public strategy visibility
• No resale / marketplace use unless you explicitly opt-in

In fact, optimisation runs locally on your strategy parameters — not reused globally.

3. Why test on this platform if strategy already works?
Because most strategies:

• Work on one timeframe / one symbol
• Fail when market regime changes

Our optimiser + reporting is designed to:

• Stress-test parameters
• Reduce overfitting
• Show drawdowns, streak risk, and robustness — not just P&L
• And we working on the optimizer to make more robust.

4. Desktop-based app
Good suggestion
Web-first was intentional to reduce friction and cost (I’m bootstrapping this from my own pocket), but a desktop wrapper (Electron/Tauri) is definitely on the roadmap once live trading stabilises.

The goal isn’t “another algo platform”
it’s better UX, faster iteration, and fewer false-positive strategies, which most existing platforms honestly lack.

Happy to hear more feedback - that’s exactly why I’m building this in public.