RBI FREE-AI
Use this path for banks, NBFCs, payment companies, cooperative banks, and shared platforms supporting RBI-regulated entities.
Open the RBI guideIndia
One AI platform, several Indian regulatory contexts.
Orient banking, payments, securities, and shared platform teams across RBI FREE-AI, SEBI AI/ML responsibilities, and Indian data-protection obligations.
Start with the regulated activity
RBI and SEBI do not regulate the same institutions or workflows. The separate guides exist because a bank's system inventory and board-governance questions differ from a securities intermediary's reporting, client-data, output-responsibility, and market-integrity questions.
SEBI AI/ML governance
Use this path for brokers, depositories, exchanges, clearing corporations, mutual funds, advisers, research analysts, and other SEBI-regulated intermediaries.
Open the SEBI guideDPDP context
Use a parallel data-governance workstream for purpose, notice, consent or other lawful processing, data-principal rights, security safeguards, and breach response.
Review the technical DPDP contextCommon controls across Indian financial services
| Shared concern | Practical platform control | AxonFlow contribution |
|---|---|---|
| Accountability | Name system owners, approved purpose, model or vendor, risk tier, and accountable business function. | Enterprise registries and framework workflow records complement your source-of-truth inventory. |
| Indian personal data | Detect and govern identifiers such as PAN and Aadhaar before external model or tool access. | Regional PII policies and governed request records provide a technical enforcement foundation. |
| Human responsibility | Require review for material customer, credit, trading, advisory, or payment actions. | HITL approval queues record reviewer, outcome, time, and decision context. |
| Output and incident risk | Track validation findings, policy violations, incidents, and emergency interventions. | Licensed RBI and SEBI workflows plus circuit-breaker controls support the operational record. |
| Audit and reporting | Correlate AI decisions with downstream transactions and preserve evidence for internal or regulatory review. | Audit records and framework-oriented exports support reconstruction; downstream logs remain essential. |
Why India has a country hub and regulator pages
The overview serves shared platform teams
A platform may support lending, payments, investment advice, and internal operations at once. This page identifies the common control layer and sends each workflow to the right regulatory guide.
The regulator pages preserve distinct intent
RBI FREE-AI and SEBI's instruments use different legal statuses, regulated populations, evidence expectations, and operational vocabulary. Combining them would make both less useful.
Market size supports the investment, but it is not the primary information-architecture reason. The decisive factor is the presence of distinct, substantive regulatory search and implementation intent.
A sensible assessment sequence
- Inventory the AI-assisted workflows and identify the RBI- or SEBI-regulated entity responsible for each one.
- Map personal-data flows, model and connector boundaries, and any external processing under the DPDP workstream.
- Route one representative workflow through policy, PII, approval, and audit controls.
- Correlate AxonFlow decisions with the downstream banking, payment, or securities-system event.
- Run a tabletop incident and emergency-stop exercise, then review whether the evidence answers risk, audit, and board questions.
Primary sources and related guidance
Test the control path against a real workflow.
Use the Evaluation license to assess policy enforcement, human review, evidence records, and deployment boundaries before a regulated rollout.