Case study · in-house product

echoSignals case study — cloud copy trading for MT4/MT5, from idea to priced product.

A multi-tenant copy-trading and signals platform for MetaTrader 4 and 5: cloud-hosted terminals that install themselves, signal delivery and routing, subscription billing, and a white-label option so resellers can launch their own service.

Type
SaaS · multi-tenant
Platforms
MT4 · MT5 (DXtrade, cTrader next)
Stack
C# / .NET · SignalR · SQL Server · React
Status
Live, priced, monitored 24/5
Problem
Traders wanted signals they could follow without installing or maintaining a terminal; providers wanted to sell without building a platform.
What we built
A cloud that runs the terminals, routes the trades and bills the subscriptions — and can be rebranded for resellers.
Hard parts
Zero-setup provisioning, lot scaling across account sizes, tenancy isolation, and keeping latency low from master to follower.
Outcome
A live product with public pricing and a white-label programme, used as the reference for client copy-trading builds.

Why we built it

Copy trading usually fails on the follower's side: a VPS to rent, a terminal to install, an EA to configure, and a support ticket every time something drifts. We wanted a service where the follower subscribes, connects an account, and everything else runs in our cloud.

Architecture

Each tenant — a signal provider or a white-label reseller — gets isolated products, masters and subscribers. Master accounts run on cloud terminals we provision automatically; trades are captured at the source, normalised, scaled per subscriber (fixed lot, multiplier or risk-based) and routed to follower terminals over SignalR. A .NET service layer owns accounts, entitlements, billing and the partner tree; a React dashboard sits on top for providers, subscribers and resellers.

What was hard

  • Zero-setup provisioning. A terminal that installs, logs in, attaches the copier and reports health without a human, and repairs itself when the broker server restarts.
  • Lot scaling. Followers with different balances, leverage and broker contract sizes need the same relative exposure — with symbol-suffix mapping and minimum-lot rounding that never turns a small account into an oversized one.
  • Tenancy. Resellers must never see each other's subscribers; providers must never see each other's masters. Scopes are enforced in the data layer, not the UI.
  • Latency. Master to follower in the same second, across brokers, with retries that do not double-fill.

What it became

A priced product — an entry membership and per-platform subscriptions — with strategies monitored 24/5 and a white-label programme for brokers, educators and signal providers. DXtrade and cTrader connectors are in development. It is also the reference implementation we bring to every client copy-trading build: the tenancy model, the scaling rules and the provisioning are already proven.

ECHOSIGNALS CLOUD · ONE TENANT SHOWN MASTER TERMINALSauto-provisioned · MT4/MT5 SERVICE LAYER.NET · SignalR · billing FOLLOWER TERMINALSscaled · routed · monitored DASHBOARDproviders · subscribers · resellers TENANCY & PARTNER TREEproducts · masters · subscriptions · commissionsisolated per reseller and provider in the data layer
C# / .NET 8SignalRSQL ServerReactMT4 / MT5Cloud virtualisationWhite-label

Want this for your own brand?

The tenancy model, scaling rules and provisioning are proven. A white-label build starts from there.

Talk to an engineer