The outcome
- The operator carries no fiduciary exposure for subscriber accounts.
- Subscribers get institutional-grade automation with retail-friendly setup.
- The pattern generalizes — any signal-based service could adopt this architecture.
The challenge
Every subscriber wanted to mirror trades automatically, but a single bot acting on behalf of hundreds of accounts is both a legal and an operational nightmare. Subscribers also operate at very different capital levels, so a fixed-size mirror is useless — and deduplicating fill notifications across many accounts is anything but trivial. The service distributes real-time entries through Discord.
How we did it
- Architected a subscriber-hosted bot pattern: each paying subscriber gets a one-click DigitalOcean deployment of their own bot, running under their own brokerage credentials.
- A central validation server publishes signed signals; subscriber bots subscribe and act locally.
- Proportional position sizing: each bot reads the signal's notional intent and scales to that account's configured risk profile.
- Fill-notification dedup: each order is tagged with a deterministic ID derived from the signal plus the account, then reconciled across the WebSocket feed.
- Subscription lifecycle wired through QuickBooks, Make.com, and Discord roles, so payment status drives bot access in real time.