A copy trading community run by your asset management team
You do not need to hand clients to a broker or run your community inside someone else's platform. Your site operates under your domain and brand, clients bind their own accounts, and strategy pages, subscriptions and copy settings stay inside your business. Unlike the broker edition, the focus here is your own acquisition, client ownership and long-term operations.
Independent community site on your own domain and brand
Private or public operation
Clients bind their own MT4 / MT5 accounts
Cross-platform and cross-broker copying
No dependency on a single broker
The community site can be built around your brand, service model and client base. When you need profit sharing and agent settlement, it can be paired with a PAMM solution.
01
An independent site, not a page inside a platform
Your community has its own domain, brand and membership. You decide how clients arrive, what they see and how they copy, instead of operating under a third-party platform's rules.
Your own domain and branded presentation
Independent client registration and membership
Private service or public acquisition
You control content and strategy presentation
02
How do clients start copying?
Clients complete binding and copy settings themselves, so you do not operate accounts on their behalf.
1
Join your community
Clients register and sign in through your domain.
2
Bind a trading account
Clients connect their own MT4 or MT5 account.
3
Choose a strategy
Clients review strategies and performance, then decide who to follow.
4
Manage copying
Clients adjust copy settings and risk limits at any time.
03
Why does it not depend on a broker?
Clients keep their existing broker and account, and copy relationships are built through cross-platform, cross-broker replication. You do not need to concentrate clients at one broker or be limited by a single broker's access rules.
Clients keep their own MT4 or MT5 account
MT4 and MT5 can copy each other
Cross-broker and cross-server replication
Copy relationships are formed and managed inside your community
04
How is this different from PAMM for asset managers?
The community solves the site and copy relationships. PAMM solves profit sharing and settlement across multiple accounts. They can run separately or as one combined solution.
Community: your independent site, client binding and copy relationships
PAMM: profit sharing, agent rebates and settlement reports across accounts
A community-only setup does not involve profit sharing or agent settlement
Pair it with the PAMM asset-manager edition when you need a profit-share structure
05
Who is it for?
It suits asset managers, trading teams and signal providers who want an independent site and direct client relationships.
Asset managers who want clients under their own brand
Private-client teams running an invitation-led service
Trading teams that want public acquisition and strategy visibility
Signal providers who do not want to be tied to one broker
06
How is a community different from a copy trading system?
The copy system handles replication and risk; the community handles strategy discovery, subscriptions, operations and client ownership. For an asset manager, the community is the layer built on top of replication.
Copy system: order replication, account binding and per-account risk
Community: site, strategy profiles, subscriptions and operations tools
Both reuse the same server-side replication engine
They can be delivered separately or combined
07
What does an asset manager community need?
The core is helping clients find strategies and form subscriptions, while giving you visibility into clients, rebates and operations.
Strategy provider profiles and performance history
Client subscriptions, copy size and pause controls
Rebate and agent relationship configuration
Client portal and operations back office
Multi-language and own-brand configuration
08
What drives build time and cost?
Time and cost depend on site scope, brand and domain, languages, broker connections, the rebate or settlement model and any data migration. Communities are quoted per project with no fixed tiers.
Site scope: entry page, client portal or full community
Brand, domain and languages
Brokers and server connections
Rebate, subscription or settlement rules
Historical data and client migration
09
How is white-label delivery and data ownership handled?
Communities are delivered white-label, with the site, brand and client relationships owned by the asset manager. Standard deployments use a hosted replication bridge; isolated single-tenant deployment is optional.
Own domain, brand and site entry point
Client data and operations remain with the asset manager
Hosted bridge or private deployment
Add languages and markets in stages
10
How do the asset manager and broker editions differ?
The asset manager edition focuses on an independent site, self-driven acquisition and client ownership; the broker edition focuses on a branded portal, multi-server access and client tiers. Both reuse the same replication engine.
Asset manager edition: independent site, strategy profiles and subscriptions
Broker edition: branded portal, multiple servers and client tiers
Both can connect to PAMM profit sharing
Deliver by client segment
FAQ
Common questions about this system
Answers to common questions about copying, delivery and pricing.
01Can the community be private, public, or both?
All three. Private operation suits existing clients, public operation helps attract new ones, and you can move between models as the business grows.
02Do clients need to change brokers?
No. Clients keep their existing broker and MT4/MT5 account and copy on their own account.
03Can clients copy across platforms and brokers?
Yes. MT4 and MT5 can copy each other, and replication works across brokers and servers, with symbol and contract differences handled automatically.
04Who owns the site and domain?
The community operates under your brand and domain, so clients see your independent site. The exact domain, branding and operating scope are confirmed during planning.
05Can the community charge subscriptions or share profits?
The community focuses on the site and copy relationships. For profit sharing, agent rebates and settlement reports, pair it with the PAMM asset-manager edition rather than mixing the two capabilities.
06How much does it cost to build a copy trading community?
Communities are quoted per project based on site scope, brand, languages, broker connections and the rebate or settlement model. There are no fixed price tiers; we scope the requirement first.
07How long does a build take?
Standard replication can be connected quickly. A full community involves brand, site, rebates and migration, so timing is assessed per project rather than promised as a fixed number of days.
08Does the broker need to open extra permissions?
No. The system uses existing read-only or trading credentials and replicates orders through the API bridge; clients do not install plugins.
09Can we use our own brand and domain?
Yes. Communities are delivered white-label, with the domain, brand, languages and client entry point configured by the asset management team.
10How is a community different from PAMM?
A community organises clients around strategy subscriptions and copied orders. PAMM centrally manages accounts and settles profit shares. They suit different fee and operating models and can run in parallel.
FXCopyNex licenses copy trading software to brokers, asset managers and prop desks. We do not operate a brokerage, hold client funds, provide investment advice or execute trades on behalf of end clients.
Trading involves substantial risk. Past or simulated performance is not indicative of future results. Customers are responsible for their own regulatory permissions and suitability assessments.