Yogfile: fast cloud storage, built for privacy

Mount the same Yogfile drives in Finder, File Explorer, and Linux file managers.

Native clients make Yogfile feel like part of the operating system. Each drive appears as a normal location, files download on demand, frequently used content stays local, and remote changes arrive through realtime events.

macOS

The macOS app uses Apple File Provider. Every Yogfile drive appears under Locations in Finder and keeps its remote drive ID as the initial name. You can set a local alias without changing the target drive.

Yogfile drives in the Finder sidebar

Availability: private preview on macOS 13 and later. Ask for access at hello@yogfile.com.

Windows

The Windows client uses the native Cloud Files platform. Drives appear in File Explorer and support normal open, move, rename, delete, hydration, and local cache behavior.

Yogfile drives in Windows File Explorer

Availability: private preview on Windows 10 and Windows 11. Ask for access at hello@yogfile.com.

Linux

The Linux client mounts drives below ~/Yogfile through FUSE 3. It is designed for file managers, shells, editors, scripts, and agents. Credentials live in the Secret Service keyring, not in a plain text configuration file.

Yogfile drives mounted in the Linux file manager

Debian and Ubuntu

sudo install -d -m 0755 /etc/apt/keyrings
curl -fsSL https://www.yogfile.com/packages/yogfile-archive-key.asc \
  | sudo tee /etc/apt/keyrings/yogfile.asc >/dev/null
curl -fsSL https://www.yogfile.com/packages/yogfile.sources \
  | sudo tee /etc/apt/sources.list.d/yogfile.sources >/dev/null
sudo apt update
sudo apt install yogfile

Fedora and RPM-based distributions

sudo curl -fsSL https://www.yogfile.com/packages/yogfile.repo \
  -o /etc/yum.repos.d/yogfile.repo
sudo dnf install yogfile

Authenticate and mount

yogfile login
yogfile mount

The login command reads the credential interactively. Do not pass a complete account number as a command-line argument because process lists and shell history may expose it.

How caching behaves

Cold reads fetch verified ranges from the storage node.
Hot extents stay in a bounded local cache for fast repeated access.
Writes are queued persistently and retried after network loss or a crash.
Realtime invalidation keeps newly opened files on the current content version.
A file descriptor already open remains pinned to one version, so a concurrent replacement never mixes old and new bytes.

Desktop clients