A practical origin
FileYard began as a personal file server. It was built for the ordinary moments that make up a homelab: finding a document from another room, sending a folder to family, syncing a working directory, and knowing a normal backup tool can still see the source files.
The project started under the name YourFiles, became Dormer for a while, and was renamed FileYard after a naming collision. The name changed; the preference did not. Files should remain ordinary files.
Why “yard”
A yard is bounded, useful space. You decide what belongs there, who can enter, and which gate they use. That is a better metaphor for FileYard than a cloud: grounded, understandable, and attached to the place you control.
The Open Gate mark reflects the same idea. FileYard creates organized access, but the opening matters as much as the boundary. You should be able to enter with a browser or client and leave with the same files on disk.
What it became
Along the way, the server gained sharing, sync, WebDAV, mobile access, authentication controls, version history, and more. It runs on its author’s own server today, which keeps design discussions close to actual maintenance and actual data.
That personal use is meaningful, but it is not a substitute for broad testing. FileYard’s public status is intentionally direct about the distance between a working implementation and a mature release.
A narrow promise
FileYard aims to make a self-hosted file server pleasant without turning into an everything platform. Its promise is narrower:
Keep the files. Simplify the server.
That means polished access, clear control, familiar infrastructure, and an honest account of the work still ahead.