Trading Platform Business Model: How a White Label Platform Earns
A trading product is paid for in several places, and not every place is open to every operator. This page sets out the six income lines built into the platform, the four kinds of customer it can serve, the order in which to switch lines on, and the line that no software can switch on for you: permission to operate. We supply the software. Your registration, your broker agreements and your compliance sign-off stay with you.
Plan My Income Mix →See the CostFour Customers One Platform Can Serve
A trading product is not a single audience. The same engine reaches four different buyers, and each one is willing to pay for something different.
Investors With Several Accounts
People who already hold accounts with two or three brokers and tidy up the numbers by hand. They pay for one order book, one profit-and-loss view and one watchlist that spans every account they connect.
Strategy Builders
Traders who write or tune their own strategies and would rather skip maintaining broker connectors. They pay for scoped keys, rate limits, webhooks, client libraries in seven languages and a paper-trading stage before any real capital.
Advisory Desks
Advisors who look after many client accounts and need basket execution plus consolidated reporting instead of a single-account retail screen. Time saved on daily reconciliation is what they are buying.
Partner Firms and Builders
Firms for whom trading is one part of a wider product, and agencies serving them. They pay for source ownership, theming and a documented API, and they answer to their own regulator, not to ours.
Software Is Not Permission
Every income line below is a setting. Whether you are allowed to use that setting is a different question, and it is yours to answer.
Orders on this platform route to the broker a trader already holds an account with. That design means you can launch a branded product without becoming a broker or holding client funds. It also means the platform gives you no licence, no exchange membership, no clearing arrangement, no custody and no source of liquidity. Those belong to your brokers and, where your model needs them, to you.
Read every row on this page with that in mind. An order fee slab is a field in the console. Whether you may charge one, and what registration that requires in your market, depends on how you operate and on what your broker agreements say. The same applies to referral income and to licensing the platform onward to a partner firm. The platform aligns its KYC and audit workflows to SEBI expectations, which is not the same as being certified, approved or registered by anyone.
Take advice from a qualified adviser in your own jurisdiction before you choose which lines to activate. Our six working days cover rebranding and deployment. Your registration and compliance sign-off run on their own timeline, and none of it is included in the price.
Why Sit Above the Brokers Instead of Inside One
Where the commercial difference between two product shapes actually comes from.
| Question | Product tied to one broker | Product above eight brokers |
|---|---|---|
| Who can become a user | Only people who hold, or will open, an account with that one broker | Anyone with an account at any connected broker |
| What a change in broker terms does | Lands on you with no alternative to move to | Lets you shift order flow toward the better commercial deal |
| How many income lines are open | Usually fees, sometimes a plan | All six, subject to your own status |
| Effort to add another broker | A fresh integration project each time | One adapter; order, trade and position logic stay as they are |
| What is hard to copy | A screen layout is easy to imitate | Breadth of connections and a documented audit record take time to match |
How Established Trading Platforms Earn
The common patterns across the category, and what each one means once you own the platform yourself.
| Earning pattern | How it generally works | Your position as a platform owner |
|---|---|---|
| Fee per executed order | A charge on each order, often capped, often heavier on intraday and derivatives activity | The slab structure is configurable per segment and per broker. Whether you may charge it is a question about your status and your broker agreement |
| Volume dependence | Thin economics per order that only add up across very large order counts | The trap for a newcomer. A smaller base needs lines that do not depend on order volume |
| Interest on client balances | Earnings on money held on behalf of customers | Not open to you. Client funds sit with each user's own broker, and the platform holds none |
| Paid tiers for tooling and data | Plans that unlock better charts, data, limits and programmatic access | Shipped as subscription and access tiers that gate broker count, strategies, order limits and API use |
| Account-opening and referral income | Payment when a new customer opens an account through a partner | Shipped as referral revenue, by volume or a flat fee. The terms come from your agreement with each broker |
The key difference: a broker earns on the flow it executes and the balances it holds. A platform owner that routes to other people's brokers earns on the tooling around that flow. That is a workable business at small scale and a different one at large scale, which is why plans and access tiers weigh more here than fees on day one.
Six Income Lines, Each Set in the Console
What each line charges for, and what you control as the operator.
| Line | What it charges for | What you control |
|---|---|---|
| Order fee slabs | Executed orders, by segment and by broker | Slab structures and tier overrides in the admin console |
| Subscription tiers | Access to a plan, from free through institutional | How many brokers, strategies, orders and API calls each tier allows |
| API access tiers | Programmatic access for strategy builders and partners | Rate limits and scopes, sold as separate levels |
| Referral income | Broker accounts opened through your product | Volume-based or flat arrangements, as your broker agreements allow |
| Gateway fees | Deposits and withdrawals | Transaction fees across the two payment gateways and direct UPI rails |
| Onward licensing | The platform, licensed to partner firms | Usage-based pricing that grows as the partner grows. The partner carries its own permissions |
Changing any of these takes no code change and no redeployment. Slabs, tiers, rate limits and referral arrangements are operator settings, so you can adjust as you learn what your market will bear. Miracuves takes no share of any line and charges nothing per user or per order.
Which Line to Switch On First
Turning on every fee at launch is a quick way to lose a user base you have not yet earned. A more careful order follows.
| Stage | Switch on | Hold back | What to watch |
|---|---|---|---|
| Before launch | Nothing yet. Confirm which lines your status and broker agreements allow | Any line you have not checked | Written answers from your adviser and from each broker |
| First users | Plans with a free tier, plus the fees you are cleared to charge | API tiers, referral and licensing | Order success rate, reconciliation accuracy and support load per active user |
| Some traction | Paid tiers, referral income where agreed | Onward licensing | Which tier gates actually convert, and whether referral volume is worth the terms |
| Established base | API access tiers, onward licensing | Nothing further | Contract value against support cost, and infrastructure headroom per tier |
This is an order for planning, not a forecast. We publish no revenue projection for this platform, because any honest figure depends on your segment mix, your fee structure and your market. Ask for a scenario worked against your own assumptions instead of trusting a generic table.
Income Lines by Stage and Sensitivity
All six ship and all six are configurable. This is the order they tend to matter in, what each needs first, and where your own permissions come into play.
| Rank | Line | Needs first | Typical stage | Where permission matters |
|---|---|---|---|---|
| 1 | Subscription tiers | A price, and a decision on what each tier gates | Launch | Charging for software access; confirm the treatment in your market |
| 2 | Gateway fees | Deposits and withdrawals passing through your gateway accounts | Launch | Your gateway agreements and local payment rules |
| 3 | Order fee slabs | Slabs defined per segment and per broker | Launch or soon after | Highest sensitivity. Depends on your registration and your broker agreement |
| 4 | Referral income | Referral agreements with the brokers you connect | Early growth | Set by each broker and by local rules on introducing clients |
| 5 | API access tiers | Rate limits and scopes, plus strategy builders to sell to | Growth | Mostly commercial; keep user agreements clear about what the access is |
| 6 | Onward licensing | A working deployment to show a partner | Scale | Each partner must hold its own permissions for its own model |
Referral and onward licensing are relationships more than settings. They also tend to carry the largest value per unit of effort, which is why a working retail deployment is best seen as the thing that makes them possible.
Three Ways Operators Run It
One engine, three different routes to market. These are shapes, not separate products, and none of them is a forecast.
The Branded Multi-Broker Product
A firm serves investors who already hold accounts at several brokers. Plans and access tiers lead, gateway fees follow, and order fees join only where the firm's own status and broker agreements allow them. Referral income comes in once there is an active base to point at.
The Strategy and API Product
An operator packages the strategy engine, paper trading and the seven client libraries as a product for people who write their own logic. Strategy slots, rate-limit tiers and paper-trading access are what customers pay for, and the operator maintains no broker connectors of its own.
The Platform Licensed to Partners
A firm deploys the platform for partner companies, each with its own broker set and fee structure. Usage-based licence terms scale as partners grow, and each partner answers for its own permissions and compliance posture.
Advisory desks, education and research businesses and community products are variations on these three shapes. Real outcomes depend on your market, your permissions, your broker terms and how well you execute.
How an Order Moves Through the Platform
Each stage can be observed on its own, which is what lets a fee be traced back to the order that produced it.
Validation
The order is tested against instrument, segment and session rules before it leaves the platform.
Risk Check
Limits you define are enforced per user, including position and order-value caps.
Margin Verification
Available margin is confirmed before the order is released, with warnings as it runs low.
Broker Submission
The order goes to the user's own broker through that broker's adapter. The fee slab you configured applies here.
Fill Reconciliation
Fills flow back into positions and profit and loss, and are written to an append-only audit log.
What Renting or Scripting It Does to Margin and Control
The mechanism behind each route. Costs that recur, and rights you may never hold, rarely show up as a single line on a quote.
| Dimension | Hosted platform on rent | Boxed script | Owned platform |
|---|---|---|---|
| Source code | Usually stays with the vendor | Some vendors withhold it from every published tier | The complete codebase is handed over |
| Fee settings | Often bounded by the vendor's own rules | Basic, and custom work for anything more | Slabs, tiers and limits are yours to set |
| User records | Often held on the vendor's servers | Held wherever you host it | In your own database, with no hosted dependency on us |
| Recurring cost | Around $2,000 to $3,500 a month, which may bundle hosting and licensing | One-time, roughly $250 to $1,500 on the open market | $15,999 once, plus your own hosting and accounts |
| Mobile app | Depends on the tier | Cheaper tiers often ship web-view apps, not native ones | A branded Android build ships in the base package |
| If you stop paying | The product can stop with the payments | Nothing changes, but nothing is maintained either | Nothing changes, because you hold the code |
Renting is not wrong for every buyer, and a monthly fee often bundles hosting that an owner must pay for separately. The fair comparison is a one-time software cost against a recurring fee, not a claim of a lower total cost of launch. Ownership only means more if you have the means to run what you own.
Own, Rent or Build: The Numbers That Are Stated
The figures we can stand behind, and nothing beyond them.
The in-house build timeline comes from our own platform's hub, and the monthly rent is a range we observed on the open market. No market size, growth rate or revenue outcome is published for this platform, so none is reproduced here.
Monetization Mistakes That Sink Trading Products
What undermines a fee strategy before it earns user trust or clears a regulator.
- Treating a configurable setting as if it were permission. A fee slab in the console proves nothing about whether you may charge it. Decide with your adviser first.
- Switching every line on at launch. Lead with what you are cleared to charge and what asks a new user for the least commitment.
- Leaving KYC and audit retention for launch week. Retrofitting compliance after users are active costs more, and it is the part that slows approvals.
- Pricing against a large incumbent's published rates instead of your own cost base and stage.
- Connecting all eight brokers when two or three cover your users. Each connection carries its own approval and upkeep.
- Promising outcomes to users or partners. Nothing here guarantees returns, and marketing copy should never suggest otherwise.
A live multi-broker deployment behind this model
"Eight broker connections behind one order screen is what our desk actually needed. The consolidated P&L ended the morning reconciliation spreadsheet." - HT, Head of Trading Operations, multi-broker trading platform, name withheld under NDA
Frequently Asked Questions
How does a trading platform business make money?
Can I charge brokerage if orders go to the user's own broker?
Which income line should I switch on first?
Does Miracuves take a share of what I earn?
Do you publish revenue projections or market sizing?
Is renting a hosted platform better than owning one?
Test the model against your own permissions
Bring your operating model, your broker set and your adviser's view. We will help you decide which of the six lines to activate first.
Explore the White Label Trading Platform
Ready to plan the platform behind this business model?
Six income lines you configure, eight broker connections behind one order layer, and the full source code handed over. This is the platform underneath the trading clones, and your permissions remain your own.
Talk to Us →Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by Zerodha, Blueberry Markets, or any other broker or trading service.
“White label trading platform” describes a category of product, not any one company. Brand names appear elsewhere on this site only to describe the kind of platform being built and the terms buyers search for.
The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from any third-party broker website or application.
All third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.
