About
Files should move
like messages do.
Sending a text to someone across the world takes a second. Sending them a large file still means an upload, a wait, a link, an expiry and a copy sitting on someone else's server. We think that is a design problem, not a law of nature.
What we believe
Five ideas behind every decision.
Direct first
The shortest path between two devices is a straight line. We send files that way whenever we can.
Private by design
Keys are made on your devices and never reach our servers. We cannot read what you send, even if we wanted to.
Open source
The code is public under the MIT licence, so you can check every claim we make.
Honest about limits
We write down what Ferry cannot do, in the README and on every comparison page.
Free to send
Sending and receiving costs nothing. We only charge for the room it takes to hold a file for someone.
Where Ferry is going
From two devices, to people, to organisations.
Today
Direct sends
Browser, command line, Chrome extension, offline mode and AI agents. No account needed.
Opening now
Ferry for the web
Accounts, held files, a dashboard and a history that follows you. Opening to a few people at a time.
Later
Teams and Enterprise
Shared workspaces, request links, single sign-on and audit. We are talking to people about what they need.
Who builds it
One person, in the open.
Ferry is built by Shola Jegede, a developer relations engineer based in Lagos. It started as a way to move files between his own devices without an upload, and grew from there.
Because the code is open, you do not have to take our word for how it works. Read the security page, then read the source.