White Label Trade Copier Explained: Run a Copy-Trading Brand Without Building Backend

"White-label" is an overloaded term. In the trade copier context it has a specific meaning: your brand on the client-facing surface, someone else's infrastructure doing the actual work. The follower downloads an EA with your name on it, enters a key your platform issued, and copies trades.

This post explains what a white-label trade copier actually involves technically, how CopyBridge structures it, where CopyBridge stays visible, and what the economics look like for a reseller.

What "White-Label" Means Here

A white-label trade copier arrangement separates three layers:

1. Brand layer — what the follower sees: EA name, color scheme, setup guide, support email
2. Operational layer — what the signal provider does: runs a Master EA, manages their subscriber list, handles their billing
3. Infrastructure layer — what makes it work: trade API, position sizing, trade storage, uptime

In a standard (non-white-label) setup, the brand and infrastructure layers are both CopyBridge. Followers know they are using CopyBridge, the EA says CopyBridge, the docs are at copybridge.io.

In a white-label setup, the EA and its setup guide carry your brand. The infrastructure layer is still CopyBridge — you are licensing it, not rebuilding it.

This is the practical value of a white-label trade copier: you get a copy-trading backend without the engineering cost of building one. Building the infrastructure layer from scratch — MT4 and MT5 EAs, a trade API, position sizing, monitoring — is a serious engineering project. White-labeling turns it into an API integration and a branded build.

Brand-Controlled EA Distribution

A branded build compiles the Master and Copier EAs for MT4 and MT5 with your details:

• Provider name — shown on the EA's status panel and in its terminal logs
• Company name and website — shown in the EA's copyright and link properties
• Color scheme — default, blue, gold or red, applied to the status panel

Each build also generates a follower pack: the Copier EAs plus a PDF setup guide with your name, website and support email.

That is the whole branding surface. There is no logo upload, and you cannot reserve a magic number range: every Copier build defaults to Magic Number 7770001, which the follower can change in the EA's inputs.

You distribute the EA yourself — from your website, your Whop store, your onboarding email. If you host the files, the follower never needs a CopyBridge download link.

The Master EA used by your signal providers is branded the same way, so they see the name from the build in their MT4/MT5 terminal. Builds are per child provider, so each child needs its own.

The Follower Experience

From a follower's perspective:

1. They purchase a subscription from your store (Whop or direct)
2. They receive an access key and a download link — both from your brand
3. They install the EA (labeled with your product name) and allow https://api.copybridge.io under Tools → Options → Expert Advisors
4. They attach it to any MT4/MT5 chart and enter their key
5. Trades copy automatically

CopyBridge is not invisible in this flow. It shows up in three places:

• The API address. CopyBridge does not offer custom domains or relay subdomains. Branded EAs connect to https://api.copybridge.io: it is the default ServerURL input, it appears in the EA's logs, and followers add it to MetaTrader's allowed URLs in step 3.
• The generated guide. The PDF carries your name, but its cover also says "Powered by CopyBridge" and its steps still mention CopyBridge, including the API address. You can write your own guide instead.
• Emails from the Whop webhook. If you let CopyBridge's built-in Whop webhook issue keys, subscribers get welcome and cancellation emails sent from CopyBridge, and the welcome email carries the CopyBridge logo and Telegram contact. Keys issued through the API trigger no email.

Without those emails, support tickets and billing questions go to you. You own the subscriber relationship.

Multi-Tenant Architecture

CopyBridge's multi-tenant model structures accounts in three tiers:

Integrator account (you, the reseller)
  └── Child provider A  (one of your signal providers)
        └── Followers: subscriber_001, subscriber_002 ...
  └── Child provider B
        └── Followers: subscriber_011, subscriber_012 ...

Your integrator account, authenticated with an X-Integrator-Key, can provision and deprovision child providers via API. Each child provider gets their own X-API-Key for Master EA auth and issues their own X-Subscriber-Key tokens to followers.

Crucially: child providers under your integrator account are isolated from each other. Provider A's followers cannot see Provider B's trades. Provider B cannot see Provider A's subscriber list. The isolation is enforced by the API on every request, not just in the UI.

This architecture supports common white-label use cases:

• A signal-provider marketplace where each provider is a child
• A prop-firm distributing trades across multiple funded cohorts
• An educator running separate signals for different course tiers

The API explorer documents the integrator API, including the child provider provisioning endpoints.

Reseller Economics

White-label resellers pay CopyBridge for an integrator plan. You charge your customers whatever your market supports — there is no revenue share with CopyBridge on what your subscribers pay you.

A simple reseller structure:

Subscriber billing can run through Whop. When a subscriber pays, a webhook fires to your endpoint; your endpoint calls POST /api/v1/providers/me/followers with the child provider's X-API-Key, gets a subscriber_key back, and sends it to the subscriber.

Technical Setup: End-to-End

Standing up a white-label trade copier on CopyBridge involves four steps. Steps 1 and 3 include manual work on CopyBridge's side.

1. Get an integrator plan Pick a tier on the white-label page. Checkout runs through Whop, and CopyBridge sends you your X-Integrator-Key by hand. Solo does not include branded EAs.

2. Provision child providers Use the integrator API to create a child provider for each signal provider on your platform:

curl -X POST https://api.copybridge.io/api/v1/integrator/providers \
  -H "X-Integrator-Key: $INTEGRATOR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name":  "Provider Alpha",
    "email": "[email protected]"
  }'

name and email are required. Each child needs its own email, which the generated guide prints as the support contact.

The response includes master_api_key and jwt_token. Store both: the integrator API does not return them again. Pass master_api_key to your signal provider, who enters it in the Master EA's APIKey input. The EA sends it as X-API-Key. The jwt_token expires after 90 days and cannot be renewed through the API.

3. Set the child's plan A child created this way starts on the free plan: 2 followers and no branded builds. To change either, email [email protected] with the child's provider.id, and CopyBridge sets the plan and follower limit by hand. Branded builds need the child on Professional or higher.

4. Deliver branded EAs Child providers have no dashboard login, so builds run through the API. Once the child is on Professional or higher, request a build with POST /api/v1/providers/me/ea/build, with the child's jwt_token as a Bearer token and your providerName, companyName, website and colorScheme in the body. Then download the .ex4/.ex5 files from GET /api/v1/download/ea (type is master or copier, platform is mt4 or mt5) and host them wherever your onboarding flow points.

From this point, trades flow from provider Master EAs through the CopyBridge API to follower Copier EAs. You manage billing and subscriber keys; CopyBridge handles the infrastructure. Some things stay manual: plan and follower limit changes and expired jwt_tokens go through CopyBridge, and a branded build does not update itself, so a new EA release needs a new build and a new download for your followers.

Is This the Right Model for You?

White-label makes sense when you are building a product or marketplace under your own brand and need to own the subscriber relationship. It requires more setup than a standard provider account and involves an integrator plan fee. It is the wrong fit if CopyBridge has to stay fully hidden, since followers connect to api.copybridge.io.

If you are a single signal provider with no reseller ambitions, a standard provider account at CopyBridge does everything you need without the integrator layer. On Professional or higher, you can build branded EAs from your own dashboard.

For resellers, marketplaces, and prop firms: the white-label landing page has pricing details and checkout for each integrator tier.