Start with your organisation’s scope and operating requirements. Discuss the deployment, capacity and commercial terms that fit your team.
Talk to usCompare infrastructure boundaries, then discuss hosting, AI processing and onboarding separately.
Hosting location and AI processing location are not the same. Confirm both during onboarding.
These describe the supported architectural models. Capacity, availability, identity setup, AI budget and commercial terms are agreed for the deployment.
| Model | Data boundary | Discuss during onboarding |
|---|---|---|
| Shared database | Tenant isolation with row-level security | Organisation structure, access scope and capacity |
| Dedicated database | A separate database for the tenant | Hosting location, operations and backup arrangements |
| Dedicated stack | A deployment dedicated to the tenant | Infrastructure readiness and operating responsibilities |
Deployment is not a promise of in-country AI processing. Read the processing details · See what each plan includes
Discuss matter volume, document sizes, users, departments, deployment tier and the expected AI workload. Confirm the actual plan and configured caps with the onboarding team.
Explore NyayaDesk for your organisation’s records, people and review process.
Talk to usCommercial terms are agreed during authorised onboarding, and the plan catalogue shows a price only where one has been published. The architecture supports shared-database isolation, dedicated databases and dedicated stacks. There is no instant self-serve trial and no guaranteed production SLA.
Discuss your deployment