Make your first DaneTrades copy in a few deliberate steps

This is the fastest clean path to a verified first copy with the current product. It uses the updated DaneTrades flow: web app first, local runtime connected, accounts added in Trading Accounts, copier created in Copiers, then verification in Logs.

Start free trial Open safety checklist

Uses current app labels and routes
Works for local PC or Windows VPS deployment
Ends with a real verification step, not just setup

Before you start

You will need:

An active DaneTrades account or trial.
A Windows PC or Windows VPS where the local runtime will stay online.
One source or master account, plus one receiver account.
Supported platforms on both sides. Check Supported Platforms first if you are unsure.

Step-by-step quickstart

Download and sign in to the local runtime. Open Download Agent, install the Windows app, and sign in so your workspace can reach that machine.
Add your source account in Trading Accounts. Go to Trading Accounts, click Add Account, choose the source platform, and complete the connection flow. If your source is a signal feed such as Telegram or TradingView, add that source here first.
Add your receiver account. In the same Trading Accounts area, add the account that should execute the copied trade. For most setups, receivers should be broker or platform execution accounts.
Create the copier connection. Open Copiers, click Create Connection, select the source and receiver, then start with simple sizing such as a 1.0 lot multiplier or another conservative test size.
Save, enable, and test with a tiny trade. Make sure the connection is enabled. Then place a very small demo trade on the source side and immediately open Logs.

What successful verification looks like

Your first test is not complete until you confirm all of the following:

The trade appears in the receiver account with the expected direction and size.
Logs show a successful copied event rather than a rejection or warning.
Symbols match as expected, especially if broker naming differs.
The runtime remains online after the trade, not just during setup.

If your first trade did not copy

The most common causes are usually one of these:

The local runtime is not connected or has gone offline.
The source or receiver account is disconnected.
The copier connection was saved but not enabled.
Symbol mapping is missing because the two sides use different symbol names.
The receiver broker rejected the order due to invalid volume, margin, or market state.

Recommended next step: check Copy Health, read Logs, and then move to the first-week safety checklist before increasing size.