Features
Everything Meridian does
Grouped by what problem each group solves. The reconciliation section is first because it is the reason this copier exists; the rest is what a copier has to get right to be worth paying for at all.
Reconciliation
The part no signal relay does
A copier's job is not done when the order is submitted. Meridian reads each account's actual position back and compares it to the leader's — repeatedly, on your schedule — so divergence is a number in a journal rather than a surprise at the open.
Position read-back
Per account and per instrument, sign and size are compared to what the leader's position implies. Manual trades on a follower show up as drift rather than being silently overwritten later.
Corrections that respect risk
Risk-reducing corrections are never blocked by a daily trade cap, and a flip from long to short is done in two stages — close, then open — so a reversal cannot gap through zero.
Slicing when size is wrong
When a correction is larger than the account can take cleanly, it is worked in slices instead of one aggressive order, and the journal says so each time.
Tonight's counters
Leader outages, corrections held, corrections sliced, flatten passes and accounts skipped — a per-night tally you can read at the end of a session without scrolling a log.
On demand
Run a pass immediately instead of waiting for the next tick, and get the verdict back: what diverged, what was held, what was corrected.
Zombie-leader detection
A leader marked connected whose unrealized P&L has not moved for a suspicious stretch is almost certainly a dead link. Meridian says so once, in the journal, and then keeps doing its job — it never guesses.
Outages
When the leader goes away, that is a decision
The dangerous outage is not the one you notice. Meridian makes the response an explicit setting, and makes it settable per follower.
Hold
Leave followers exactly as they are and wait. The right answer when the leader is expected back shortly.
Flatten
Close the followers. The right answer when the position is the risk rather than the opportunity.
Pause & report
Stop routing, change nothing, and write the reason to the journal so the next person to look knows exactly why nothing happened.
Global default, per-row override
Set the policy once for every follower, then give a single row something different — one account that must flatten, while the rest hold. The dashboard always shows the resolved policy for a row, so you are never guessing whether an override is in force.
Settle before correcting
After a leader reconnects, Meridian waits out a settle window before the first correction. A link that has just come back often drops again, and correcting into that churn is worse than waiting.
Sizing & routing
One leader, many accounts, different rules each
Per-row leader selection
Any follower follows any configured leader, and can be switched without touching the others.
Multipliers & fractional
Scale every copied order by a per-row factor, including fractional contracts when the account supports them.
Max leader size
Refuse to copy a position larger than a threshold — a guard against a single outsized leader fill.
Max family exposure
Cap correlated exposure across a family of instruments rather than per symbol.
Contract mapping
Map a leader's instrument to a different contract on a follower, including multiplier differences.
Shadow mode
Journal what would have been copied, without sending it. A safe way to test a new leader.
Pause reconciliation per row
Exclude an account from corrections while you manage it by hand, without pausing the others.
Slippage & margin awareness
Per-row slippage tolerance, and a follower that cannot cover the trade is reported rather than forced.
Multi-account connections
Connect and disconnect NT connection profiles from the dashboard, one click, with confirmation.
Risk
The stop that is not a stop order
Most of these are conditions Meridian evaluates itself, not orders it places — which means they still work when the market is moving faster than your broker.
Per-account loss cap
Pause routing for a follower that breaches its daily loss limit. Risk-reducing actions are never blocked by it.
Trailing drawdown
A high-water mark per account that pauses new exposure as it is given back.
Trade windows
Only copy inside your session hours, with an optional auto-flatten at the close.
Panic
One confirmed action flattens every account and stops routing. It works even while the engine is mid-pass, and it is journalled.
Journal
Show your work, always
Every webhook, route, fill, correction, guard trip and system event is written with enough detail to reconstruct what happened — filterable by account, instrument and kind, and streamed live.
Isolation
One account, one PC, one secret
Three mechanisms, none of which rely on you trusting anyone: a per-account webhook address with a server-minted secret, a device key per account that rotates on every sign-in, and routing that only ever reaches the copier linked to the caller.
Per-account endpoint
Your secret lives in your URL, is shown only on your Profile page, and cannot be edited by anything — including the admin.
Rotating device key
Signing in on a new PC invalidates the old one. Two machines can never drive the same account.
Account-scoped routing
A request is only ever routed to the copier linked to the account that made it. A wrong secret and an unknown account are refused identically, so URLs cannot be probed.
Integrations
Whatever sends a webhook
Meridian speaks plain HTTP with JSON, which means the sender is not a dependency. TradingView is the common case, not a requirement.
TradingView alerts
Paste the endpoint, add the listener secret, and route by strategy tag. Templates in the docs.
Any webhook sender
Custom scripts, bots, scanners — anything that can POST JSON. The payload contract is documented.
Discord notifications
Route fills and corrections to a channel, with per-event filtering.
Signal Console
Build and send a payload from the dashboard, exactly as TradingView would, to verify a wiring before it matters.
Heartbeat & health check
A periodic probe of your public URL, so a dead tunnel is detected before the next signal needs it.
Link over WSS or a tunnel
The PC connects out over a secure websocket, or through your own tunnel. No inbound ports to open.