Usually: stored
Direct
Most sharing is an upload to someone else's servers. adhal sends device to device, so there's no hosted copy to retain or leak.
adhal connects two devices directly and moves a file between them, end-to-end encrypted. No account, and no server storing it along the way.
A simulation with a sample file. Nothing on your device is read or sent.
Ready for the real thing? with the adhal CLI, or read the source.
The engine and command-line tools are live on npm for macOS and Linux. Desktop and mobile apps come next.
Usually: stored
Most sharing is an upload to someone else's servers. adhal sends device to device, so there's no hosted copy to retain or leak.
Usually: readable
Keys are derived on the two devices from the code, and the code is never sent. Anything carrying the traffic sees only ciphertext.
Usually: capped
No account, no plan tiers. Pipe a stream of unknown length straight in, and an interrupted transfer resumes where it stopped.
Built on Holepunch's and , with a small, specified protocol on top. adhal runs no servers of its own.
--relay=<key>) carries the encrypted traffic. It's experimental; the relay sees both IP addresses, never the file.Private, not anonymous. Each side sees the other's IP address, as do DHT nodes near the meeting point.
The code is the key. Whoever holds it can complete the drop. Hand it over privately.
macOS and Linux today. Windows follows once it's covered by CI. Threat model.
@ad-hal/engine and @ad-hal/cli on npm