For banks, NBFCs and AMCs
Distribution at institutional scale.
A multi-product wealth platform built for relationship hierarchies, institutional volumes and the controls your risk committee will ask about.
The problem
You have distribution. The platform behind it was built for someone smaller.
- 01
The tools your teams use were designed for a single-adviser practice, not a branch network.
- 02
Every product class beyond mutual funds is a separate system and a separate reconciliation.
- 03
Building in-house means a two-year programme and a permanent engineering team.
What matters at your scale
Business rules, not adjectives.
Volume is an operational question, not a marketing one.
Folio masters and transaction files load and reconcile at institutional volumes. Bring a real file to the evaluation and we will run it rather than describe it.
The hierarchy matches your organisation.
Group, family, client and account map onto regions, branches and relationship teams, so a branch head sees the branch and nobody sees more than their mandate.
Every product class on one book.
Mutual funds, AIF, PMS, bonds, deposits and insurance in one system, so a relationship manager answers a client question without reconciling three screens first.
Compliance controls are enforced, not advisory.
EUIN validity is enforced at order entry. KYC runs against the KRA inside onboarding. Sensitive actions write an immutable audit entry.
Your identity provider governs access.
Sign-in runs through your existing directory. Access ends when employment does, without a second system to remember.
The platform is available over API.
Embed wealth operations into the channel your customers already use, rather than sending them to a separate destination.
The modules your teams live in.
Set up
Get the firm, its people and its clients onto the system.
Transact
Move money and keep the book true.
Serve
Answer the client before they ask.
Grow
Get paid, and see where the practice is going.
What it connects to.
Seven categories
Order routing
Orders leave the platform and reach the exchange.
RTA feeds
Folio masters and transaction files land and reconcile.
KYC and KRA
Identity checked inside onboarding, not beside it.
Market data
NAVs, prices and corporate action announcements.
Payments and mandates
Collection and recurring authorisation.
Identity
Your existing sign-in, not another password.
Open API
REST endpoints and webhooks for your own flows.
Deployment
As a service, your cloud, or your data centre.
A service-oriented platform on Kubernetes, running wherever your data policy requires — the deployment choice does not change the platform.
Enterprise and white-labelAPI
Build it into what you already have.
The same operations the interface performs, available as REST endpoints with webhooks.
API and embeddedEvaluations start with your data, not our deck.
Bring a real folio master and a real transaction file. We would rather you watch the platform process your own book than watch a demo tenant behave perfectly.
- Mutual Funds
- AIF
- PMS
- Bonds
- Fixed Deposits
- Direct Equity
- NPS
- Insurance
- BSE StarMF
- CAMS
- KFintech
- AMFI
- CVL KRA
Every product class, one book
What institutional evaluators ask.
Can this sit behind our existing app?
Yes. The platform is available over REST with webhooks, so wealth operations can run inside the channel your customers already use. It can also run as a white-labelled portal under your brand if you would rather not build the front end.
Where would the data live?
That is your choice. The platform runs as a service, in your own cloud account under BYOC, or on-premises in your data centre. The deployment decision is yours to make against your own data policy.
How does this handle our relationship-manager hierarchy?
Through the same four-level hierarchy the whole platform is built on. Roles and position determine visibility, so the structure in the platform mirrors the structure in the business rather than approximating it.
You are a new company. Why should we take the risk?
It is a fair question and we would rather answer it than deflect it. We are new, and we do not have a twenty-five-year installed base to point at. What we can do is run your real data through the platform during evaluation, publish our security posture with dates rather than adjectives, and be specific about what is built and what is not. Judge us on what you can verify.
What does an institutional engagement cost?
It is quoted against scope rather than published, because institutional engagements differ too much for a list price to be meaningful. The model does not change: you pay for the platform, and never a share of what flows through it.
What are your certifications?
ISO 27001 is in audit, completing end-September 2026, with 27017 and 27018 following. The DPDP programme completes 30 September 2026. Current status, with dates, is on the security page — and nothing is claimed there before it is issued.