White Label Trading Platform Cost

The first question a broker, prop firm or fintech operator asks when evaluating a white-label trading platform is what it actually costs. The second question, usually within a week, is why every vendor's website hides the number behind a contact-sales wall.

There's a straight answer. This playbook breaks down what an operator actually pays across the platform stack, gives industry-typical ranges per bucket, compares building versus licensing across 24 months, and lists the questions to put in front of any vendor before signing. See what is a white-label trading platform for the definition and scope. This one is about the money.

The Seven Cost Buckets

Every white-label deal — whether packaged as one line item or unbundled across five vendors — breaks down into the same seven buckets. Any quote that leaves a bucket out is a quote that will be topped up later.

• Matching engine license. The core price-time-priority CLOB, order lifecycle, risk engine, margining, funding, liquidation and settlement paths. Licensed per-venue or per-symbol depending on vendor. It's the load-bearing component, and the one operators most often try to build in-house
• Liquidity access. Market-maker relationships, prime-broker or venue connections, hedging routes to lay off HOUSE inventory. Priced as a monthly retainer to an LP, per-trade rebates and fees, or bundled with the platform
• Custody integration. Where client funds actually sit. Third-party crypto custodians, banking partners for fiat rails, or self-custody with an insured hot/cold wallet split. Priced on assets-under-custody or per-transaction, usually with a monthly minimum
• KYC/AML vendor. Identity verification, sanctions screening, ongoing transaction monitoring, source-of-funds workflows. Priced per verification and per ongoing check. Non-optional in any regulated jurisdiction
• Hosting and infrastructure. Colocated bare metal or cloud, low-latency network paths to liquidity venues, database and disaster-recovery footprint, monitoring stack. Runs into five figures monthly at any real scale
• Ops staffing. Risk analysts, compliance officers, treasury operations, on-call engineers, customer support. The line item most first-time operators underestimate — even a lean operation is several full-time hires
• Regulatory licensing. Broker-dealer, MSB, VASP, CASP, FSP or equivalent depending on jurisdiction and product set. Legal setup, capital requirements, ongoing compliance filings, audits. Runs from tens of thousands to several million USD upfront depending on where the venue is registered

Six of the seven are external contracts with real counterparties. Only the matching engine is a build-versus-license decision — and it's the one that most defines what the other six end up costing.

Rough Ranges Per Bucket

Industry-typical ranges. Not any single vendor's quote. Numbers vary by scale, jurisdiction and how hard the operator negotiates. Treat this as calibration, not a menu.

The pattern is clear once you run the numbers: the platform license isn't the biggest recurring line item on any real deployment. Ops staffing and regulatory maintenance dominate. Which means the largest lever the operator holds is what the platform layer forces the ops team to do — how many people it takes to run the venue, how much of the reconciliation and risk surface is automated, and how much of the daily workflow is native tooling versus one-off scripting duct-taped together at 2am.

Building In-House Versus Licensing: The 24-Month View

Every technical founder considers building the matching engine in-house. Most abandon the plan around month six. A realistic 24-month build-in-house budget covers this:

• Engineering: matching engine, risk system, margin engine, funding and liquidation engines, ledger, admin console, ops surface, trader-facing web and mobile clients, market-data handlers, WebSocket gateway. Even a lean team of six senior engineers over 18 months is well into seven figures fully loaded
• Integration: liquidity provider connections, custodian API integration, KYC vendor integration, banking rails, chain analytics. Each is weeks of engineering plus legal review
• Testing and hardening: order-book chaos testing, fault injection on the settlement path, capacity testing under 10x load, external security audits. Below-the-waterline work that a first-time operator rediscovers the hard way in production
• Regulatory delay: launching a jurisdiction-approved venue often takes longer than the build itself. Runway burns during the wait, with no client revenue offsetting it

The comparison isn't close. Building runs 10-100x more expensive than licensing over the same 24-month window, and every dollar of that spend is capital that doesn't generate a single dollar of client revenue until the venue is actually live.

