PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project
Omnistu logoOmnistu
Groww Clone ยท Features ยท Proposed scope - specified

Groww Clone Features: Breadth Is the Product

The claims below are the original page's, and the numbers are specified in the listing. It says one identity carries one KYC record, one set of wallets and one portfolio across 15 asset classes, grouped below by who touches it, with every licence and third-party account named against the feature. Whether a record matches the description is the diligence to run on every vendor, ourselves included.

82 database entities - specified55 backend modules - specified119 mobile screens - specified167 API route handlers - specified
15Asset classes - specified
82Database entities - specified
13Calculators - specified
1Portfolio view - specified
By Role

Feature Set by Role

Six people use this platform differently. All six read the same 82 entity schema - specified.

01 ยท The New Investor

Registration, a KYC wizard with document upload, and a funded wallet before the first order. Then an academy with course progress tracking and 13 calculators on both web and mobile, so the education sits inside the product rather than on a separate blog - as the original page puts it - nobody reads.

02 ยท The Long-Term Investor

Instrument search spanning Indian equities, US symbols and funds, detail pages carrying NAV, expense ratio, exit load and benchmark, then holdings and a portfolio analytics view with CAGR, XIRR, a risk score and asset and sector allocation held as structured data rather than a rendered chart.

03 ยท The Active Trader

Four order types across five product types and four validity modes on five exchanges, with a seven state lifecycle carrying partial fills and preserved rejection reasons. Charges for brokerage, STT, GST and transaction fees are computed server-side and shown before confirmation, the original page states - verify payment behaviour in your own testing.

04 ยท The Systematic Investor

SIP, STP and SWP as three separate entities rather than variants of one, with daily through quarterly cadence, a step-up percentage, a top-up amount and auto-invest on dividend. Goals track a target amount and date and link to the plans funding them, and tax P&L splits realized gains short and long term with harvesting suggestions.

05 ยท The KYC Desk

A seven state lifecycle across individual, corporate and NRI records, six document types each carrying a SHA-256 checksum, a PEP flag, a risk category and a verification level. Operators approve or reject with a stored reason, and every decision writes an audit row with before and after values.

06 ยท The Operator

Ten console pages covering platform stats, an activity feed, user management, the KYC desk, order inspection with status override, the support ticket queue, analytics, the audit log viewer, runtime feature flags, security policies and system health, plus a mode subsystem that switches the whole deployment between demo and production.

Admin authentication is held apart from the retail JWT, so a compromised customer credential grants no operator access, the original page states - verify security behaviour in your own testing. The F&O terminal and the operator console are deliberately web-first; the mobile app carries 119 screens of everything else.

Compare

Clone vs Generic Script vs Building From Scratch

This contrast is the original page's framing, not a general verdict on scripts or agencies. The second column is the proposed scope here - specified; the third is the set of questions worth asking of any generic script you evaluate, including this one's competitors.

What decides itThe Omnistu proposed route - specifiedWhat to ask a generic script vendor
Time to a working platformAgreed in writing as part of your scoped quote - no day-count published hereHow long is it to a working platform, and who does the work?
Asset classes in the schemaFifteen, each with its own typed entityWhich asset classes are in the schema today, each with its own typed entity?
Adding the second asset classA new entity and a seeder, behind a feature flagWhat does adding a second asset class take - an entity, or a parallel stack?
Orders across instrumentsOne model, polymorphic keys, twelve instrument typesIs there one order model across instruments, or one table per product?
The wealth layerSIP, STP and SWP as first-class entities at launchAre systematic plans first-class entities at launch, or a phase two quote?
KYC and auditSeven states, checksummed documents, audit on every mutationIs there a reviewable audit trail with before and after values?
Operator consoleTen pages, separate auth, runtime feature flagsWhat can an operator do without a developer on call?
Source codeFull ownership, no runtime licence, no per-seat fee - as listed; whether yours works this way depends on the software agreement you signIs the source complete and unencrypted, with no runtime licence?

Groww itself is the reference for what this category looks like; it is not a product you can buy or self-host. The commercially useful comparison is the second column against the third, and against a custom build, which is covered on the Development Cost page.

End to End

How It Works, End to End

Every step below is enforced in the service layer rather than in the client, the original page states, which is what makes the sequence auditable afterwards - the auditability is the claim to verify in diligence.

Step 1 ยท Register and verify

Signup creates one user record that everything else hangs from. Passwords are hashed with bcrypt on a column that is not selectable, and access and refresh tokens are issued on separate secrets with rotation, so a leaked access token does not extend into a session - the original page's claim; verify in your own testing.

Step 2 ยท KYC submitted, then reviewed

The applicant uploads six document types, each stored with a SHA-256 checksum, and the record enters a seven state lifecycle typed for individual, corporate or NRI. An operator approves or rejects it with a reason in the console, and that decision writes an audit row a compliance officer can read back later.

Step 3 ยท Wallet funded

Four wallet types carry blocked and available balances alongside margin used and margin available. Payment is verified server-side before any wallet is credited, and refunds store the gateway response rather than a status flag, so a disputed transaction has evidence behind it - the original page's claim; verify payment behaviour in your own testing.

