Enterprise and white-label
Your brand, our platform.
A full multi-product wealth platform running under your name — deployed as a service, in your own cloud, or inside your data centre.
The problem
You have the distribution. You do not have the platform behind it.
- 01
Building it in-house is a two-year programme and a permanent engineering team.
- 02
The vendors that can do it want a nine-month implementation and a bank-sized licence.
- 03
Anything you buy off the shelf puts someone else’s brand in front of your clients.
What white-label means here
Concretely, not as an adjective.
Your brand, your subdomain, your client portal.
Investors see your institution throughout — the portal, the statements, the emails. Finvica does not appear in front of your clients.
One tenant per institution, isolated.
Your data, your configuration and your users are separated from every other tenant on the platform rather than partitioned by a query filter.
Your identity provider is the source of truth.
Sign-in runs through your existing directory, so joiners and leavers are handled where you already handle them and access ends when employment does.
The four-level hierarchy maps to your org.
Group, family, client and account map onto branches, relationship teams and books — so reporting lines in the platform match reporting lines in the business.
Every sensitive action writes an immutable audit entry.
Who did what, and when, in a trail designed to be produced for a regulator rather than read by an engineer.
The platform is available over API.
The same operations the interface performs are available as REST endpoints with webhooks, so you can build your own flows on top rather than around.
Deployment
Three ways to run it, and you choose.
As a service. We run the platform and you use it. The fastest route to live, and the right one for most institutions.
BYOC — in your own cloud. The platform deploys into your cloud account. Data resides on infrastructure you own, under your existing cloud governance, while we remain responsible for the software.
On-premises — in your data centre. For institutions whose data policy does not permit a third-party cloud at all, the platform runs inside your own estate.
It is a service-oriented platform on Kubernetes, so the same system runs in all three. The deployment decision changes where it runs and who operates it — not what it can do, and not which modules you get.
The modules an institution asks about first.
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.
Enterprise engagements start with a conversation.
White-label and enterprise engagements are scoped rather than configured. Tell us what you are building and who it serves, and we will tell you what it takes — including whether we are the wrong answer.
- Mutual Funds
- AIF
- PMS
- Bonds
- Fixed Deposits
- Direct Equity
- NPS
- Insurance
- BSE StarMF
- CAMS
- KFintech
- AMFI
- CVL KRA
Every product class, one book
What institutions ask.
Can we run this in our own cloud account?
Yes. BYOC deploys the platform into your cloud account, so the data never leaves infrastructure you own and control, and your existing cloud governance applies unchanged.
Can we run it in our own data centre?
Yes. Finvica runs on-premises as well as in cloud environments, which matters for institutions whose data policy does not permit a third-party cloud regardless of region.
Does the deployment choice change the product?
No. It is a service-oriented platform on Kubernetes, and the same platform runs in each environment. Deployment changes where it runs and who operates it, not what it does.
What does an enterprise licence cost?
It is quoted, not published — enterprise engagements differ too much for a list price to mean anything. What we can tell you in advance is the shape: you pay for the platform, never a share of what flows through it.