Nothing leaves.
Until you press send. Then exactly the project you shared, and nothing else.
Just send.
One link. Always the latest.
Nothing leaves.
Until you press send.
Just send. One link. Always the latest.
Sending work? Drop the folder.
Receiving it? Open the link.
Rather not do it yourself? Ask your agent.
Then Epic Games rebuilt it. Lore is the version engine they open sourced from Fortnite: built by people who ship hundred-gigabyte worlds, so huge files are the normal case. We host it and wrapped it in a link: no commands, no jargon, and anyone you send it to just opens it. Dropbox simplicity. GitHub history. Epic’s engine underneath.
You’re meeting the Henderson team at 9 tomorrow.
The deck is yours, the renders are Priya’s, the numbers are Dana’s, and all three changed today. The link you sent Monday already carries every save. Nobody attaches anything tonight.
Collecting, zipping, re-attaching. “Is this the final deck?” at 11 p.m.
The link went out Monday. Every save since is already in it: deck, renders, numbers.
One address · the round trip
Everyone stays on the same files.
Interlinked treats the folder as a project with versions. Every save pushes just the change up to the link; every reader gets just the change down. Nobody re-sends, nobody re-downloads, nobody asks which file is right.
The full loop
interlinkedfiles.com/s/atrium-towerSent once, weeks ago, edited every day since: never re-sent, never stale.
The heavy part is the re-send.
The receipts · measured on real projects
And the cost isn’t only bandwidth and waiting. Every re-send mints one more copy nobody can tell apart, and the truth of the project scatters across inboxes and drives. Keep one address, and the question “which file is right?” stops existing.
Then Epic Games rebuilt it. Lore is the version engine they open sourced from Fortnite: built by people who ship hundred-gigabyte worlds, so huge files are the normal case. We host it and wrapped it in a link: no commands, no jargon, and anyone you send it to just opens it. Dropbox simplicity. GitHub history. Epic’s engine underneath.
Any of them can run the CLI: “share this folder with Ana” is a working instruction. And your first project costs $0: no card, 2 projects and 5GB hosted free, the app free forever.
ifile share+ 7 more, auto-registered by the installer · the CLI rides on PATH
One project. Four ways in.
Someone sent you a project? Paste the link, or bring the QR code in as a picture, on screen, or on your phone. And the link itself opens read and write in the browser: receiving is never the whole story.
Four ways, one destination · straight into the app
“Send Ana Tuesday's version of the site plan.”
Nothing to memorize: your agent finds the save and sends the link, and the link works for anyone, forever.
The engine your link runs on
- A zip or a drive upload re-sends every byte, changed or not.
- Lore, the engine Epic Games open sourced from Fortnite, content-addresses every file: it knows exactly which bytes are new.
- Only those cross the wire, and every save stays behind the same address.
Same folder, same files. Just never re-sent.
measured: a 1MB edit inside a 3.5GB project crossed as 1.1MB · a rename crossed as 161 bytes · a 128MB project arrived cold in 5.6s