Unified identity
One account and credential system spanning mail, domains and cross-subdomain access.
Nataraja LabsResearch FoundationMandates ↗WORK / 05 · Native identity infrastructure
Kuttaka
The front door to digital life should not be someone else’s rental property.
Kuttaka is an Indian-native stack for email, domains and digital identity. One account joins a Kuttaka mailbox, domain acquisition, bring-your-own-domain verification, managed DNS and cross-subdomain access—turning sovereignty from a slogan into an inspectable operating system.
Operational · external gates remain2026
Evidence position
The September 2026 operating record documents live account, mail, domain and SSO surfaces; residency, continuity and institutional-scale claims remain bounded.
- Condition
- Operational · external gates remain
- Review
- Foundation technical, operating and historical review / active
- Record year
- 2026
THE GOVERNING QUESTION
Can India own more of the identity layer through which people and organisations communicate, recover access and establish durable digital presence?
THE INTERVENTION
What the work changes.
- 01
Join mail, domains and account recovery inside one legible identity boundary rather than scattering responsibility across unrelated services.
- 02
Make domain ownership, DNS configuration and mailbox access understandable enough to be governed by the person or institution using them.
- 03
Treat authentication, recovery, replay protection and abuse controls as the ordinary architecture of trust—not premium add-ons.
- 04
Carry mathematical memory into contemporary infrastructure without converting historical kinship into an exaggerated claim of technological descent.
ANATOMY OF THE WORK
One proposition, held through several layers.
Consumer addresses, mailbox synchronization and webmail read/send through a dedicated mail service.
Domains and DNS
Domain purchase, bring-your-own verification and managed DNS joined to the identity layer.
Security and continuity
TOTP, recovery codes, throttling, replay protection, routing and the unresolved duties of resilient operation.
CLAIM REGISTER
What may—and may not—be said.
Each material claim is paired with the present basis on which it rests. Absence of evidence is kept visible rather than converted into confidence by presentation.
Kuttaka operates public account, mail and domain surfaces.
The September 2026 product record documents the live product family and implemented workflows.
The service has a unified authentication and recovery boundary.
The source records synchronized credentials, TOTP, recovery codes, throttling, replay protection and SSO.
Kuttaka is fully hosted within India.
The source records a Singapore production instance and a Mumbai outbound relay; complete India residency is a roadmap claim.
Kuṭṭaka is the direct ancestor of every modern cryptographic exchange.
The mathematical kinship is real, but the universal line-of-descent formulation is historically and technically too strong.
RESEARCH RECORD
The objects presently in the file.
Kuttaka product family
Mail, domains and unified-account surfaces are described as operating publicly.
Documented liveProduction architecture
Application, mail, registrar, DNS, database and outbound-relay boundaries are identified.
DocumentedIdentity and recovery controls
Authentication, recovery, replay and rate-limiting controls are recorded at the product layer.
ImplementedResidency, deliverability and recourse
External gates and institutional-scale continuity responsibilities require a fuller public account.
IncompleteWHAT EXISTS NOW
The present record.
- The source identifies Kuttaka as a product of Nataraja Labs Research Foundation and records public mail, domain and account surfaces.
- Username selection, synchronized credentials, TOTP, recovery codes, throttling, replay protection and cross-subdomain SSO are described as live.
- Domain purchase, bring-your-own-domain verification, managed DNS and webmail read/send are described as live.
- The operating record identifies the production stack, service providers and present geographic architecture rather than presenting sovereignty as an abstraction.
WHAT IS NOT YET CLAIMED
The boundary of the evidence.
- Kuttaka is not yet fully India-resident: the source records production on AWS Lightsail Singapore with AWS SES Mumbai for outbound relay.
- SES production access and TRAI DLT remain external dependencies and should not disappear inside a generic claim of independence.
- No adoption, deliverability, incident-response or institutional-continuity outcome is claimed without a published operating record.
- The historical account should state mathematical kinship carefully rather than asserting that every RSA key pair descends directly from one historical algorithm.
WHY IT BELONGS TO THE FOUNDATION
Kuttaka turns a question of sovereignty into an operating boundary: who controls the account, mailbox, domain, recovery path and service dependencies through which a digital identity persists. It also imposes a discipline on memory—the past may name the system, but it cannot be used to exempt the system from evidence.
NEXT PASSAGE
What must happen before the work can claim more.
- 01
Publish privacy, retention, incident-response and user-recourse records in language ordinary users can inspect.
- 02
Document service continuity, backup, recovery and provider-exit responsibilities.
- 03
Advance the India-residency roadmap while keeping current geographic dependencies explicit.
- 04
Complete a scholarly and technical review of the public kuṭṭaka narrative.