Prerequisites and process for enabling multi-tenant OAuth login support on a Connect App

chaudharyamitiit2007
Hello everyone,

We are developing a broker-neutral execution utility designed to help retail investors run systematic grid-ladder order placements on their own accounts.

We currently have a fully functional web platform built and verified as a Proof of Concept (POC) using a personal Kite Connect Developer subscription. However, by default, standard Connect apps are restricted to a single Zerodha Client ID.

Since we are planning to onboard a small group of beta testers and eventually scale the platform, we want to enable multi-tenant OAuth login support for our app.

Could the Kite Connect team or any developers who have gone through this process share some guidance on the following:
  1. Prerequisites for Multi-Tenant Activation: What are the business structure requirements (e.g., LLP/Private Limited) and regulatory prerequisites (e.g., SEBI RA/RIA registration status) required to get a Connect App approved for multi-user OAuth logins?
  2. Platform Audit Scope: Once we submit our platform walk-through, demo video, and website credentials, what does the security/compliance audit process entail, and how long does it typically take?
  3. Egress IP Whitelisting: Once multi-user login is enabled, is our central server's static IP address whitelisted at the App level to execute orders on behalf of all authorized Client IDs? Does Zerodha restrict routing multiple client orders through a single platform IP in this mode?
  4. Alternative Options for Beta Staging: Is there a way to add a limited list of test Client IDs (e.g., 5 to 10 staging accounts) for initial integration testing before going through the full platform audit?
Thank you for your time and guidance.
Sign In or Register to comment.