Building a cryptocurrency exchange from scratch is a multi-year engineering project. You need a matching engine, multi-network wallet infrastructure, identity verification, fiat rails, an admin panel, and a security model that survives contact with real attackers. A ready-made exchange script compresses that into an installation. The trade-off is that you inherit someone else's architecture — so the only question that matters is whether that architecture actually covers what an exchange needs. This guide sets out what a serious white label platform must include, how to evaluate one before buying, and where the genuine costs sit on both paths.
What building in-house actually costs
The engineering estimate people usually give themselves is the matching engine. That is the part everyone thinks about, and it is not the expensive part.
The expensive parts are the ones that never finish. Wallet infrastructure across multiple networks means running nodes, handling reorgs, managing hot and cold custody, and reconciling deposits that arrive with the wrong memo. Fiat rails mean payment-gateway integrations, each with its own reconciliation logic and failure modes. Identity verification means either building document forensics yourself or integrating a provider. Then there is the admin panel, the ticketing system, the notification layer, the referral logic, and the reporting that finance and compliance will ask for on day one.
None of this is intellectually hard. All of it is time. A realistic in-house build is measured in years and a permanent team, not in a launch date. That is the number worth comparing against — not the licence price of a script.
What a complete exchange platform must include
Not every product marketed as an exchange script is complete. Many cover spot trading and stop there, which leaves you with the easy 30% and none of the operational reality.
A platform worth deploying covers, at minimum:
- Markets: spot, futures, swap, margin and P2P — with Market, Limit, Stop-Market and Stop-Limit orders. Users expect Binance-style order types; anything less reads as unfinished.
- Wallets: multiple custody models across many networks, plus dust conversion so users can clear unusable balances.
- Identity: built-in KYC, ideally two-stage, so limits can rise as verification deepens.
- Fiat: multiple payment gateways, open banking where available, and a manual review path for transfers that need approval.
- Operations: ticketing, internal chat, SMS and email panels, notification channels, staking, referrals, bonus schemes and tiered user levels.
- Security: two-factor authentication, admin controls and database backups.
Our exchange platform ships all of the above, including six user tiers, three wallet models and four notification channels — because in practice each of these is a support burden if it is missing.
Compliance is not an add-on
The most common gap in exchange scripts is compliance. A platform that lets anyone deposit anonymously is not a business you can bank, and no payment provider will keep processing for you once they understand the exposure.
You need two distinct controls. KYC establishes who your users are at onboarding. KYT tells you what their money is doing afterwards — screening deposit addresses before you credit them, and withdrawal destinations before you release funds. Sending to a sanctioned address is, in most jurisdictions, the more serious violation of the two, and it is the one deposit-only screening misses entirely.
If you onboard corporate clients or market makers, you also need KYB to verify the company and its beneficial owners. Building this stack yourself means sourcing sanctions data, maintaining it, and defending your methodology to a regulator. Integrating it means an API call.
Licence or source code: which to choose
Turnkey platforms are usually sold two ways, and the right choice depends on your engineering plans rather than your budget.
A limited licence installs the platform on your server for a single domain, branded to you, with support. It is the right choice if you intend to operate the exchange as delivered and do not plan deep customisation. Our limited licence is $1,200 and includes all markets, built-in KYC, multi-network wallets and a payment gateway.
A full source-code handover removes the domain restriction and gives you the code outright, so your team can modify anything and launch as many deployments as you want. That is $12,000. It is the right choice if you have developers and a roadmap of your own — and the wrong choice if you do not, because owning source you cannot maintain is a liability rather than an asset.
Both are one-time purchases rather than revenue shares. Current details are on the exchange platform page.
How to evaluate a script before buying
Ask for a live demo environment rather than screenshots, and place real orders in it. Screenshots hide latency, broken states and half-built admin screens.
Then check the parts vendors tend to skip. Does the admin panel let you actually run the business — adjust limits, review flagged withdrawals, resolve tickets — or is it a thin CRUD layer? Is there a real reconciliation view for deposits? Can you see what happens when a deposit arrives under-funded or on the wrong network, since that will happen weekly?
Ask what the technology stack is and whether it is one you can hire for. Ask what is included in support and for how long. And ask directly whether the compliance layer is built in or assumed to be your problem — a surprising number of vendors leave that entirely to the buyer without saying so.
A realistic launch sequence
Buying the platform is week one, not the finish line. A workable sequence looks like this.
Install and brand the platform. Connect your payment gateways and test each one with small real amounts, including failures and refunds. Enable KYC and run verifications end to end, deliberately including a poor-quality document so you learn your review rate. Configure screening on deposits and withdrawals, with conservative thresholds at first. Set your fee schedule and user tiers. Then run a closed beta with real money and a small group before opening registration.
The beta is the step teams skip and regret. It is where you discover that your withdrawal approval queue has no owner, or that nobody has decided what happens when a screening result comes back medium at 2am.
Exchange or prop platform?
Some operators discover partway through that what they actually want is not an exchange. If your model is funding traders and taking a share of profits rather than matching orders and taking fees, that is a prop trading platform — a different product with challenge rules, funded accounts and payout logic.
The two share an identity and screening layer, so the compliance work carries over. But the core mechanics differ enough that picking the wrong one costs you a rebuild. Decide which business you are in before you buy either.
See what the exchange platform includes — Pricing · Services · KYT · KYC · KYB · Exchange · Prop