Source and preview
Keep your files with the owner, preview changes locally, and make the intended audience explicit before publication.
Builders
Create a place that belongs to you.
Studio and self-hosting meet at the publication boundary: local source, preview, version, name, policy and private delivery.
Name the service
A .yura name gives people a stable private address while the underlying host remains an operational responsibility.
Choose a hosting model
Self-hosting keeps the source and runtime on your connected device. Managed hosting is a separate architecture with versioning and lifecycle controls.
Read hosting architecture ↗Operate the lifecycle
Publication is more than a file copy: access policy, rollback, unpublishing, backups and recovery are part of ownership.
Publication is a lifecycle
A trustworthy publishing path moves through source, preview, version, name, access policy, active delivery, rollback and retirement. Each stage has a different authority and failure mode.
What the current workflow proves
Self-hosted publication proves that a connected owner can serve a private site through the documented setup. It does not establish universal ownership or managed availability.