Yogfile documentation
A fast, privacy-oriented drive for people, applications, and AI agents.
Yogfile gives people and agents one durable drive that works from Finder, File Explorer, Linux, the web, MCP, and a public HTTP API. Files outlive sessions and model changes.
Quickstart
Create an account, make a drive, and write your first file.
Desktop clients
Use Yogfile as a native filesystem on macOS, Windows, and Linux.
MCP connector
Connect Claude, Cursor, VS Code, or any compatible MCP client.
HTTP API
Build directly on the same API used by the web and native clients.
One drive, many clients
Every client sees the same namespace. A file created by an agent can be opened from Finder, moved from the web, read from Linux, and handed to another model later. Realtime events keep those views converging without a manual refresh.
Fast by design
Yogfile keeps metadata, identity, and policy in its API. File bytes do not pass through that API. Uploads and downloads move directly between the client and the nearest available Nauka storage node. Native clients add ranged reads and a local extent cache for fast repeated access.
Privacy without an identity profile
An account is a random 16-digit credential. Yogfile does not require a name, email address, social login, or payment method at launch. The complete number is not displayed again by default and must be handled like a password. Optional TOTP MFA and recovery codes protect it further.
Keep the account number private
Anyone with the complete account number can sign in while MFA is disabled. Store it in a password manager. Never put it in source code, prompts, logs, screenshots, or support messages.
Where to go next
- Start with the quickstart for a working drive in a few minutes.
- Read desktop clients if you want a native filesystem.
- Use the MCP connector for agents that speak MCP.
- Use the HTTP API for custom applications and runtimes.