The $70,000 first-year platform-and-liquidity number on Basis Points is documented on /pricing with no sales-call wall. Custody, KYC and regulatory are arranged separately with the operator's chosen vendors under their own direct contracts — see the section below for why that separation matters rather than being an unbundling trick.

Cost Pitfalls Hidden in Vendor Contracts

Three patterns eat the cheap out of most white-label deals inside the first year. Read every contract with these in mind.

• Per-trade fee ladders on top of the platform fee. The vendor's monthly quote covers the platform. A separate per-trade cent-fraction fee is charged on every fill. At any real volume it dominates the platform fee within months. Some vendors bury the ladder in an appendix; some invoice it as transaction processing. Same line item you didn't price on day one
• Forced upgrade cycles. The vendor announces a v2 of the platform with a one-off migration fee, or sunsets the version the operator is on. Migration is the vendor's leverage — the operator either pays the upgrade fee or rebuilds every integration on a new stack. A well-drafted contract locks in the current version's price and defines a minimum notice for deprecation
• Vendor lock-in via non-standard APIs. The vendor's order-entry API, admin API and reporting schema are proprietary. Every operator tool the ops team writes is bound to those endpoints. When the operator wants to move platforms two years later, every one of those tools has to be rebuilt. Invisible on day one. Enormous on day 700

The clean pattern is the opposite: flat monthly, no per-trade top-up, published price schedule, standard REST and WebSocket APIs the operator's team can grep documentation for without an NDA in the room.

What to Ask Before Signing

Ten questions that separate an operator who's done the homework from one the vendor can quietly overcharge.

• Is the recurring fee flat, or does it include a per-trade or per-user ladder?
• What's included in the setup fee, and what's billed separately?
• What's the minimum term, and what's the notice period to exit?
• How is version upgrade handled — free within contract, or billed as new work?
• Is liquidity bundled, or a separate contract with a third-party provider?
• Are custody, KYC and regulatory arranged by the vendor or by the operator?
• Does the platform expose standard REST and WebSocket APIs, or vendor-proprietary schemas?
• Where does the operator's ledger and client-data footprint sit — vendor's cloud or operator-controlled infrastructure?
• What's the SLA on ops support, and how are incidents escalated?
• Can the price be locked for 24 or 36 months from signature?

Any vendor that hesitates on the first three isn't a vendor to build a real-money venue on. See how to launch a crypto perpetuals exchange in 2026 for the operational sequencing that turns these answers into a launch plan.

What Basis Points Ships

Every number on the Basis Points pricing page is public and flat: $10,000 one-time setup and $5,000 per month, all-in for platform and liquidity. That covers the matching engine, risk system, margining, funding, liquidation, insurance-fund logic, mark-price blender, trader dashboard, admin console, ops surface, standard REST and WebSocket APIs, monitoring, and every version upgrade within the contract. No per-trade fee ladder. No forced-upgrade line item. No NDA required to see the schedule.

Custody, KYC/AML and regulatory licensing are arranged separately — the operator contracts directly with the custodian, verification vendor and regulator of their choice. That's a deliberate design decision, not an unbundling trick. Those three areas are jurisdiction-specific and sit on the operator's legal liability. A platform vendor sitting in the middle of them is a lock-in vector, not a saving.

The team's ~30 years of combined experience shipping matching engines, hedging stacks and venue infrastructure sits behind every default in the platform. Standard 12-month initial term, USD or USDT invoicing, one to six weeks from signature to production. Priced so an operator can run the full 24-month total-cost-of-ownership number on the back of an envelope before the first call.

The full white-label decision isn't just what the platform costs on day one. It's what the operator pays over 24 months across all seven buckets, what leverage the vendor keeps in the contract, and how fast the operator gets to a first paying client without spending capital that could have funded ten hires instead. Get that right and it's a contract decision made once. Get it wrong and it's an invoice the operator explains to the board every quarter for years.

Frequently Asked Questions

Evaluating the platform?

Related articles