Multi-instance setup
Run several bridge instances side-by-side for different strategies, accounts, or environments.
Why multi-instance
Running one instance per account is the cleanest operational model. You get isolation, per-instance risk ceilings, and per-instance logs without cross-contamination.
Naming conventions
Name each connection after the human context it represents — for example, desk-eu-fx, personal-ibkr, or prop-binance-perp. The connection name appears in every log line and analytics split.
Routing by account
Set the account field in your alert payload to target a specific instance. Omit it and the signal fans out to all matching connections according to your global routing rules.
Plan limits
Starter supports 1 instance. Pro supports 25. Scale removes the cap and adds priority queueing during burst traffic.
Related guides
Want to contribute?
Spot an inaccuracy or missing detail? Send us a note from the contact page — real humans read every message.