About Payload

Ever noticed how file transfers can be so tricky? We think it should be easy, fast and 100% private. That's Payload.

Right now, Payload runs on desktop devices, over local networks. In the future, you'll be able to transfer online and on mobile as well.

How does it work?

When Payload is first launched, it generates a public keypair (Ed25519) and stores it on the local file system, which acts as a stable device identity. Devices announce their presence on the local network and connect automatically to each other (using TLS over either TCP or Quic).

Incoming connections from public IPs are dropped. Local file paths never leave the device and all incoming transfers must be accepted by the user.

Your Privacy

Payload does not have DRM, show ads or sell your information. Today, it only uses the internet to check for updates. If this changes in the future, it will be clearly communicated and optional. For example, we may add anonymized metrics or features that rely on the internet.

A Note on Open Source

Open source software is essential today, and perhaps particularly for networked applications. The plan is to open source parts of Payload when the time is right. For now, please reach out if you want to build something that integrates with Payload.

The Developer

Payload is independently designed and developed by Didrik Nordström. You can find Didrik on Github, Twitter and LinkedIn.

Feedback

Found a bug? Missing a feature? Join our Discord, file an issue on Github or send an email to directly to feedback@payload.app.

Company

John Didrik Nordstroem (Sole Proprietor)
1301 79th Ave
94621 Oakland
United States
contact@payload.app