Quorumcell

Attested clean rooms where lenders and insurers pool data without sharing it

Enterprises

TL;DR Quorumcell rents secure enclaves from the big clouds and packages them as clean rooms. A bank, an NBFC and an insurer can then run an agreed analysis on their combined customer data while none of them, nor the cloud, sees the others' raw records. Financial firms pay per project plus a platform fee.

The problem

Indian lenders and insurers want to learn from each other's data - overlap in customers, fraud rings that span institutions, co-lending risk. Sending raw files to a partner is exactly what the DPDP Act makes risky. Every data fiduciary must take reasonable security safeguards to prevent breaches[1], and failing to do so carries the highest penalty in the law, up to ₹250 crore[2].

Consent-based sharing already runs at scale. The Account Aggregator network counts over 2,880 million enabled accounts and 1,076 financial information users[3]. That system moves one customer's data with consent. It does not let two institutions compute on pooled data while keeping it private from each other.

The idea

What it does, in regulatory terms: a technology provider acting as data processor for its clients. It is not an Account Aggregator, credit bureau or lender, and holds no RBI licence. Each client remains the data fiduciary for its own records.

The seed asked for remotely attestable, hardware-isolated computing. Building that hardware is a chipmaker's job, and the clouds already rent it. One big cloud's confidential service runs on chipmakers' secure-enclave machines and releases data only to workloads that pass attestation[4]. So I reframed the idea as the layer on top.

Here's how it works - Quorumcell gives each party a key it controls, and the parties agree on one piece of code, say a fraud-overlap count or a joint model. The enclave proves to every party's key service that it is running exactly that code, and only then are the keys released. Outputs are aggregated and checked for leaks before anyone sees them. India's DEPA training design describes the same pattern, with attestation gating key release[5].

Who pays

The users are risk, fraud and analytics teams. The payer is the head of risk or data at a bank, NBFC or insurer, often with the CISO's sign-off. There's no public price for clean-room projects in India. My assumption is ₹15–40 lakh per project for the first deals, moving to annual platform fees once trust builds.

Why now

The DPDP Rules were notified in November 2025[2], which raises the cost of careless sharing. RBI's IT governance directions, in force since April 2024, tighten oversight of outsourced technology at banks and larger NBFCs[6]. And rentable confidential VMs and GPUs now exist on the major clouds[4][7].

Market signal

There is no public figure for confidential computing or data clean-room spending in India. The closest signal is the Account Aggregator network, with 1,076 financial information users and over 295 million data shares a month as of June 2026[3]. Those firms already pay to receive data. How many also want to compute jointly? Nobody knows yet, so treat it as adjacent and not your market.

Who's already doing this

The big cloud providers sell the underlying confidential compute[4][7]. One US vendor sells confidential AI with hardware attestation and key release, aimed at global enterprises[8]. The iSPIRT-linked DEPA effort publishes an open design for confidential clean rooms, but it isn't a commercial service[5].

I found no Indian company packaging this for lender and insurer use cases.

How hard is it?

Difficulty Hard (56/100)
Starting capital ₹2–3.8 Cr
Time to launch 12–18 months

The cryptography is rented, so the hardest parts are elsewhere. Banks' legal and security teams will spend months on each contract. Proving that outputs can't leak individual records takes careful privacy engineering. And getting three institutions to agree on one analysis is slower than building it, by a long way.

Licences and approvals

Quorumcell needs no RBI licence, as long as it stays a technology provider and never scores individuals for lending itself.

  • DPDP Act section 8. Clients are data fiduciaries and you are their processor, bound to reasonable security safeguards from the first project[1][2].
  • RBI IT governance directions. Bank and NBFC clients review you as a vendor against these before they sign[6].
  • Account Aggregator consent. If clients bring data received through AAs, confirm the consent purpose covers joint analysis before you accept it[3].
  • Staying outside credit bureau and lender rules depends on how you structure outputs. Confirm with a regulatory lawyer before launch [Requires validation].
  • Company registration and GST as for any technology business.

