Your operating environment, private network and creative tools. Connected by design. Built around the freedom to make a digital world yours.
YURANETWORK / THE NETWORK IS ONLY THE BEGINNING
An operating system gives you a place to work. A private network gives you somewhere to go. Creation tools give you a reason to stay.
YuraNetwork is a first-of-its-kind integrated environment: authorized devices, private names, first-party applications and spaces owned by the people who create them, connected as one system.
Discover the idea behind the system ↗Choose a layer to follow the connections. Every part has a role; the relationships are what make it a platform.
The place where the ecosystem comes together.
HOW IT CONNECTSYuraShell brings the desktop experience together; Native connects authorized devices, while Browser and Studio give that connection purpose.
THE EXPERIENCEEnter your workspace, discover a service, then create a space of your own.
Explore OS ↗Admit a known device, not just an anonymous tunnel endpoint.
HOW IT CONNECTSAn account registers a device identity. Signed admission binds it to a WireGuard key; private routing then connects that device to names and services.
THE EXPERIENCEEnroll your device, connect to private services and revoke access when a device leaves your control.
Explore Native ↗Establish ownership and access at the right layer.
HOW IT CONNECTSAccount sessions authorize registration; device signatures authorize Native admission; service policies decide who can use a particular resource.
THE EXPERIENCEManage device access separately from the websites and projects you own.
Explore Identity ↗Connect human-readable names to private services.
HOW IT CONNECTSNative supplies access, private DNS resolves names, routing reaches the registered service, and HTTPS verifies the service connection.
THE EXPERIENCEMove from a discovered name to a creator-owned website without publishing that service directly to the public web.
Explore .yura ↗Turn network access into an everyday browsing experience.
HOW IT CONNECTSNative makes a private destination reachable; private DNS finds it; the browser validates HTTPS and presents the application’s own access experience.
THE EXPERIENCEOpen a private service, follow its links and discover what the connected environment offers.
Explore Browser ↗Help people find private sites through meaningful metadata and content.
HOW IT CONNECTSRegistered services provide the destinations; Search presents discovery inside the network; Browser opens the result.
THE EXPERIENCESearch by a subject, recognize a relevant service and continue directly to its private address.
Explore Search ↗Connect creation with ownership, naming and publication.
HOW IT CONNECTSStudio organizes account-owned projects and versions; .yura gives them a name; hosting serves their artifacts under access policies.
THE EXPERIENCECreate → Design → Preview → Publish → Connect → Manage.
Explore Studio ↗Deliver private services without confusing project ownership with network transport.
HOW IT CONNECTSNative reaches the host, .yura names its service, account ownership controls registration, and the application enforces its own permissions.
THE EXPERIENCEStart with a device-hosted website; grow toward managed, versioned publication as that platform becomes available.
Explore Hosting ↗Bring people into the ecosystem story.
HOW IT CONNECTSThe long-term direction relates communication to accounts, devices and the network while preserving application-specific security boundaries.
THE EXPERIENCEDirect and group conversations, shared media, voice and video are the communications horizon of the platform.
Explore Communications ↗Make the relationship between the user environment and private network state visible and actionable.
HOW IT CONNECTSYuraCore informs YuraShell with trusted status signals, gives Native context for connection readiness, and provides the conceptual policy surface where system state becomes a usable environment.
THE EXPERIENCEOpen a workspace, understand what is ready, see why a service is reachable, and act on the next meaningful system step.
Explore YuraCore ↗Turn a complex private environment into a clear, coherent place to work.
HOW IT CONNECTSYuraShell presents YuraCore state, launches first-party tools, exposes Native context and keeps the relationship between local work and private services understandable.
THE EXPERIENCEMove from a system signal to a useful action: connect, discover, create, publish, inspect or return to the work already in progress.
Explore YuraShell ↗The atlas preserves the eleven present environment layers. YuraMesh is the proposed protocol architecture that reaches across them—naming, identity, admission, ownership, protected data, continuity and transport—without pretending to be a twelfth deployed product layer.
YuraNetwork OS is the vision of a desktop designed around the network—not a network added as an afterthought.
YuraShell, first-party applications and Native connectivity form a consistent setting for everyday work and exploration.
Explore YuraNetwork OSDesktop. Connection. Creation.
Original product-concept illustration · not a release screenshot
Native connects account-owned devices through signed admission and WireGuard transport. Private names turn that connection into a navigable environment.
Inside Native ↗An account registers a device key. The device proves possession through a signed challenge.
Private routes use the encrypted tunnel. Ordinary Internet traffic keeps its ordinary route.
Private DNS, HTTPS verification and the service’s own permissions each play their part.
Browser opens the door. Search helps you find a destination. The private .yura namespace gives services an address people can remember.
Recognizable names. Creator-owned spaces.
Example name, not a live service. .yura is private to YuraNetwork, not a public DNS top-level domain.
An idea becomes a project. A project becomes a space. Studio connects creation with the network it belongs to.
A space for ideas, stories and things worth sharing. Made by you. Connected to something bigger.
Local illustration. No account, reservation or publication is performed.
Self-hosted services, account ownership, private certificate trust and explicit access boundaries give the ecosystem substance beyond its interface.
Explore the technology & security model ↗Communications belong in the wider picture. Meet the separate YuraGram messaging project and the direction for a more connected first-party experience.
The communications vision ↗Existing guides, downloads, account workflows and technical explanations remain accessible.
Choose your starting point ↗YuraMesh is the proposed protocol family for identity, admission, private discovery, ownership, encrypted objects and continuity.
Native remains the current foundation. YuraMesh is the additive architecture exploring what names, sites, services and devices can prove to one another beyond a route or lookup.
Enter the YuraMesh architecture ↗The hub keeps the technical detail; this map gives the wider ecosystem a clear way in.
Private naming and signed service records.
Admission, membership and scoped authority.
Separated installation, device, session and ownership identities.
Portable cryptographic website ownership.
Presence and capability-aware private discovery.
Client-controlled encrypted objects.
Rotation, migration, delegation and recovery.
Signed retirement and anti-reactivation state.
Future privacy-conscious transport direction.