Pelican Trading: broker copy infrastructure, platform integrations and entity-specific permissions

Pelican supplies broker-facing copy-trading infrastructure and branded user interfaces, alongside its Pelican Trading customer-facing presence. The model connects a broker’s clients with strategies and copying workflows rather than replacing the underlying brokerage account. It can involve technology and regulated-service relationships, so the contracting entity and jurisdiction matter more than the umbrella brand.[1]

A strategy catalogue can reduce the work of populating a new service, but it does not establish that the strategies are suitable for an individual user or that past results can be repeated. The broker’s operating rules and client-facing disclosures remain essential.

Pelican announced its cTrader integration on 16 April 2026 and described an early live deployment with G4Trade. The June DXtrade announcement expands the described cross-platform functionality.[4][5]

The copy process needs controls at more than the connection boundary. A provider may trade a symbol unavailable at a follower’s broker, or use a position size that cannot be reproduced under the follower’s minimum lot and margin rules. An integration test should include these rejected or resized cases, not only a successful sample trade.

No complete current public broker-enterprise tariff was established from the inspected sales pages. The broker-facing technology agreement, the customer’s trading costs and the strategy-provider remuneration are different commercial layers. They should not be merged into a single claim that copying is free.[3]

For a fee example, use realised or eligible profit as defined in the contract rather than assume that a percentage is applied to total account equity. Establish how deposits, withdrawals, earlier losses and manual position changes affect the calculation. No general rate is inferred from a marketing example or a particular strategy screen.

Pelican’s published build process begins with brand assets and broker connection details, followed by a stated one-to-two-week build phase, testing and launch. That is a vendor outline, not a promise that regulatory assessment, broker integration, app approval and customer migration will all finish inside the build window.[2]

Acceptance should follow a strategy change through signal generation, risk checks, copied order, execution acknowledgement and the final account record. Include instrument substitutions, minimum sizing, insufficient margin, partial fills and closed markets. For each exception, decide whether the system retries, skips or requests intervention.

The supplier’s operating guide discusses a record of client actions, strategy changes and copied-order outcomes. A broker should agree the actual exported fields and retention rules, rather than treat a general auditability description as proof that every needed complaint record will remain available.[7]

An execution dispute may require records from both the copying provider and the broker. Keep the original signal, intended allocation, copied instruction, broker response and price timestamps. No 24/7 response commitment, customer-specific incident SLA or measured support result was established from the inspected public contacts.

CySEC’s register identifies Pelican Exchange Europe (CY) Ltd, company registration 426432, licence 441/24 dated 15 January 2024, and the approved trade name Pelican Exchange EU. The register’s approved domain is pelicaneu.com. Those facts apply to the named Cyprus entity, not every global website or broker using the software.[10]

The UK website wording is inconsistent: one line claims direct FCA authorisation while another describes Pelican Exchange Ltd, FRN 739090, as an appointed representative of London & Eastern LLP, FRN 534484. A complete current FCA firm-detail record was not independently retrieved here. This profile therefore does not resolve that inconsistency by asserting either wording as a verified current UK status.[1]

A 27 August 2026 provider announcement also claims South African approval and discusses other jurisdictions. That announcement is not an independently matched register entry in this profile. Any proposed cross-border service needs the current entity, permission and customer-scope evidence before deployment.[12]

Companies House identifies Pelican Exchange Ltd under company number 09437275. Corporate registration is distinct from financial-services permission. The UK company and the separately registered Cyprus investment firm must not be collapsed into one regulatory identity.[11][10]

Pelican’s 2026 product announcements establish active work across several platforms and distribution formats. They do not establish a common contract, common fee or common protection regime for every end user. The broker should record which company supplies software and which, if any, performs a regulated service.[4][5]

Operator

Pelican Exchange Ltd and Pelican Exchange Europe (CY) Ltd; the contract and jurisdiction determine the supplier

Service scope

Pelican combines branded copy-trading technology and strategy distribution. The profile examines its integration model, commercial layers, implementation, operating controls and the limits of the available regulatory evidence.

Customer types

Brokers offering copy-trading services; Strategy-distribution and introducing-broker businesses; Broker technology and compliance teams

Delivery

Hosted; API; Managed service

Pricing publication

Quote only

Platforms

Pelican white-label applications; Private Signal View; Pelican Network

Implementation

Branding and broker connection setup followed by testing; the advertised build phase is not an end-to-end deployment guarantee.

Support

Commercial contact plus Cyprus-entity register contacts; no universal support SLA established.

Permissions and regulatory scope

Cyprus register identity verified; current UK website wording conflicts and the full FCA status was not independently resolved.

Provider metadata checked 20 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 7Source 8Source 9Source 10Source 11Source 12

The published member terms warn that copied trades can receive different prices and results because of latency, manual changes, stop settings or insufficient margin. They do not guarantee that a follower reproduces the original strategy outcome. The separate risk warning should be read with the current broker and member agreements.[8][9]

A particularly important operational question is what happens when copying is stopped. Ending future signals, closing existing positions and cancelling pending orders are separate actions. The publicly inspected material did not establish one universal rule for all integrations. The broker must present and test the applicable behaviour, including residual fees and the customer’s ability to manage remaining exposure.

A leaderboard or strategy label should never replace the operating record. A robust reference set includes the strategy’s observed period, account context, fee treatment and changed or discontinued status.