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 and logo, enters a key your platform issued, and copies trades — with no mention of CopyBridge anywhere in the experience.

This post explains what a white-label trade copier actually involves technically, how CopyBridge structures it, 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, logo, documentation, 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: WebSocket relay, position-sizing engine, trade caching, 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 brand layer is entirely yours. Your followers have no reason to know CopyBridge exists. 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 production-grade copy-trading backend without the engineering cost of building one. Building the infrastructure layer from scratch — broker adapters, WebSocket handling, position sizing, failover, monitoring — is a 6–18 month engineering project. White-labeling makes it a configuration task.

Brand-Controlled EA Distribution

The Copier EA that your followers install is compiled with your branding baked in:

• EA display name — shown in MT4/MT5's Expert Advisors panel and terminal logs
• Magic number prefix — a numeric range you own, so your EA's trades are identifiable and can be filtered by other tools
• Default server endpoint — points to the CopyBridge relay, but the follower sees your domain (via a DNS CNAME you set up)

You distribute the EA yourself — from your website, your Whop store, your onboarding email. There is no CopyBridge download link in the follower's journey.

The Master EA used by your signal providers is similarly branded. Providers under your reseller account see your product name in their MT4/MT5 terminal, not CopyBridge.

The Follower Experience

From a follower's perspective:

1. They purchase a subscription from your store (Whop, Stripe, 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) on any MT4/MT5 chart
4. They enter their key and connect
5. Trades copy automatically

At no point does CopyBridge appear in the UI, the logs, or the documentation they read. The relay connection is to your custom subdomain (copy.yourproduct.com → CopyBridge infrastructure). If they inspect the EA's network traffic, they see your domain.

Support tickets go to you. Billing questions go to you. You own the subscriber relationship entirely.

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 at the data layer, not just the UI layer.

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 developers reference documents the full integrator API including child provider provisioning endpoints.

Reseller Economics

White-label resellers pay CopyBridge at the infrastructure tier (integrator plan, seat-based). You charge your customers whatever your market supports — there is no revenue share with CopyBridge on what your subscribers pay you.

A typical reseller structure:

Seat billing for your subscribers is typically managed through Whop, which natively supports webhook-based key provisioning. When a subscriber pays on Whop, a webhook fires to your endpoint; your endpoint calls the CopyBridge API to issue a subscriber key and returns it to the subscriber. The whole flow is automatable with ~50 lines of code.

Technical Setup: End-to-End

Standing up a white-label trade copier on CopyBridge involves four configuration steps:

1. Create an integrator account Apply via the white-label page. The integrator tier is not self-serve — there is a brief onboarding call to confirm use case and set up the custom domain.

2. Configure your custom domain CopyBridge provisions a TLS certificate automatically. EA connections and webhook deliveries will use your domain.

3. 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: ik_live_YOUR_KEY" \
  -d '{
    "name":          "Provider Alpha",
    "magic_prefix":  9100,
    "plan":          "standard"
  }'

The response includes the child provider's X-API-Key. Pass it to your signal provider so they can configure their Master EA.

4. Deliver branded EAs Generate branded EA builds from the integrator dashboard. You will receive MT4 and MT5 .ex4/.ex5 files compiled with your EA name, your magic number range, and your relay domain. Host them wherever your onboarding flow points.

From this point, the platform runs without manual intervention. Trades flow from provider Master EAs through your relay subdomain to follower Copier EAs. You manage billing and subscriber keys; CopyBridge handles the infrastructure.

Is This the Right Model for You?

White-label makes sense when you are building a product or marketplace where CopyBridge attribution would be a problem — either for brand reasons or because you need to own the subscriber relationship fully. It requires more setup than a standard provider account and involves an integrator plan fee.

If you are a single signal provider with no reseller ambitions, a standard provider account at CopyBridge does everything you need without the white-label layer.

For resellers, marketplaces, and prop firms: the white-label landing page has pricing details and the application form.