Company
Infrastructure for copy trading, sold to the people who operate it
The infrastructure behind modern copy trading. Launch branded copy trading, strategy marketplaces, multi-account management and institutional-grade trading infrastructure.
- Built for brokers, providers and investors on one platform
- Capability statements instead of performance promises
- Disclosure treated as part of the product, not a compliance afterthought
Product
What ClonePips is
Three surfaces over one platform: a broker venue, a provider console and an investor application.
Broker venue
A branded copy trading venue with tenant configuration, provider review, fee plans and venue-wide risk control.
Read the broker briefProvider console
Master account control, strategy publishing under review, copy settings and attribution.
Read the provider briefInvestor application
Marketplace discovery, standardised disclosure, allocation and monitoring.
Read the investor briefThe platform under them
Nine layers from audience applications to execution adapters, with the dependencies written down.
See the capability mapHow we work
Three commitments that shape the product
These are engineering constraints rather than slogans: each one is visible in the architecture and in the interface.
- State capability, never outcome. The product describes what a module does, not what it returns
- Disclosure is part of the read model. Period, currency and account scope travel with every figure
- Authority is explicit. The broker configures the venue, the platform evaluates the rules
What that means in practice
- Surfaces still in development are labelled as such, never described as available
- Demo data is labelled everywhere it appears
- Risk and no-advice notices sit on the pages that need them
Status
What exists today
This repository is a preview: the design system, the global product shell and the page framework, running entirely on fictional data with no services connected.
- Implemented: design system, navigation shell, page framework, marketing pages
- Implemented: domain contracts, product and audience registries, architecture model
- In development: data layer, accounts, services, execution adapters, integrations
Why preview the shell first
- Information architecture can be reviewed before services exist
- Compliance copy is settled while it is cheap to change
- Every subsequent build inherits one navigation and page vocabulary
Contact
Request a demo
Request a demo
A demo request starts a conversation about your venue: client segment, execution setup, fee model and the products you want enabled.
- A walkthrough of the platform with fictional data on screen
- The architecture and the roadmap, including what is still in development
- Commercial basis for your deployment, agreed in writing
This preview has no contact form and no backend to receive one. Every request action on the site leads here, and a direct contact channel is added as the platform opens.
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.