White label trading software

By the TradeAgentic engineering team·Published 30 August 2026·Updated 30 August 2026

What white label means here

Putting your name on software somebody else built, and presenting it as your own product. In this category it usually comes bundled with source access, because a name change alone is rarely the point. The buyer normally wants to develop the thing further.

It is a different purchase from a licence to run. You are acquiring a codebase and a maintenance obligation, not a working system somebody else keeps working.

What you can and cannot change

What you should be able to change

The name, the mark, the colours and the copy, obviously. Beyond that, the parts that make it yours: which markets it covers, which brokerage it connects to, the defaults it ships with, and the way it presents itself to whoever you sell it to.

Broker connectivity is the one to interrogate. Adapting a system to a different brokerage is real work, and whether that work is included, quoted separately, or left entirely to you is the single largest variable in what a source deal actually costs.

What should not change, whoever's name is on it

The protections. If you rebrand a system and then loosen its risk controls to make it look more attractive, you have taken on the consequences of every account it runs. Loss limits, the control that flattens everything, protective orders resting at the broker, and the refusal to trade when checks fail should survive rebranding untouched.

The same goes for the honesty of what it reports. A system that reconciles to the broker should keep doing so after you put your name on it, because the first time your numbers disagree with a client's brokerage statement, the name on the software is yours.

What source access has to include to be worth anything

The right to build. Source you cannot compile into a working product is a document, not a deliverable. Expect the complete engine and application, the research code that produced whatever priors it ships with, and enough documentation to build it from a clean machine.

Expect restrictions on redistribution, and expect them to be specific. There is a large difference between selling a rebranded product to end users and reselling the source to another vendor, and the licence should say which one you are buying.

Handover and ongoing obligations

Handover

A source deal without a handover is a zip file and a wish. Budget for direct time with whoever built it, covering the architecture, the parts that are load bearing, and the reasoning behind decisions that will otherwise look arbitrary when you come to change them.

Ask for that time in writing as part of the deal, not as a favour afterwards.

Support obligations transfer with the name

The moment your brand is on the product, your customers contact you, not the vendor. Whatever support arrangement you have with the vendor sits behind that, and it needs to be able to answer questions fast enough that you can answer yours.

Price the support obligation into what you charge. It is the cost most often forgotten in a white label deal, and it does not appear until you have customers.

Compliance sits with whoever sells it

If you present the product as yours, the regulatory questions come to you. What you may say about it, what disclosures accompany it, and who may be sold it are your responsibility in your jurisdiction, regardless of what the original vendor does in theirs.

That is not a reason to avoid white labelling. It is a reason to involve someone who knows your regulatory position before you sign, rather than after your first customer.

Commercials and fit

What it costs beyond the licence

Adapting to another brokerage, ongoing maintenance, your own support function, and whatever your regulatory position requires. The licence fee is usually the smallest of those over a couple of years.

Budget on the assumption that you are taking on a product, because you are.

Who this suits

Firms that already have a client base and want to offer something to it, and firms that want to build on a working foundation rather than start from nothing. It suits nobody who simply wants to run the software, for whom an ordinary licence is far cheaper and far less work.

What to ask for in the deal

Complete source and build rights. Documentation good enough to build from a clean machine. Direct handover time with whoever wrote it. A clear statement of what redistribution is permitted. Some period of maintenance updates while you get established.

Agree all five before signing. Each is straightforward to include at the outset and awkward to request later.