PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project

Engagement scope - proposed scope

Choosing a White Label Trading Platform Provider

This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product, a fixed bundle or a fixed price.

Scope areas for this kind of build

Software, Permission and Access: Who Holds What

Read this before anything else on the page. A platform vendor supplies software, and everything to the right of it is arranged by you.

Which of these your business actually needs depends on your market and operating model. That is a question for your legal counsel, and no software vendor can answer it for you.

Typical scoping questions

Who owns the source and the database?

  • Ask for the repository and the client records by name. A licence to run software is not ownership, and the gap shows the first time you want to change an order screen.

What happens the day you stop paying?

  • With a rental, the platform and often the client list go dark with the last invoice. With a platform you own, you carry on with a hosting bill. Get the answer in writing.

Whose name is on the broker agreements?

  • Yours. If the provider's own broker relationship carries your traders, your fees, your data and your exit are theirs to set.

Which entity holds the regulatory permission?

  • We supply software and no permission of any kind. If another provider says cover is included, ask for the entity's name, the scope in writing and what becomes of it when you leave.

Where does the risk and margin check run?

  • Before the order reaches the broker, or after? A check that happens second turns every rejection into a support ticket and a trust problem.

Can anyone edit the audit log?

  • Ask who changed a brokerage slab last month, and when. An append-only record answers that. An editable one is worth very little to an inspector.

Where is the list of what is not included?

  • A quote with no exclusions was not costed. Ours is on the features page, and it names the licences, memberships and scoped extras up front.

The Six-Step Delivery Process

Set brokerage, risk and roles

  • Brokerage slabs per segment and per broker, margin thresholds and console roles scoped so that only the right people can touch slabs, margin rules or client fund records.

Red Flags That Mean Walk Away

Use this list on us as well. In trading the expensive mistakes are regulatory, and they surface late.

What a White Label Trading Platform Has to Get Right

One adapter, many brokers

  • Trading screens must never learn a broker's quirks. Otherwise each new broker edits the order path, and each API change becomes a regression.

Risk and margin before routing

  • Validation, risk check and margin verification upstream of the broker. Stopping a bad order early costs less than explaining a rejected one.

Fills that reconcile

  • Each order followed from placement to fill across every broker. Without that, the consolidated portfolio is a guess and traders stop trusting it.

Market data that degrades gracefully

  • Five sources behind one interface, with a failover target of five seconds. A blank screen at the open loses users faster than any other outage.

Records that hold up

  • Fund transactions, trade records and audit logs are append-only, and roles fence off slabs, margin rules and client fund records. The record is the control.

A clear line between software and permission

  • A vendor's job ends at the software. Anything that implies otherwise is selling a promise it cannot keep on your behalf.

What Is Built In, and What Is Not Ours to Give

A platform that routes real orders answers to a higher bar than a consumer app. These are the limits, stated before the purchase and not after it.

Software, Not Permission

  • We supply no broking licence, no exchange membership and no clearing or custody relationship. Any registration your model needs is yours to obtain and hold.

No Liquidity, No Matching

  • Orders route to the broker each trader already holds an account with. We do not match orders, run a market or supply liquidity.

Approvals Stay in Your Name

  • Broker agreements, exchange data licences, KYC vendors, payment gateway and store accounts are contracted by you. We wire them in and hold none of them.

SEBI-Aligned, Not Approved

  • KYC review, retention rules and audit trails are built to align with SEBI expectations. That describes a design. It is not an approval, and it does not replace your own compliance sign-off.

Real Records, Real Roles

  • Fund transactions, trade records and audit logs are append-only. Access follows four server-enforced tiers, with TOTP two-factor sign-in, and every console action is scoped by role.

Larger Scope Is Scoped

  • Native iOS and Android apps, international markets, margin funding, auto-hedging, a strategy marketplace and further brokers are each priced against your plan before any work starts.

Illustrative multi-broker trading requirements

A proposed multi-broker operating scenario, not a verified client deployment, testimonial or performance result. Broker access, permissions, regulations and the actual implementation require independent checks.

Proposed multi-broker configuration

  • Assess a consolidated interface and the separately required broker API integrations, account permissions, maintenance and reconciliation. No already built connector or maintenance-free launch is established here.
  • The source names eight broker connections as a proposed scope option. Confirm the actual APIs, approvals, implementation, operating ownership and continuing maintenance before agreement.
  • Propose portfolio/P&L aggregation with explicit data freshness, currency, fee, position and reconciliation rules across approved accounts.
  • Determine applicable KYC, audit and retention requirements with qualified review, including SEBI requirements where relevant. No regulatory alignment, certification or day-one readiness is established here.

Choose on the answers, not the pitch

Omnistu is an independent software development project. 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.

Discuss this scope by message

Tell us your market and audience, and we will respond with a practical read on scope.

team@omnistu.com