Building this outside India? The categories above usually have a local equivalent, so check with your own regulator.

How AI can power this business

  • Joint fraud models. Lenders can train a fraud or mule-account model on pooled data inside the enclave, which none of them could build alone.
  • Output leak checks. Automated checks on every result catch outputs small enough to identify a customer before anyone sees them.
  • Workload review. A model can read the agreed analysis code and flag anything that writes raw rows out, so each party's reviewer starts with a short list.
  • Vendor questionnaires. Drafting answers to the long bank security reviews from your past responses saves weeks per deal.

AI here must never make a lending or claims decision about a person. Results go back to each client as aggregates, and they decide.

Want to work out the AI layer for Quorumcell? Talk to Yash →

Biggest risks

Here's what can go south -

  • Sales cycles. Each deal needs approval from several regulated firms at once, and one veto stalls it.
  • Cloud bundling. Hyperscalers may ship a ready clean room that is good enough.
  • Leaky outputs. A badly designed query could reveal individuals and destroy trust overnight.

Our take

I'd back a founder with security engineering depth and existing relationships in bank risk teams. If you're expecting quick SaaS revenue then walk away now. Before raising money, get one bank and one insurer to sign a paid pilot on a single fraud question.

Questions founders ask

Plan for roughly ₹2–3.8 Cr, mostly on a strong engineering team, cloud costs and long pilots with banks and insurers.

Do I need an RBI licence to run a data clean room for lenders?

Not if you stay a technology provider and processor. Clients remain responsible for their data, and you meet DPDP safeguards and their RBI vendor reviews. Confirm your structure with a lawyer.

Can I start a confidential clean room business in another country?

Yes, since the confidential computing machines are rented from global clouds. Check local data protection law and what your financial regulator says about sharing customer data.

Download the kit

The free Quorumcell validation kit has the line-by-line capital breakdown, the effort scoring, the regulatory and data-protection checklist, a 14-day validation sprint with pass/fail targets, a 90-day launch plan, 10 interview questions for risk heads and CISOs, and 5 assumptions to test. Download the kit →

Talk to Yash

Thinking about building Quorumcell or something close to it? The make-or-break work is getting two regulated firms to agree on one joint question and sign the same contract. If you need a hand, you know where to find me. Talk to Yash →

Sources

  1. DPDPA.com, "Section 8: General obligations of Data Fiduciary", accessed 2026-10-21. https://www.dpdpa.com/dpdpa2023/chapter-2/section8.html
  2. PIB, "DPDP Rules, 2025 notified" (backgrounder), 2025-11-17. https://static.pib.gov.in/WriteReadData/specificdocs/documents/2025/nov/doc20251117695301.pdf
  3. Sahamati, official site (Account Aggregator ecosystem figures), accessed 2026-10-21. https://sahamati.org.in/
  4. Google Cloud, "Confidential Space overview", accessed 2026-10-21. https://docs.cloud.google.com/confidential-computing/confidential-space/docs/confidential-space-overview
  5. DEPA, "DEPA training: architecture", accessed 2026-10-21. https://depa.world/training/architecture
  6. RBI, "Master Direction on Information Technology Governance, Risk, Controls and Assurance Practices", 2023-11-07. https://www.rbi.org.in/Scripts/BS_ViewMasDirections.aspx?id=12562
  7. Microsoft Learn, "Azure confidential computing overview", accessed 2026-10-21. https://learn.microsoft.com/en-us/azure/confidential-computing/overview
  8. Fortanix, "Confidential AI" (official site), accessed 2026-10-21. https://www.fortanix.com/platform/confidential-ai

For illustration only. Names are fictional and ideas hypothetical; sourced facts are real but may be out of date. Nothing here is legal, financial or professional advice, and Yash Khatri is not personally liable for any use of it. Read the full disclaimer.

Reviews

No reviews yet