Step 4 ยท The first order

One order model reaches twelve instrument types through polymorphic keys plus a type discriminator. Brokerage, STT, GST and transaction charges are computed on the server and shown in the ticket before confirmation, and the order moves through seven states carrying partial fills and any rejection reason.

Step 5 ยท The portfolio forms

The filled order becomes a holding, and the holding appears in the same allocation view as every other asset class the user owns. Multiple portfolios per user are supported, each carrying CAGR, XIRR, a risk score, day change, holdings count and asset and sector allocation as structured JSON.

Step 6 ยท Systematic plans run

A SIP is created with a cadence, a step-up percentage and a top-up amount, and a goal is linked to the plan funding it. Installments settle through the Bull queue path rather than in the request cycle, which is why enabling the queue workers is part of deployment rather than an optional extra.

Step 7 ยท Tax at the other end

Realized profit and loss splits short and long term, a harvesting suggestion engine runs against it, and dividends and corporate actions are tracked so holdings reconciliation stays correct across the year. This is the surface most platforms leave until an accountant asks for it, the original page says.

The same sequence runs on web and on the React Native app against one API, and the platform mode subsystem lets an operator run the whole flow in demo mode without touching production data.

Justified

Every Feature Earns Its Place

The reasoning in this table is the original page's engineering justification for each module - treat it as the design rationale to probe in diligence, not as a guarantee about outcomes.

ModuleWhy it is in the base build - the original page's reasoning
Polymorphic instrument keysOrders, holdings and watchlists carry nullable per-asset foreign keys plus a type discriminator, so a new asset class is an entity and a seeder rather than a second stack to reconcile.
Server-side charge computationThe original page argues brokerage, STT and GST calculated on the client can be tampered with and cannot be defended in an audit, and that computing them server-side is the difference between a demo and a product.
SIP, STP and SWP as separate entitiesThey have genuinely different lifecycles, the original page argues; modelling them as one entity with a mode flag is the shortcut that makes the wealth layer hard to extend later.
Seven state KYC with checksumsIdentity proofing and record retention are expensive to retrofit into a schema that was not designed for them, the original page argues.
Audit row on every mutationBefore and after values on operator actions are what the original page says a compliance review actually examines; a log line saying an approval happened is not the same artifact.
Runtime feature flagsLaunching with two asset classes and widening as licensing allows only works if switching one on is a toggle rather than a release, the original page argues.
Per-plan features JSONFive plans across four billing cycles gated by JSON means moving a feature between tiers is configuration, so packaging can be tested without engineering time.
Queue-backed settlementSystematic plan installments and news ingestion are write bursts; running them through Bull producers keeps them from contending with interactive traffic at market open, the original page argues.

Underneath sit 15 database seeders for catalogs and demo data, 11 queue producer services and 5 scheduled jobs including the market data provider refresh - specified.

Stack

The Technology Behind the Features

One language end to end, on frameworks any team can hire for, with nothing proprietary to unwind - the original page's claim; the stack list below is specified.

Web application

Next.js 16 with React 19, Tailwind and Radix across 41 dashboard route domains and more than 100 pages, 53 component domains including a motion library, TanStack Query for server state and Zustand for client state, delivered as a PWA with an offline page, i18n locales and both dark and light themes.

API layer

A NestJS 11 core of 55 modules, 52 of them domain modules, behind 167 backend-for-frontend handlers with Zod validation. Passport JWT with guards for tokens, roles and API keys, Swagger and OpenAPI decorators throughout, and an admin cookie session held apart from the retail JWT.

Database

PostgreSQL under TypeORM 0.3 with 82 entities carrying jsonb metadata extension columns, polymorphic instrument keys on orders, holdings and watchlists, indexed hot paths on user and status, symbol and status and creation date, plus a migration runner and 15 seeders.

Mobile application

React Native 0.73 with Expo Router: 119 screens plus 15 router routes, biometric unlock, MMKV secure storage, Firebase analytics and messaging, NetInfo offline detection, EAS build profiles for both platforms and home-screen widgets. It is a real application, not a web wrapper, the original page states - verify on a real device before go-live.

Realtime and async

A Socket.io gateway fanning out market ticks, order updates and notifications, with Bull and Redis behind 11 queue producer services gated by an environment flag, and 5 scheduled jobs. Systematic plan installments settle through the queue path rather than in the request cycle.

Deployment and observability

Docker Compose for development and production, an nginx reverse proxy, a PM2 process configuration, four GitHub Actions workflows and a validation script, a Prometheus scrape configuration with four Grafana dashboards, health endpoints and a synthetic monitor, plus deploy, rollback and backup scripts.

Every integration sits behind a service interface rather than inside a domain module, the original page states. Razorpay and Stripe gateways, two market data providers and an FCM push provider all ship against those interfaces, which the original page says makes adding a broker venue an adapter rather than a rewrite - the integration path is scoped work to validate.

Honest Readiness

What Is Not Included in the Base Package

Named here rather than discovered after the invoice.

01 ยท No connection to a live venue

The order engine is complete and the lifecycle carries a broker reference and an exchange order id, expecting fills from a connector, the original page states. What is not included is the connector itself, so wiring an actual broker is an integration per venue. Paper trading works out of the box through the demo flag, the original page says, which is also what it argues makes the evaluation safe to hand a prospect.

02 ยท Market data licensing is yours

Provider adapters ship against a service interface, but exchange and vendor data licensing is a commercial arrangement between you and the vendor. The same applies to US equities: the catalog, quotes, charts and a dedicated portfolio type are built, the original page states, and live US execution is an integration rather than a shipped connection.

03 ยท Price alerts evaluate two conditions

Above and below, and only those. The richer condition set in the schema covering volume spikes, RSI, moving-average crossovers and news keywords is a schema capability rather than a shipped evaluator, and building it is scoped work. The original page says it calls this out because the words "price alerts" usually carry more than they should.

04 ยท Two-factor is not enabled

The TOTP libraries ship but the enable endpoint is not implemented, so two-factor authentication is not available to users as delivered. Enforced multi-factor for admin roles, SIEM integration and hard row-level multi-tenancy are likewise scoped rather than shipped. All four are named in the security handbook, the original page states.

05 ยท Licensing is not software

Omnistu supplies platform software, not broker registration. Exchange membership, broker licensing and your KYC and AML obligations remain yours as the operator. What the platform provides is the control fabric those licences are examined against, so a review has artifacts to look at rather than a promise - confirm your own regulatory requirements with qualified counsel.

06 ยท What is built is real

Specified in the listing: 82 entities, 55 backend modules, 167 route handlers, 119 mobile screens, fifteen asset classes with their own typed entities, four order types across five product types, a seven state KYC lifecycle, four wallet types, thirteen calculators, five subscription plans across four billing cycles, and a ten page operator console with an audit row on every mutation.

Production payment keys, SMTP, a Firebase project for push and the queue workers all need your own accounts or configuration before launch day. The full list sits on the Development Company page.

FAQ

Frequently Asked Questions

How is this different from your Zerodha Clone?

They are genuinely different platforms rather than two presentations of one codebase, the original page states. The Zerodha Clone is about execution depth: multi-broker order routing, an algo engine and consolidated profit and loss across broker connections, built for trading-first businesses and prop desks. This one is about breadth: fifteen asset classes in one portfolio plus the wealth layer of systematic plans, goals and tax tooling. The original page suggests picking that one if your differentiator is how a trade gets executed, and this one if it is how much of a customer you can hold.

Which asset classes are actually included?

Indian equities on NSE and BSE, US equities on NYSE and NASDAQ, mutual funds, ETFs, index funds, IPOs with grey market premium and allotment, futures and options, intraday and the margin trading facility, commodities on MCX, currency pairs, bonds, fixed deposits, digital gold and SGBs, REITs and P2P. Each has its own entity with typed fields, and orders, holdings and watchlists reach all of them through polymorphic keys - the original page's enumeration; verify coverage against your own target markets.

Can it trade live, or is it a demo?

The order engine is complete, the original page states: four order types across five product types and four validity modes on five exchanges, a seven state lifecycle with partial fills and preserved rejection reasons, and server-side charge computation. What is not included is the connection to a live venue. The lifecycle carries a broker reference and an exchange order id and expects fills from a connector, so wiring a broker is an integration per venue rather than a rearchitecture - the original page's claim; validate the integration path before relying on it.

Does it handle SIPs, goals and tax properly?

The original page answers yes, with specifics: SIP, STP and SWP are three separate entities carrying daily through quarterly frequencies, step-up percentages, top-up amounts and auto-invest on dividend, with a full scheduled through completed lifecycle. Goals track a target amount and date against progress and link to the plans funding them. Tax gives realized profit and loss with short and long term splits plus harvesting suggestions, and dividends and corporate actions are tracked so reconciliation stays correct. Treat the specifics as the checklist to verify in diligence.

What does the mobile app actually cover?

A React Native application of 119 screens plus 15 Expo Router routes, not a web wrapper, the original page states. It carries auth with biometric unlock, the dashboard, market and instrument screens, orders, holdings with analytics, watchlist, wallet, KYC status, alerts, news, IPO, SIP creation, all thirteen calculators, the alternatives stack, research screens and market intelligence. Home-screen widgets, Firebase messaging, MMKV storage and offline detection ship with it. The F&O terminal and the admin console are deliberately web-first. Verify on real devices before go-live.

What can the operator do without a developer?

Ten console pages cover the daily loop: platform stats and an activity feed, user management with status changes, the KYC review desk with approve and reject reasons, order inspection and status override, the support ticket queue, analytics, the audit log viewer, feature flags, security policies and system health. On top sits the platform mode subsystem, which switches the deployment between demo and production with mode history, readiness checks and a demo data reset - the original page's enumeration.

Next Step

Trace the breadth, not the feature reel

The original page suggests an evaluation path: search an instrument, add it to a watchlist, place an order with the charges visible, then open the portfolio and watch the same position land in the allocation view alongside every other asset class. Ask us to walk that path with the spec in writing - and ask every vendor the same. Email is fine - no calls required, no phone numbers collected.