Identity before access
Account-authenticated registration uses an Ed25519 device key and a single-use signed challenge. The private identity key stays on the device.
YuraNetwork Native
A connection with an identity.
Native connects authorized devices to YuraNetwork’s private services. Account ownership, device identity and encrypted transport form one deliberate access path.
A layered relationship
AccountDevice identityNative admissionPrivate route.yura service
An account registers a device identity. Signed admission binds it to a WireGuard key; private routing then connects that device to names and services.
Protocol relationship
Native is the current foundation
Native v1 remains the operational admission and transport layer. YuraMesh membership, ownership and authorization would require separate signed objects; Native is not silently replaced.
Current systemDefined boundaryProtocol direction
Explore the related architecture ↗Encrypted transport
WireGuard carries traffic between the device and the network gateway. A separate admission exchange authorizes the connection.
Two routes, one device
Private destinations use the Native route. Public Internet traffic stays on the ordinary interface under the documented split-routing contract.
Access has a lifecycle
Device listing, revocation, session expiry and heartbeats make access manageable. Service authorization remains a separate boundary.
Connected by design
Native is part of something bigger.
An account registers a device identity. Signed admission binds it to a WireGuard key; private routing then connects that device to names and services.
Enroll your device, connect to private services and revoke access when a device leaves your control.
Use the preserved setup guides for the existing Tunnel tools; OS Native activation follows its account and device workflow.