Platform product
ClonePips Copy
Branded copy trading with a strategy marketplace. A white-label copy trading venue for brokers, with provider onboarding, strategy review and an investor marketplace on one platform.
- Broker-branded domain, theme and copy
- Provider approval and strategy review workflow
- Investor allocation and portfolio dashboards
- Rule-based risk controls per broker, provider and account
Demo data — fictional sample content for interface development. Not real ClonePips customer data.
Availability
Available in this build
What the product registry says about this product today, stated without extension.
- Listed available in the product registry for this build.
- Delivers 4 platform modules, so its scope is defined by them.
- Declares integrations with mt4, mt5, white label, webhooks — no venue is connected here.
Registry facts
- Category: platform
- Status: Available in this build
- Intended for: brokers, traders, investors
- Delivers modules: 4
- Pricing basis: per active investor
Why it exists
A copy venue is an operating business, not a copier
A broker launching copy trading inherits onboarding, disclosure, risk and pricing work that a replication engine alone does not solve.
Copy trading at venue scale is rarely blocked by the engine that replicates a signal. It is blocked by everything around it: reviewing providers before they are visible, disclosing how a track record was produced, and holding one risk posture across every follower account.
ClonePips Copy packages those concerns as one tenant-scoped venue. Provider onboarding, strategy review, an investor marketplace and rule-based risk all read from the same domain model, so a change in one surface stays consistent in the others.
- Broker-owned domain, theme and copy.
- Provider approval and strategy review before discovery.
- Risk rules evaluated per venue, provider and account.
Product view
The venue console, illustrated
A broker-facing view of a copy venue: providers, strategies, subscriptions and execution connectivity, composed from demo data.
Broker venue console
Demo dataVenue — Demo Broker
- Providers
- 4
- Strategies live
- 6
- Subscriptions
- 5
- Venue
- 1
Services
- Copy engineActive
- Strategy reviewActive
- Risk engineActive
- Analytics snapshotsActive
Execution connectivity
- MetaTrader 4 bridgeIn development
- MetaTrader 5 bridgeIn development
- FIX / dealing integrationIn development
- External liquidity providerIn development
- ClonePips internal venueIn development
Performance figures shown on this site are illustrative demo data. Past performance is not indicative of future results.
Demo data — fictional sample content for interface development. Not real ClonePips customer data.
- The console shows a venue with an active signal turned into per-account copy instructions.
- Allocation, fee and risk figures in the frame are fictional demo data.
- No venue is behind it: the frame is a layout illustration, not a system check.
- Illustrative product composition built from demo data. Not a live account or venue.
Design
How ClonePips Copy is designed to work
One tenant, three surfaces
Broker console, provider studio and investor marketplace are projections of the same tenant-scoped records.
Review before discovery
Strategies pass a broker-controlled approval workflow before the marketplace exposes them to investors.
Rules per broker
Exposure, drawdown and eligibility rules are configured per venue and evaluated in the shared risk engine.
Workflow
ClonePips Copy end to end
How the pieces connect. The diagram names the stages; the labels live in configuration, like every other page.
A diagram of a copied trade: a provider's master account, signal capture, normalisation, risk checks, routing and the follower accounts that receive the replicated order.
- A signal is captured from the master account and normalised into per-follower instructions.
- Risk checks run before routing, so a subscription limit is a gate, not a report.
- The replicated order reaches follower accounts through the venue's execution adapters.
Audience
Who operates it
One tenant, three surfaces. The same records are projected for the broker, the provider and the investor.
- Brokers own the domain, theme, fee plan and approval workflow.
- Providers publish strategies into a broker-controlled review queue.
- Investors discover approved strategies and allocate within eligibility rules.
Built for the operator
- White-label deployment on the broker's own domain.
- Per-broker risk profiles and eligibility rules.
- Fee plans configured per venue, not per deployment.
Deployment
Deployment notes
- 01
Step 1
Deploys as a white-label venue on a broker's own domain and theme.
- 02
Step 2
Provider onboarding, strategy review and investor allocation share one tenant configuration.
- 03
Step 3
Risk profiles, fee plans and eligibility rules are configured per broker.
Questions
About ClonePips Copy
What does available mean for ClonePips Copy?
The product suite lists it as available. Scope and hosting terms are confirmed during a demo, and this site states no customer, volume or regulatory facts beyond what the repository evidences.
How much of the venue is branded?
Domain, theme, copy and surface selection are tenant configuration, which is what makes it a white-label venue rather than a shared portal.
Notices
Risk warning
Trading foreign exchange, CFDs and leveraged instruments on margin carries a high level of risk and may not be suitable for all investors.
No advice
Information on this site is provided for general information only and does not constitute investment advice or a recommendation.
Demo data
Demo data — fictional sample content for interface development. Not real ClonePips customer data.
Next
See it in a demo
Bring the venue, the execution setup and the fee model you run; the demo covers the platform and the commercial basis.