Copy execution with control, limits and visibility.
DAROS Copy replicates master execution across child accounts with allocation rules, per-account risk limits and full sync visibility — copy infrastructure built like an execution system, not a signal forwarder.
Standard copy tools fail exactly when it matters — a child account hits a margin shortfall, or a broker API disconnects mid-basket, and the divergence goes unnoticed. DAROS treats every child as an isolated, risk-managed pool: mapped, limited, monitored and logged.
What breaks without it
These are the failure patterns DAROS Copy is built to remove:
- Blind signal forwarding with no execution control
- No account-level control over what children trade
- Over-leveraged child accounts relative to capital
- No visibility into sync gaps and partial fills
- Operational chaos as trading communities scale
Built for
- Trading communities running member accounts
- Prop desks allocating one strategy across accounts
- Fintechs building copy or social-execution products
- Family/multi-account operators
Spec sheet & configuration
Where this module sits in the pipeline, what it handles, and what its configuration looks like. Figures marked as design targets are benchmarked per deployment.
| REPLICATION | Master–child fan-out through OEMS · per-child lot / capital multipliers |
| CHILD ISOLATION | Per-child RMS: loss limits · exposure caps · symbol rules |
| SYNC TELEMETRY | Fill parity · copy delay per child · divergence alerts |
| FAILURE HANDLING | Retry policies · flag-and-alert on persistent failure · nothing silently dropped |
| SCALE | Children across multiple brokers via the Connect abstraction |
Values are design targets and depend on deployment environment, broker APIs and data sources. Nothing here is a performance or return claim.
{
"master": "MASTER-01",
"children": [
{ "acct": "A-114", "mult": 0.5, "broker": "brk-1",
"rms": { "daily_loss": 8000, "max_exposure": 120000 } },
{ "acct": "B-021", "mult": 1.0, "broker": "brk-3",
"rms": { "daily_loss": 15000 } }
],
"on_partial_fail": ["retry:2", "flag", "alert:ops"]
}What DAROS Copy does
Master–child execution
Fills on the master account replicate to mapped children.
Account mapping
Explicit mapping of which children follow which masters and strategies.
Lot / capital multipliers
Scale child orders by fixed lots or capital-proportional rules.
Allocation rules
Control which strategies and instruments each child participates in.
Child-account risk limits
Per-child loss limits and exposure caps enforced by RMS.
Execution sync monitoring
See fill parity between master and every child in real time.
Partial failure handling
Rejected or partial child orders are retried or flagged, not lost.
Copy delay tracking
Measure replication latency per child and per broker.
Alerts
Sync breaks, limit breaches and broker errors notify operators immediately.
Full logs
A complete audit trail of every replicated order and its outcome.
How it runs in practice
Community copy setup
Map member accounts to a master → set per-child multipliers and loss limits → enable sync monitoring → members' accounts follow with enforced boundaries.
Partial-failure recovery
A child broker rejects an order → Copy retries per policy → if it still fails, the child is flagged, the operator alerted and the divergence logged.
Controlled scale-up
New child accounts are added with conservative multipliers → sync quality and limit usage are reviewed in Monitor → allocation is raised deliberately.
How it connects with other DAROS modules
No module runs alone. DAROS Copy plugs into the rest of the platform:
All modules:
Map your master–child setup with an engineer.
Share how many accounts, which brokers, and how allocation should scale. We will design the mapping, multipliers and per-child limits.