White Label Futures Trading Platform
Launch a Branded Perpetual Futures Exchange in 8-12 Weeks
Perps, cross/isolated margin, Kraken/OKX liquidity, KYC/KYT, 100% source code. Request a live demo today.
Access to Demo
A custom build of equivalent scope runs $300,000–$500,000 and 9–18 months.
You do not need to build a derivatives engine to run a derivatives business. Our futures core already handles funding rates, mark price, margin modes and auto-liquidation in production. You pick the liquidity model, we apply your brand, connect your providers, and hand over the repository.
Two ways to start: request a live demo of the working futures terminal, or send your requirements and get a per-module hour breakdown within 48 hours at no cost.
Derivatives platforms fail on custody and infrastructure, not on UI. Every measure below ships in the base delivery — not as a paid hardening phase after launch.
| Layer | What ships in the base platform |
| Account security | 2FA via email, SMS and Google Authenticator with re-issue only (users cannot fully disable it), anti-phishing codes, device identification on login, SMS rate limiting against bombing, session expiry with forced re-login |
| Withdrawal control | Manual admin approval queue, per-coin minimum and maximum limits, confirmation flow for key actions, admin IP restriction, optional cold wallet integration (Ledger, Trezor, SecuX, KeepKey) |
| Application layer | Output filtering against XSS, input filtering against SQL injection, anti-CSRF tokens, secure headers, X-Frame-Options, HTTP-only and secure cookie flags, Google reCAPTCHA |
| Network & transport | Cloudflare DDoS protection, SSL termination, encrypted channels between internal services, hardened server configuration |
| Compliance | SumSub or Ondato for KYC, Elliptic or Crystal for KYT, AML risk scoring on every inbound deposit before the balance is credited |
| Optional | Independent white-hat penetration test and remediation from $20,000 |
We also implement forced wallet regeneration: when a deposit address gets flagged, the platform issues new addresses across every supported network and retires the old one. If you want the full threat model behind these decisions, our breakdown of crypto exchange security covers each attack surface in detail.
| Module | Capability |
| Perpetual futures terminal | 24h volume, open interest, 24h change, mark price and last price indicators; leverage selector; cross/isolated switch; order book; recent trades; open and closed position tables; open orders; trade and transaction history |
| Order types | Market, limit, stop-limit, take-profit and stop-loss |
| Margin engine | Borrow and repay flow, leverage selection, margin level monitoring, automatic liquidation at configurable thresholds, admin-set margin and liquidation limits |
| Charting | TradingView integration; paid tier available with 1-second timeframes, cluster charts and real volume oscillator for professional order flow |
| Wallet layer | Isolated balances per module (spot, margin, futures, P2P) with an internal transfer layer, or a consolidated funding/trading account model |
| Transfers | Off-chain UID-based internal transfers at zero fee, plus a unified EVM address covering every EVM-compatible network |
| Converter | Market-order abstraction routed through the trading engine, so users convert at real market rates rather than internal quotes |
This is the decision that shapes your cost, your licence exposure and your risk profile. We ship all three models.
| Model | How it works | Best for |
| A-book | Your backend acts as a broker layer over a Tier-1 provider. Master account plus per-user sub-accounts, orders proxied over REST and WebSocket, positions and history synchronised back. Custody and liquidity stay with the provider. | Fast market entry, minimal custody liability, no internal matching engine to operate |
| B-book | Every trade executes inside your platform against internal liquidity. Requires your own matching engine and a real risk desk. | Operators who want full spread capture and already have risk management competence |
| Mirroring (hybrid) | Orders are mirrored onto an external venue while funds remain in your hot wallet. In Borrow Mode the system borrows the equivalent on the venue at 3x margin, executes, credits the user, then clears the borrow. | Solving the cold-start problem without moving 100% of client funds to a third party |
If you go A-book, broker-mode API constraints on major venues limit you to isolated margin. Cross margin requires the B-book path or the hybrid model. We flag this in discovery rather than after contract signature. Choosing a venue is a separate exercise — our comparison of the best crypto liquidity provider options covers spreads, sub-account limits and API stability per venue.
You choose between self-hosted nodes and remote RPC providers. Self-hosted nodes satisfy regulators who require you to control the infrastructure; remote RPC through Alchemy or QuickNode lets you list new tokens without provisioning hardware. Both paths are wired into the same backend abstraction, so switching later does not mean rewriting the wallet service.
| Parameter | Merehead White Label | Build from scratch |
| Time to live | 8–12 weeks | 9–18 months |
| Investment | from $34,000 | $300,000–$500,000+ |
| Core trading risk | Production-tested engine, already handling real order flow | Unproven until your first live trading day |
| Liquidity | Provider integration included in delivery | Cold-start problem is yours to solve |
| Source code | Transferred in full on delivery | Yours |
| Licensing fees | None | None |
| DevOps | Kubernetes configuration ships with the platform | Built from zero |
| Customisation ceiling | UI, branding, modules on/off, custom modules on request | Unlimited |
The honest trade-off: if your product thesis depends on a trading mechanic nobody has built before, white label constrains you. If your thesis depends on distribution, brand and a specific market, the engine is a commodity and building it yourself burns nine months of runway. Our analysis of whether to build or buy matching engine infrastructure walks through the break-even maths for both cases.
| Starter | Pro | Enterprise | |
| Price (our solution) | $34,000 | $54,000 | from $64,000 |
| Same scope from scratch | $48,000 | $74,000 | $81,000+ |
| Development timeline | 2 months | 3 months | 3–4 months |
| Discovery phase | 1 month | 1 month | 1 month |
| Trading modules | Perpetual futures, futures wallet, internal transfers | + Margin trading with borrow/repay, fiat on-ramp, affiliate programme, intra-platform transfers | + Spot, P2P escrow, options, mobile applications |
| Admin panel | Base: users, KYC, fees, withdrawals, pairs, restrictions, market maker | Extended: admin roles, financial analytics, turnover-based fee tiers | Full: multi-module accounting, custom token listing, granular permissions |
| Liquidity | One provider integration | One provider plus market maker | Multi-provider with mirroring |
| Networks | BTC, ETH | BTC, ETH plus AML/KYC integration and partial liquidity connection | Full multi-chain, 60–70 assets |
| Module | Price |
| External liquidity integration (Binance, Kraken, OKX) | $4,000 |
| External KYC/AML service, single integration | $1,600 |
| Payment gateway integration (PayPal, Skrill, Simplex, ZotaPay) | $1,500 |
| Bank API integration, single bank | $2,500 |
| Blockchain node integration | $800 (BTC-family, Tron, BNB Chain, Polygon) / $1,000 (Arbitrum, Solana, EOS, Algorand) |
| ERC20 token listing, Ethereum node already integrated | $200 |
| Microservice architecture | +20% of platform cost |
| Turnover-based dynamic commission | $1,200 |
| Country-level access control | $700 |
| IP white/black list | $500 |
| Portfolio module with balance and earnings charts | $8,000 |
| Cold wallet integration | $1,300 (Ledger) / $2,300 (Trezor, SecuX, KeepKey) |
| CMS for platform text editing | $8,000–$16,000 |
| Independent white-hat security audit | from $20,000 |
| Additional interface language | $300 |
Payment structure: 20% upfront covering technical documentation and design, then two milestones of 40% each, split 50% prepayment and 50% on acceptance. If you want the numbers benchmarked against the wider market before you commit, our pricing guide on white label crypto exchange cost breaks down what vendors charge at each tier and where the hidden fees sit.
| Stage | Duration | What happens |
| Discovery | 2–4 weeks | Technical documentation, user flow, architecture design, platform design. Node synchronisation starts here, in parallel. |
| Branding and configuration | 2–3 weeks | Design tokens applied to the existing UI, layout adjustments through Figma, domain and SSL setup |
| Integrations | 2–4 weeks | Liquidity provider, KYC/KYT vendors, payment gateways, blockchain nodes, notification services |
| Mainnet testing and go-live | 1–2 weeks | Full deposit → trade → withdrawal cycles on every supported network using real mainnet assets, then admin handover |
This adds days and a small cost to the schedule. It is non-negotiable. A rebrand-only deployment, where you need no custom modules, compresses this entire sequence to under two weeks.
Challenge. The client wanted spot plus perpetual futures but had neither liquidity nor a budget for an internal matching engine and risk desk. A full in-house build of that scope prices at $300,000–$500,000 and runs into years.
Solution. We built the platform as a broker layer over a Tier-1 venue on an A-book model. Master account plus per-user sub-accounts on the provider side; a backend orchestrator proxies orders over REST and WebSocket and synchronises positions and history back to our database.
The terminal ships the full professional surface — order book, long and short positions, open orders, open positions, funding rate, open interest, volume, TradingView charts. Broker-mode API limits fixed us to isolated margin, which we scoped explicitly during discovery rather than discovering mid-build. Custody and liquidity stayed entirely with the provider.
Result. Live futures trading with no custody liability and no internal order book to operate. Futures integration took roughly three months. The client's deadline was tighter than that, so we ran spot and futures development in parallel instead of sequentially and hit it. Against a from-scratch equivalent, the CAPEX difference is an order of magnitude.
Challenge. An empty order book kills conversion on day one of a new exchange. The obvious fix — routing everything to an external venue — means parking client funds there, which the platform owner refused to accept.
Solution. We implemented order book mirroring in two modes. In No Borrow Mode, deposits move through the hot wallet to the venue and trade there directly. In Borrow Mode the funds never leave our infrastructure: when a user places a sell order, the system borrows the equivalent amount on the venue at 3x margin, executes against that market, credits the user's USDT balance, and settles the borrow from the hot wallet afterwards. We wired real-time monitoring of margin utilisation, borrow limits and USDT collateral positions, with Telegram and Slack alerts on every critical threshold.
Result. The order book reads as fully populated from launch day because it is backed by Tier-1 depth, while custody stays with the platform owner. We state the trade-off plainly to every client considering this model: if any of the three monitored components fails, user trades fail. Alerting on those thresholds is not optional infrastructure — it is part of the product.
Challenge. An exchange running on a monolithic virtual machine could not absorb projected trading load, and naive horizontal scaling broke state consistency in the wallet and order book services.
Solution. We rewrote 17 microservices as Docker containers, deployed them through Helm charts, integrated HashiCorp Vault for secrets management with GitLab CI pipelines, configured Horizontal Pod Autoscaler per service, and introduced a Redpanda message bus for inter-service communication. The decisive engineering choice was the scaling policy: stateless services such as the API gateway and notification service autoscale freely, while stateful services such as the wallet manager and matching engine do not.
Result. The platform went to production on Kubernetes. The transferable lesson we now apply to every project: define the scaling policy before writing Helm charts. Teams that write the charts first pay for the rework twice. The broader patterns behind this sit in our breakdown of crypto exchange architecture at scale.
| Revenue stream | Mechanics | In base delivery |
| Trading fees | Charged on full contract value, not trader margin. A $100,000 position opened at x50 leverage uses $2,000 of margin but generates fees as if $100,000 changed hands. | Yes, with turnover-based tiers as an add-on |
| Funding rate flow | Collected periodically from one side of the market and paid to the other; the platform retains a share. Independent of market direction. | Yes |
| Liquidation fees | A penalty applied when a position closes at the liquidation threshold. | Yes |
| Spread on conversion | Converter routes through the trading engine at market rates; you set the spread. | Yes |
| Listing fees | Projects pay to have tokens listed for futures trading. | Admin-side listing tooling included |
| Affiliate revenue share | Partner portal tracking visitors, registrations, first-time deposits, deposit volume and revenue share, with up to four offer types per partner. | Pro tier and above |
Derivatives count as financial instruments in most major jurisdictions, which puts them above standard VASP registration. Plan the licence in parallel with development, not after.
| Jurisdiction | Licence type | Indicative timeline | Key requirement |
| EU (MiCA) | CASP with derivatives authorisation | 6–12 months | Proof of capital reserves, documented risk management policy |
| UAE (VARA) | Virtual Asset Exchange plus derivatives permission | 4–6 months | Local office, AED capital requirement |
| Seychelles / BVI | Offshore VASP | 4–8 weeks | Minimal capital, no derivatives restriction |
| Bahamas / Bermuda | Digital Asset Business Act | 3–5 months | Established route for perpetuals |
| United States | CFTC DCM licence | Not a practical retail path | Multi-million dollar process; retail crypto perpetuals remain effectively closed |
We have built trading infrastructure since 2015 — centralised exchanges, P2P platforms, derivatives terminals and tokenisation systems across the EU, Middle East and Southeast Asia. The futures core we deploy was written for derivatives, not adapted from a spot template.
What that means concretely: our team has handled node integration across Bitcoin, Ethereum, Litecoin, Tron and BNB Smart Chain in production; dual-path KYC with two separate verification state machines; forced wallet regeneration on AML risk events; and order book mirroring with live margin utilisation monitoring.
Every engagement runs through a business analyst and project manager who produce the technical documentation before a line of code changes, with Scrum and Kanban delivery, demo builds at each logical milestone, and a 60-day warranty. If your scope extends past white label into a fully bespoke venue, our cryptocurrency exchange development team handles that path as well.
Our Starter package starts at $34,000 and covers the perpetual futures core, futures wallet and internal transfers, delivered in two months plus a one-month discovery phase. Pro is $54,000 and adds margin trading with borrow and repay, a fiat on-ramp, the affiliate programme and an extended admin panel, delivered in three months. Enterprise starts at $64,000 and adds spot, P2P escrow, options and mobile applications over three to four months. The same scopes built from scratch price at $48,000, $74,000 and $81,000 or more respectively. Add-ons are priced individually — for example, external liquidity integration is $4,000, a KYC/AML service integration is $1,600, and a blockchain node is $800 to $1,000 depending on the chain. Payment runs 20% upfront, then two milestones of 40% each.
You receive the complete repository on delivery, and there are no monthly licence fees or revenue share arrangements. You can commission independent security audits, bring in your own engineering team, fork the codebase or migrate hosting without our involvement or approval. The 60-day warranty period after handover covers defect fixes at no cost. This is the main structural difference between our model and SaaS white label vendors, who typically retain the code and charge a recurring licence plus a percentage of trading volume.
Derivatives are classified as financial instruments in most major markets, so a standard VASP registration is not sufficient. Practical routes include Seychelles or BVI for initial market entry, typically four to eight weeks; UAE VARA with derivatives permission, four to six months and requiring a local office and AED capital; and EU MiCA with CASP derivatives authorisation, six to twelve months and requiring documented capital reserves and a risk management policy. The United States has no viable retail path — the CFTC requires a DCM licence through a multi-million dollar process. Start the licensing track in parallel with development and retain local counsel; the timelines above are indicative, not legal advice.
Three approaches work in practice. First, run an A-book model where your platform acts as a broker layer over a Tier-1 venue — your users trade against that venue's depth from day one, and you never operate an order book. Second, use order book mirroring in Borrow Mode: funds stay in your hot wallet, the system borrows the equivalent on an external venue at 3x margin to execute, then settles afterwards. Third, launch with three to five core pairs only — BTC-PERP, ETH-PERP, SOL-PERP — to concentrate whatever depth you have rather than spreading it thin across fifty markets. All three ship in our platform. Which one fits depends on your custody appetite and licence scope.
Yes, but the model you choose constrains it. In an A-book deployment, broker-mode API limits on major venues restrict you to isolated margin — this is a provider constraint, not an implementation gap, and we flag it during discovery. Cross margin requires either the B-book path with an internal matching engine and risk desk, or the hybrid mirroring model where you control the margin calculation layer. Professional traders expect both modes, so if cross margin is a hard requirement for your target segment, plan for B-book architecture from the start rather than migrating later.
Under two weeks from contract to live platform. That path covers deploying the existing production-tested platform to a dedicated server, connecting your domain with SSL, replacing API credentials across all third-party services — payment processor, SMS provider, email, market data — applying your logo and colour scheme, running smoke tests on critical user flows, and handing over admin credentials. Design adaptation beyond a colour and logo swap adds two to three weeks. Anything requiring new modules moves you into the standard 8 to 12 week timeline.
