A drive for AI agents
A drive your agent can write to.
And read back tomorrow.
Storage that outlives the session, reachable by any model: one MCP connector, or plain HTTP for everything else. Files stay until you delete them, and each one has a URL you can hand to a person.
No agent? Opening a drive creates your account for you. No form, no password.
Three ways this product gets used
If you are an agent
One line of config, then seven tools: drive, folder, upload, link, list, delete. What you write is still there on the next run, and readable by a different model.
If you are a person
One click opens a drive and creates the account for you. Folders, previews, and a short URL to hand out.
If you are receiving one
A page with the file's name and size. Preview it without downloading anything.
For agents · Model agnostic
One connector. Any model.
A drive belongs to your account, not to the assistant that happens to be talking. Add the connector in Claude, Cursor, VS Code, or anything else that speaks MCP, and the same files answer to all of them. Whatever cannot speak MCP can still speak HTTP: the seven tools sit on a public API, so no model is locked out.
create_account: a 16-digit number, created and remembered on first use.
create_drive: a short public name like x7k2p9, open or locked.
create_folder: a path like reports/2024/q3, every missing level created at once.
upload_file: path in, share URL out. Drops it straight into a folder if you name one.
share_link: a short-lived signed URL that downloads immediately.
list_files: drives, folders, files and sizes.
delete_file: gone now, and every link with it.
Errors come back as {code, message, hint}: an agent that fails is told what to do next.
Run this
claude mcp add --transport http yogfile https://mcp.yogfile.com/mcp
Then say anything: on the first call it opens a page to connect your account (or create one). Nothing to install.
A session
> upload the build and send me a link uploaded app-v2.dmg 48.2 MiB drive x7k2p9/releases link yogfile.com/f/8c41… kept until you delete it
An example session, not a benchmark.
What agents do with it
- Keep state between runs
- a drive outlives the conversation, so the next run starts from what the last one left.
- Hand off between models
- one agent writes to a drive, another reads it. The name is the protocol, whoever is at the other end.
- Ship an artefact
- the build leaves as a link, not as a path on a machine nobody else can reach.
- Collect for a human
- several files, one short URL that previews everything.
The link
A share link that carries its own rules
Every file gets one stable URL, and each visit mints a fresh signed link behind it. The rules travel inside the signature: strip one out and it stops matching.
- Signed, not public
- the URL a recipient opens is minted for them and lives minutes. A link that leaks is a link that has already stopped working.
- Speed cap
- 10 MiB/s per connection, enforced by the storage node itself rather than by us asking nicely.
- Connection cap
- two per link, so one recipient cannot turn your file into a mirror.
A public bucket URL is a promise you cannot take back. A signed link is a decision you already made.
The drive
Folders, previews, and one short name
A drive carries a short name like x7k2p9 and lives at a URL you can read out over the phone. Folders nest as deep as you want them to, and an agent files things straight into a path. Recipients preview images, video, audio and text without downloading a thing. Lock it and it asks for a passphrase.
Your drives
| Name | Size | Added |
|---|---|---|
releases | Aug 14 | |
press | Aug 09 | |
launch-teaser.mp4 | 48.2 MiB | Aug 15 |
press-kit-cover.png | 3.1 MiB | Aug 15 |
build-2026-08.tar.gz | 212 MiB | Aug 13 |
quarterly-report.pdf | 840 KiB | Aug 12 |
handover-notes.md | 12 KiB | Aug 11 |
press-kit-cover.png
- Size
- 3.1 MiB
- Added
- Aug 15
No invitations to accept, no permission matrix, no seats to buy. You have the address, or you do not.
Lifecycle
Files stay until you say otherwise
Nothing deletes itself here by default. When something should not linger, say so and the sweeper honours the date to the second. It is a policy you set, on the drive or on the upload, not a rule you live under.
- Nothing, by default
- a file you upload today is still there next year unless you delete it.
- A lifetime per drive
- set it once and everything dropped into that drive inherits it, including what an agent puts there.
- Or per file
- one upload, one date, for the thing that genuinely should not outlive the week.
The path of a byte
Four steps, and our API never touches your file
- 01
Ask
The client asks for an upload grant. The API checks the account and signs Ed25519 headers valid for minutes.
- 02
Send
The bytes go straight to the storage node the geo-DNS picked. They never pass through our API.
- 03
Confirm
The client reports the content hash. The file appears in your drive, ready to share.
- 04
Keep
It sits in the cluster, erasure-coded across machines, until you delete it or a lifetime you set runs out.
Underneath
The storage engine is ours, and you can read it
Yogfile is a thin product over Nauka, an open-source storage engine (AGPL) by the same author. Files are erasure-coded across machines on several continents and served from the nearest nodes.
- Reed-Solomon 4+2
- six pieces across machines; any four rebuild the file.
- BLAKE3 content addressing
- a file's name is what is inside it, so identical uploads are one object.
- Authoritative geo-DNS, inside the binary
- the cluster answers DNS itself and hands each client its nearest nodes.
- Even our database sleeps in the cluster
- its snapshots ship into the storage it sells, so the service can be rebuilt from it.
Built by Sacha Ifrah, engine first, product second. The source is public, which is a reasonable thing to demand of anyone holding your files. Read the engine →
Pricing, honestly
Free while we launch
There is no checkout, so nobody is paying and nothing is metered beyond the two caps below. Storage will be billed eventually, at three dollars per terabyte per month, and you will hear about it before a bill does. Here is every limit that exists today.
- Storage
- Uncapped while we launch
- Nothing is metered today. Billing arrives with a checkout, and a warning before it.
- File size
- 1 TiB per file
- Bytes go straight to a storage node, so a big file is a long upload, not a refusal.
- File lifetime
- Yours to set
- No expiry unless you ask for one, on a drive or on a single upload.
- Speed per connection
- 10 MiB/s
- Enforced by the node itself, inside the signed link. This one you can actually hit.
- Connections per link
- 2
- So one recipient cannot quietly turn your file into a mirror.
- Signup
- None
- A 16-digit number is the whole account. No email, no card, nothing to cancel.
Hit a limit and the API tells you which one, and by how much.
Straight talk
What Yogfile is not
Not a backup. One copy, one service. A file that only exists here does not exist.
Not a sync folder. No desktop client, no version history, no shared team accounts. A drive here is an address you hand out, not a disk that follows you around.
Not one assistant's feature. Any MCP client can add the connector, and anything with an HTTP client can skip it. Your files sit in your account, not inside a chat window.
Not recoverable. Lose the 16 digits and the account is gone, on either plan. That is the price of an identity nobody can phish or subpoena.
Not old. It launched this month. No logos, no uptime record, nothing true to show yet.
Not lawless. Reports are deduplicated, a threshold takes a file down, and a banned hash dies across the cluster with every copy of it.
Honest answers
Fair questions
Does this only work with Claude?
No. The connector is plain MCP, so any client that speaks it works: Claude, Cursor, VS Code, your own harness. And the seven tools sit on a public HTTP API, so a model with no MCP support at all still reaches the same drive.
Do my files expire?
Not unless you ask. Put a lifetime on a drive or on a single upload and the sweeper honours it to the second. Leave it alone and the file stays until you delete it.
What if I lose my account number?
It is gone, and nobody can bring it back, us included: there is no email to reset with. Copy it somewhere real the first time you see it.
What is the catch?
It is free while we launch and there is no email address to sell. The only limits you can actually hit are the two on every link: 10 MiB/s per connection, two connections.
Can two different agents share a drive?
Yes, and that is the point. A drive is reached by its short name, so one run writes and another reads, whatever model is behind each of them.
Can anyone find my files?
No index, no search, no directory. A file is reached by its URL, a drive by its name, and a locked drive shows nothing without its passphrase.
Who is behind this?
One person, who also wrote the open-source engine underneath. That is the honest answer for a service this young.
What do you know about me?
A file's name, size, hash, and the lifetime you chose if you chose one. No email, no password. Rate limits hold your IP in memory for minutes; abuse reports keep only a salted hash of it.
Give your agent somewhere to keep things.
One line of config, no account to create, nothing to cancel. What it writes today is still there for the run after this one.