The outcome
- The subscriber-hosted structure is designed to limit the operator's potential fiduciary exposure: credentials and trade execution remain within each subscriber's account.
- Subscribers get an account-specific automation path with a guided setup.
- The pattern generalizes — any signal-based service could adopt this architecture.
The challenge
The service needed to support automated trade mirroring without one central bot acting directly across subscriber accounts. Subscribers also operate at different capital levels, so a fixed-size mirror is unsuitable — and fill notifications still need reliable deduplication across accounts. The service distributes 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.