Blueberry Markets Clone - Features
Blueberry Markets Clone Features: What a Brokerage Platform Actually Includes
A brokerage portal is a client lifecycle wrapped around a trading terminal it does not own. The supplied specification is unusually direct about where the platform's responsibility begins and ends - including the two integrations it does not ship. The master sections below preserve that substance in full. Everything here is proposed scope: this preview does not implement or verify it, counts are inventory recorded in the supplied specification, and nothing is priced until your scope is quoted in writing.
By Role: Six Logins, Each in Its Own Scope
Access control is enforced per area rather than by hiding menu items, which is the difference that matters when a compliance officer and a support agent share a platform.
Client
Everything a trader touches outside the terminal itself.
- Registration, onboarding and tiered KYC submission
- Deposits, withdrawals and internal transfers
- Account management across live and demo accounts
- Prop evaluation challenges and funded-account progression
- Document upload, verification status and support tickets
- Android client via Capacitor on the same API surface
Partner & IB
The introducer network: a distribution channel this platform supports with tiered rebates and sub-IB attribution.
- Tiered rebates calculated on client trading volume
- Sub-IB hierarchies with multi-level attribution
- Affiliate CPA tracking alongside volume rebates
- Commission schedules configurable per partner
- Partner payout requests with an approval path
- Referral links, client attribution and partner reporting
Operator
Admin, support, compliance and finance, each scoped separately.
- Admin console across eight navigation sections - the supplied specification records fifty pages and more than thirty-four operational areas
- Clients, trading, payments, KYC, risk, CRM, partners and system settings
- Compliance queues, document review and AML workflow
- Finance views for funding, reconciliation and payouts
- Support ticketing with client context attached
- Demo and live runtime switch for training and rollout
The demo and live runtime switch is worth calling out. The whole platform runs on simulated data for demonstrations and staff training, then flips to live vendor routes once your integrations are configured. An operator can train a full operations team on it before a single real deposit exists.
Established Broker vs This Build vs From Scratch
Where the proposed platform matches an established broker's operational stack, and what the same capability costs in effort if you build it yourself. Pricing is deliberately not on this page - the cost shape lives on the development cost page.
| Capability | Established broker | This build, as proposed | From scratch |
|---|---|---|---|
| Trading terminal | MT4 / MT5 | MT4 / MT5, unchanged | Licensed separately either way |
| Client portal | Mature | Onboarding, funding, accounts, documents | A full phase of work |
| KYC and AML | Vendor integrated | Tiered KYC with queues and document review | A vendor integration plus its own workflow build |
| IB programme | Core to distribution | Tiered rebates, sub-IB hierarchies, CPA, payouts | Rebate attribution alone is a project |
| Prop desk | Separate product if offered | Challenges, drawdown checks, funded progression | A second product build of its own |
| Operator scoping | Role based | Six consoles, access enforced per area | Scoped separately as the build is planned |
| Admin depth | Built up over years of operation | Fifty pages, thirty-four-plus operational areas, as recorded | An ongoing build track of its own |
| Multi-language | Per market | Configured before launch, including right-to-left | A writing project of its own within the build |
| Training environment | Staging | Built-in demo runtime on simulated data | Separate environment to build and maintain |
| Time to live | n/a | A fixed deployment window, confirmed in your written quote | A multi-quarter programme at market rates |
The Technology Behind the Features
The supplied specification records Next.js and React in TypeScript on PostgreSQL, with Capacitor producing the Android client from the same codebase and Stripe handling card rails. It records a schema of 93 tables across twelve business domains and a REST surface of 213 handlers spanning portal, admin, partner and webhook routes. Nothing proprietary sits underneath it: standard PostgreSQL and a mainstream stack mean there is no vendor format to unwind if you later move or extend the platform.
How It Works, End to End
The path from first visit to a screened withdrawal, and where the platform's responsibility begins and ends.
1. Acquisition and education
The supplied specification records an organic surface of 132 public pages and 93 education articles across academy, learn and market analysis - a content asset that otherwise becomes a long writing project after launch.
2. Registration and verification
Signup opens a client record and a wallet, then routes documents into the operator verification queue where a decision unlocks trading. Nothing is tradeable before that decision exists.
3. Funding and wallets
Deposits credit the wallet through provider webhooks, with internal transfers and conversion between currencies handled inside the platform rather than pushed onto the client.
4. Trading accounts
The platform provisions and links MT4 and MT5 accounts, then reports history and performance back into the portal. Execution itself stays in the terminal - the portal is the client relationship, not the matching engine.
5. Prop and partner economics
Two revenue engines run alongside the core brokerage - evaluation challenges on one side, introducer rebates on the other. Both are configurable and both earn before a trader is profitable.
6. Compliance and payout
Every withdrawal passes screening before it reaches finance, and every operator action lands in the audit log a regulator can read. In this category that log is the product as much as the portal is.
Every Feature Earns Its Place
A feature list tells you what exists. This tells you what each one is worth to a brokerage operator, and what it costs you not to have it.
| Capability | What it actually does | Why it matters commercially |
|---|---|---|
| 132 public pages, 93 education articles | An organic acquisition surface shipped with the platform | Client acquisition cost is a cost to model for your target market. This is the alternative to buying every visitor |
| Verification queue with decisions | Documents routed to operators, a decision unlocking trading | No client trades before a recorded decision exists |
| Wallet with internal transfer and conversion | Funding, movement and currency conversion inside the platform | Clients who can move money without a support ticket depend less on support for routine funding operations |
| Prop evaluation challenges | Priced challenges at three account sizes with configurable pricing | Revenue before a trader is ever funded, and a line that can activate before liquidity connectivity finishes |
| Configurable profit split | Funded-trader share set per package | Your prop economics are an operator decision rather than a hard-coded assumption you inherit |
| Tiered IB and affiliate rebates | Volume tiers, sub-IB attribution and affiliate CPA | An IB programme can help you track referred clients and pay introducer commissions accurately. Sub-IB attribution is what lets a network build under one partner |
| Operator-set funding fees | Deposit pass-through and withdrawal fees as policy per method | Payment costs vary by method and market. Hard-coded fees mean absorbing that variance yourself |
| Withdrawal screening before finance | Every payout passes a screening step before release | The control that stands between you and a fraud loss; ask your payment provider which screening records they require |
| Regulator-readable audit log | Every operator action recorded and readable | The proposed audit log keeps operator-action records you can present when the platform is reviewed; verify which records are required with a qualified adviser in your jurisdiction and with your payment provider |
What Is Not Included in the Base Package
Two items at the top of this list are more significant than anything else on the page, and you should read them before evaluating anything else. We would rather lose a deal here than after purchase.
Reported gap: live MT4 and MT5 connectivity
The supplied specification records MT4 and MT5 as registry entries at stub level today. Live account provisioning, position sync and trade reconciliation need a bridge and liquidity connectivity - required scope, quoted before work starts, not work already performed.
Reported gap: live market data
Watchlists and instrument catalogues run on simulated prices in demo mode. Real-time pricing requires a market data contract wired into the platform - a commercial relationship as much as a technical one.
Live money movement
The supplied specification records Stripe, Skrill and Neteller webhook handlers in the codebase. Moving real money requires your own merchant contracts, credentials and provider approval for your jurisdiction and category.
KYC and AML vendor connection
The verification queue, risk scoring and screening workflow are described as complete. Automated identity and sanctions checking requires connecting a vendor, and their per-check fees are yours.
Regulatory reporting formats
The audit and compliance data model supports it. The specific formats your regulator expects are built per jurisdiction as a scoped module rather than shipped generically.
iOS application
Android ships with the base product. The same Capacitor build produces iOS, making it an additive step rather than a second codebase - but it is an add-on.
External marketing automation
Segments, campaigns and a journey engine ship in-product. Connecting an external marketing platform or a data warehouse is an integration.
Enterprise controls
Single sign-on for operator accounts, custom roles beyond the six shipped, extended retention policy and data residency are scoped against your procurement requirements.
To be direct about what the first two items mean: what is proposed is a complete brokerage portal - client lifecycle, verification, wallets, prop engine, partner economics and compliance. What it is not yet is a live trading venue. Bridging to MT4 or MT5 and contracting market data are the two steps between this platform and taking real orders, and both are as much commercial work as technical.
Frequently Asked Questions
Does this replace MT4 or MT5?
No, and deliberately so. Order execution stays in MT4 and MT5, where your traders already are and where liquidity connectivity already works. This platform is the operational layer around the terminal: onboarding, funding, compliance, partner payouts and the back office your team lives in.
What does the IB programme actually calculate?
Tiered rebates on client trading volume, with sub-IB hierarchies so multi-level introducer structures attribute correctly. Affiliate CPA tracking runs alongside volume rebates, commission schedules are configurable per partner, and payout requests follow an approval path rather than being paid by spreadsheet.
Is the prop desk a separate product?
It is proposed as included. Priced evaluation challenges, daily drawdown checks, pass and fail state machines, funded-account progression and payout handling all ship as part of the platform, sharing the same client records and money movement as the brokerage side.
What is the demo runtime mode for?
Running the entire platform on simulated data. Operators would use it to train staff and record partner walkthroughs before any live integration exists, then flip a switch to live vendor routes once the payment gateway and KYC vendor are configured.
Can this take live trades out of the box?
No. The supplied specification records MT4 and MT5 as registry entries at stub level today, and watchlists run on simulated prices in demo mode. What is proposed is a complete brokerage portal - client lifecycle, verification, wallets, prop challenges, partner economics and compliance. Bridging to a live terminal and contracting market data are the two steps between that and taking real orders, and we would rather state it here than after purchase.
What does the 132-page public surface actually give me?
An organic acquisition asset proposed with the platform - the supplied specification records 132 public pages and 93 education articles across academy, learn and market analysis. Client acquisition cost is a cost to model for your target market; building this content after launch is a separate project of its own.
Independence and third-party names
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Blueberry Markets. "Blueberry Markets clone" is used descriptively - it is how the software industry refers to building a platform with similar functionality, and how buyers search for it. Blueberry Markets, MetaTrader and all other third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.
Discuss your scope by message
Tell us your jurisdiction, which consoles your team needs, and whether the prop desk is part of your launch offer. We reply by email with a scoped proposal - no calls required, no phone numbers collected.
