1 / Prepare the device
Use the existing platform-specific setup material and preserve the generated device identity. Keep credentials out of URLs and logs.
View verified downloads ↗Start here
Connect with context.
Choose a path, establish trust, then move through the private environment with a clear understanding of what each layer does.
2 / Establish Native access
Account ownership and device admission are separate from application permissions. Read the Native and Identity pages before troubleshooting a connection.
Understand Native ↗3 / Resolve a private name
Private DNS and HTTPS verification make a .yura service reachable and recognizable inside the network.
Explore .yura ↗4 / Publish or discover
Open YuraSearch, follow a private destination, or use Studio and the self-hosted workflow to create a space of your own.
Open Studio ↗How to troubleshoot by layer
Start with account authentication, then device identity, Native admission, private routing, DNS resolution, HTTPS trust and finally application authorization. A successful tunnel does not prove that a service is permitted.
What to keep separate
Keep installation keys, transport keys, account credentials and recovery material separate. Use the preserved platform guides for exact commands and never paste private credentials into a URL or support message.