Future Roadmap — Overview¶
4pass is designed with a clear scaling path from the current baseline to 100K+ users. We share this roadmap in the open so you can see where we are headed — your feedback and use cases directly shape our priorities (in-app backtest, native strategy execution, one-webhook multi-account, and more). This page is organized by dimension so you can follow infra, architecture, or product features independently.
Roadmap philosophy
Optimize for the current tier, plan for the next, and ensure nothing blocks the tier after that. No big-bang rewrites — every scaling change is incremental (a Terraform variable, a config change, or a single new module). Over-engineering for 100K when you have 100 users wastes money and adds complexity. Under-engineering means a rewrite when growth comes. The architecture was designed so that both extremes are avoided.
| Dimension | Scope | Examples |
|---|---|---|
| Infrastructure | Cloud resources, cost, resilience | Graviton, RI, Aurora Serverless, Valkey cluster, cross-region DR |
| System Architecture | Data layer, application backend, scaling patterns | TimescaleDB, SQS for background tasks, Redis sorted sets, rate limiting |
| System Features & Product | User-facing capabilities, markets, UX | PineScript backtest, native execution, one-webhook multi-account, US/crypto expansion, DLL & MT4/MT5 broker bridges (planned), backtest dashboard |
| DevOps & Quality | CI, testing, deployment | Automated testing pipeline, ECS rolling updates |
Estimated timelines and user thresholds that trigger each change are noted in the respective pages.
Timeline Summary¶
Priorities subject to change based on user growth and market demand. Updated: 2026-02.