Finance and accounting decision

TradeCopier.cloud

A single-master→single-receiver trade copier is realistic for a capable developer to build and run (core prior-art exists for MT4/MT5), but reproducing the full multi-platform, low-latency, polished commercial service with billing and broad platform coverage is larger than a one-person short-term project.

Visit website
You pay

$8/mo

$96/yr

Per seat. Read off the official pricing page.

You’d pay instead

$100one-off120 h to build

$35/mo6 h/mo upkeep

On cash alone, building overtakes the subscription at 6 seats.

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • Listen for trade events from a master account, transform/map order parameters (symbol, lot, SL/TP), enqueue and dispatch matching execution requests to receiver platform APIs, persist logs and show real-time status in a dashboard.

What it still won’t have

  • Out-of-the-box support for many receiver platforms (MatchTrader, TradeLocker, DXtrade) — initial scope is one receiver
  • Polish, monitoring, SLA and 24/7 support of the commercial service
  • Scale-tested low-latency guarantees (the site advertises ~50 ms sync)
  • Billing, account management, multi-master/multi-receiver UI features

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 6 seats.

Paid seatsseats

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a minimal cloud trade copier that accepts a MetaTrader5 master and copies trades to one cTrader receiver. Use Node.js (TypeScript), Postgres, BullMQ (Redis) for background jobs, Docker, and GitHub Actions for CI. Core features in scope: MT5 trade listener (socket/bridge) ingest, symbol/lot mapping and simple filters, idempotent execution sender to cTrader API, persistent trade/log storage, a basic web dashboard showing live events and history, authentication, retry/error handling, and tests for ingest->dispatch flow. Out of scope: MT4/MatchTrader/TradeLocker/DXtrade integrations, multi-receiver routing UI, billing/subscriptions, SLA/ops. Provide Docker Compose deployment, monitoring health endpoints, structured logs, and automated tests for the worker and API.
How we checked2 sources · 2/3 runs agreed · evidence score 56

How the score was reached

  • Partly verdict base52
  • 2 cited sources+1
  • Price verified on pricing page+3
  • Evidence score56

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 2

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ Price read off the page! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded