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

Groww Clone Development Company: What to Check Before You Hire

The claims below are the original page's, and the numbers are specified in the listing. Its argument: on an investing platform the questions that matter are not about features - they are about what the schema decided before anyone wrote a screen, and about which controls a compliance reviewer will find missing. Below is how we work, the security items we name rather than bury, and the nine questions we would want answered if we were the ones buying.

Monorepo in your repository82 entity schema plus ERDMigrations and 15 seedersVAPT reference, OWASP mappedEleven documentation filesThe gap list, in writing
82Database entities - specified
15Seeders - specified
6Security items named, not buried
9Diligence questions to ask any provider
Compare

Agency vs Freelancer vs Omnistu

Three routes to the same platform, and where the original page argues each tends to fail once the second asset class arrives. The middle column is what to ask a freelance team; the right column is the proposed scope as specified in the listing.

What mattersWhat to ask a freelance teamThe proposed scope - specified
Time to liveAsk each bidder to estimate the work implied by the specification's scope - 82 entities, fifteen asset classes and the wealth layer - and explain their assumptionsAgreed in writing as part of your scoped quote
The second asset classAsk whether it becomes a parallel stack or a new entity behind a feature flagA new entity and a seeder behind a feature flag - specified
KYC and auditAsk what reviewable trail an operator approval leaves behind, and to read oneSeven states, checksummed documents, audit on every mutation - specified
The wealth layerAsk whether SIP, STP and SWP ship at launch or are quoted as a later phaseSIP, STP and SWP as first-class entities at launch - specified
Operator toolingAsk how operations staff work without a developer on callTen console pages with runtime feature flags - specified
Admin access modelAsk whether admin authentication is separate from customer authA separate admin authentication path entirely - specified
Stated limitationsAsk for the list of known gaps before purchasePublished before purchase, security gaps included
Price behaviourAsk whether the number moves once work has startedA fixed one-time quote - the recorded listing carries the number; it is agreed in writing before work starts

Good agencies exist and will build you a competent platform. What the table measures, in the original page's framing, is elapsed time, price certainty, and whether the compliance and wealth layers are in the schema from the start or promised for a phase that usually gets cut.

Due Diligence

Questions Worth Asking Any Provider

Put all nine to us and to whoever else is bidding. What a provider says about the order model tells you more than any portfolio, the original page argues.

01 ยท How does one order reach twelve instrument types?

If the answer is a table per product, adding an asset class means a parallel stack. Ask to see the discriminator and the keys, because that single decision determines what widening costs later.

02 ยท Where are brokerage and taxes calculated?

Charges computed on the client can be tampered with and cannot be defended in an audit. Ask them to show the server-side computation, then ask what happens if the client sends a different number.

03 ยท Is SIP one entity with a mode flag?

SIP, STP and SWP have genuinely different lifecycles. Collapsing them into one entity is the shortcut that makes the wealth layer impossible to extend, the original page argues, and it is invisible in a demo.

04 ยท What does an operator approval leave behind?

A log line saying an approval happened is not the artifact a compliance review examines. Ask whether the audit row carries before and after values, and ask to read one.

05 ยท Is admin authentication separate from customer auth?

If an operator signs in with the same token type as a customer and a role claim, a compromised customer credential is closer to operator access than anyone wants to admit, the original page argues.

06 ยท Can it trade live today, or does it expect a connector?

Ask this directly and expect a direct answer. A complete order engine and a live venue connection are different things, and conflating them is the most common overstatement in this category, the original page argues.

07 ยท What exactly do the price alerts evaluate?

"Price alerts" covers everything from two comparisons to a technical-indicator engine. Ask which conditions are evaluated in code rather than merely present in the schema.

08 ยท How long is data retained, and can you produce it?

Orders and payments held seven years is a design decision, not a setting. Ask what the retention model separates and whether restore has ever actually been tested.

09 ยท What is on your pre-launch security list?

Any provider whose list is empty either has not looked or is not telling you, the original page argues. Ours names the unimplemented two-factor endpoint first, and it sits further down this page.

All nine get answered in writing, the uncomfortable ones included. The Platform Trust section below puts the same answers on the record.

Process

The Six-Step Development Process

What we do, in the order we do it. Step timing is agreed in writing as part of your scoped quote; no day-counts are published on this page.

Step 1 ยท Catalog, licences and plan tiers

We confirm which of the fifteen asset classes go live first and which stay behind feature flags until licensing allows them, then the subscription tiers with their features and limits JSON. On a breadth product those two decisions are the product rather than configuration around it.

Step 2 ยท Branding and locales

Name, logo, colour scheme and theme tokens across the web application, the operator console and the React Native build, with your locales configured and both light and dark themes verified, since a financial product is used in both far more than a content product is.

Step 3 ยท Deploy and connect your accounts

The stack goes onto infrastructure you control through Docker Compose behind nginx, or PM2 if you prefer a process manager. Payment keys, SMTP, market data credentials and your Firebase project are connected, and the queue workers are enabled so systematic plans settle rather than sit.

Step 4 ยท Seed catalogs and stand the desk up

The 15 seeders populate the instrument catalogs for the classes you are launching, operator accounts are created against the RBAC roles, the KYC review desk is configured with its reject reasons, and the platform mode subsystem separates demo from production before the first incident rather than after it.

Step 5 ยท Walkthrough and handover

We run one investor end to end in front of your team: register, submit KYC, approve it in the console and read the audit row back, fund a wallet, place an order with the charge breakdown visible, watch the position land in the portfolio, create a SIP with a step-up and link a goal to it. Source, schema and documentation transfer.

Step 6 ยท Post-launch support

Launch guidance, priority bug fixes and updates follow the build, with durations and terms agreed in writing as part of your scoped quote. Broker venue connectors, the security hardening list and store publishing are scoped separately on their own schedule.

The first step carries more weight here than on most products, the original page argues. Which asset classes you commit to and how the plan tiers are drawn are the two decisions that are awkward to revisit once real users are subscribed against them.

Warning Signs

Red Flags That Mean Walk Away

Five answers that should end the conversation - the original page's list, kept in full.

"Yes, it trades live."

Asked without qualification, this is the answer to check hardest. A complete order engine still needs a venue connector, and a provider who does not volunteer that distinction is either not being careful or not being straight.

"We can add the other asset classes later."

Later means a parallel stack unless the order model was polymorphic from the start. Ask what a second asset class costs, and treat a vague answer as the real answer.

"The admin panel uses the same login."

A role claim on a customer token is not an access boundary. On a platform holding wallets and KYC documents, that is the shortcut with the largest downside, the original page argues.

"Charges are calculated in the app."

It is faster to build and impossible to defend, the original page argues. Every charge a user is shown must be computed on the server or the number means nothing in a dispute.

An estimate with no named exclusions

Software has edges, and financial software has licences on top of them. A number presented without either was never costed properly, the original page argues.

We are on the uncomfortable side of our own first flag in one respect and we would rather say it twice than once: the order engine here is complete, and it does not ship connected to a live venue.

Domain

What a Multi-Asset Platform Has to Get Right

The decisions that are cheap at the schema stage and expensive at every stage after it, the original page argues.

One order model, many instruments

Orders, holdings and watchlists carrying nullable per-asset foreign keys plus a type discriminator, reaching twelve instrument types. This is the decision that determines whether the fourth asset class is a week of work or a second platform, the original page argues, and it cannot be retrofitted cheaply.

Charges computed where they can be defended

Brokerage, STT, GST and transaction charges calculated server-side and shown in the ticket before confirmation. A user disputing a charge is a support conversation; a user disputing a charge you cannot reconstruct is a regulatory one.

A KYC lifecycle, not a status column

Seven states across individual, corporate and NRI records, six document types each with a SHA-256 checksum, a PEP flag, a risk category and a verification level, with operator approval or rejection stored with its reason. Identity proofing is asked about first now, not last, the original page argues.

An audit fabric with before and after

Every operator mutation writing the prior and resulting values, readable from a console page rather than reconstructed from application logs. This is the artifact a compliance review actually reads, the original page argues, and log lines are not a substitute for it.

A wealth layer at launch

SIP, STP and SWP as separate entities with step-up, top-up and auto-invest on dividend, goals linked to the plans funding them, and tax profit and loss with harvesting suggestions. The original page calls this the highest-LTV segment and the one most platforms reach last, if at all - its judgement, offered as a hypothesis to test.

Retention as a design decision

Orders, transactions and payments held seven years, audit logs archived then purged on the same horizon, sessions hard deleted after thirty idle days and notifications archived at ninety. The tables that grow without bound are exactly the ones a regulator later asks you to produce, the original page argues.

All six are in the recorded scope of the base build. Ask by email and we will point you at each one in the specification, including what an audit row from a KYC approval records.

Platform Trust

What We Have Not Done Yet

Six items, stated before a purchase rather than after one.

01 ยท 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. On a platform holding wallets and KYC documents this is the item we would schedule first, which is why it leads the list rather than sitting at the bottom of a handbook.

02 ยท No connection to a live venue

The order engine is complete, with four order types across five product types, a seven state lifecycle carrying partial fills and server-side charge computation. It expects fills from a connector it does not ship with, so live execution is an integration per venue. Paper trading works through the demo flag.

03 ยท Three controls are scoped, not shipped

Enforced multi-factor authentication for admin roles, SIEM integration and hard row-level multi-tenancy are named in the handbook as scoped work rather than delivered controls. If your review process asks for any of them, tell us by email and we will quote them before you buy rather than after.

04 ยท Alerts evaluate two conditions

Above and below, and only those. Volume spikes, RSI, moving-average crossovers and news keywords exist in the schema as a capability rather than as a shipped evaluator. We name it because "price alerts" is a phrase that routinely carries more than the code behind it does, the original page argues.

05 ยท Licensing is yours, not ours

Omnistu supplies platform software, not broker registration. Exchange membership, broker licensing, market data agreements and your KYC and AML obligations remain yours as the operator. What ships is the control fabric those licences are examined against, so a review has artifacts rather than assurances.

06 ยท What is built is real

Bcrypt hashing on a column that is not selectable, access and refresh tokens on separate secrets with rotation, RBAC with row-level user scoping, admin authentication held apart from the retail path, server-side payment verification before any wallet credit, SHA-256 checksums on KYC documents, validation rejecting unknown properties outright, parameterized queries throughout, and an audit row on every operator mutation. Verify each control in your own testing; the VAPT reference maps the platform against the OWASP Top 10 and marks its own gaps, and no certification and no vulnerability-free claim is made anywhere on this page.

Modelled

Modelled Reference Deployment

An authored scenario showing how the shipped platform is configured for an operator launching equities and mutual funds first, then widening. It is not a client engagement, and every figure in it is a property of the platform rather than a reported outcome.

Illustrative scenario ยท Multi-Asset Retail Investing Launch ยท not a client engagement ยท India, market modelled

82Database entities - specified
119Mobile screens - specified
15Asset classes - specified

How the shipped platform is configured for an operator launching equities and mutual funds first, then switching on US equities, alternatives and the systematic plan stack as licensing allows.

What the situation makes hard: running equities, mutual funds and US stocks as three separate stacks nobody can reconcile; a KYC desk improvised in scripts with no reviewable trail of who approved what; and systematic plans treated as a later phase, so the highest-value segment never activates.

What the configuration addresses: putting every asset class into one portfolio, one wallet and one KYC record; giving operations a review desk rather than a database client; and shipping the wealth layer at launch instead of quoting it as phase two.

What ships in the base build: one order model covering twelve instrument types through polymorphic keys; SIP, STP and SWP as first-class entities with step-up and top-up; a seven state KYC lifecycle with checksummed documents and an audit trail; a ten page operator console with demo and production mode switching; and portfolio analytics carrying CAGR, XIRR, a risk score and sector allocation.

This preview provides no verified company track record: it neither restates nor verifies founding history, delivery counts or client engagement figures published elsewhere on the original site, and no completed catalogue client build is claimed here. The scenario above is modelled: a configuration we can build, not a business we have launched.

FAQ

Frequently Asked Questions

Why publish your own security gaps?

Because on a financial platform an independent tester will find them, and finding them after payment is worse for both of us. The VAPT reference maps the build against the OWASP Top 10 and marks its own gaps deliberately. It also means the platform you plan a compliance review around is the real one rather than the marketing one.

Should we buy this or your Zerodha Clone?

The original page's answer: they solve different problems. The Zerodha Clone is about execution depth - multi-broker order routing, an algo engine, 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. Pick 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.

What exactly do I own at the end?

The monorepo, in full, the original page states: the Next.js 16 web application, the NestJS 11 core API, the React Native app, the operator console, the 82 entity schema with its migrations and 15 seeders, the deployment kit and the eleven documentation files - with no runtime licence, nothing counted per seat and no revenue share. Commercial terms are agreed in writing as part of your scoped quote; no revenue-share or no-fee promise is made on this page.

Will you close the security items for us?

Yes, as scoped work quoted before it starts, and we recommend booking it before you hold live client records. The two-factor enable endpoint is the first one and it is ordinary engineering rather than a rearchitecture, since the TOTP libraries are already present. Enforced admin multi-factor, SIEM integration and hard row-level multi-tenancy are each their own piece of work and we scope them individually.

Have you deployed this for a licensed broker?

This preview provides no verified company track record: it neither restates nor verifies founding history, delivery counts or client engagement figures published elsewhere on the original site, and no completed catalogue client build is claimed here. The reference deployment on this page is labelled modelled because it is authored rather than reported, and its numbers describe the build - a configuration we can build, not a business we have launched.

Can the operator work without a developer on call?

That is what the console is for, the original page answers. Ten pages cover the daily loop including the KYC review desk, order inspection with status override, the support ticket queue, the audit log viewer, runtime feature flags and system health. Subscription packaging is per-plan JSON, so moving a feature between tiers needs no release, and the platform mode subsystem switches between demo and production with readiness checks and a demo data reset.

Next Step

Ask us the hard questions first

Come with the nine questions above. You will get straight answers in writing, the unimplemented two-factor endpoint included, well before a contract enters the conversation. Email is fine - no calls required, no phone numbers collected.