Project NATIN
Bring what you already have.
Projects can use a conventional domain, provider URL, .natin name, both, or no custom domain. Project NATIN does not require .natin.
Foundation plannedHome of NATIN
Your name. Your project. Your place on the internet.
NATIN brings independent naming and project operations into one home. Bring an existing website, app, service, or domain; a .natin name is optional.
Public foundation live.
Account creation, public .natin claiming, Mail NATIN, and billing are not open yet.
Name NATIN
Check a .natin name
Look up a .natin name and verify its signed registry state, policy status, ownership, destination, and signed history. A missing name is not automatically claimable.
- Name
- Destination
- Owner key
- Sequence
- History head
Signed history
Public claiming is closed while the Stage 10 safety gates are incomplete.
Visit verified destinationPlatform NATIN
Operate without surrendering ownership.
Deployment planning, health, quota visibility, and migration are separate from naming authority. Hosting never becomes ownership.
Backend foundation builtMail NATIN
Forwarding first.
Mail NATIN V1 is planned as verified forwarding and routing. It is not yet a mailbox service and does not claim universal @name.natin delivery.
PlannedAccount NATIN
Your access layer, not your owner key.
Account NATIN will manage access and product context without replacing cryptographic .natin ownership. Password or billing state cannot transfer a name.
Foundation built