What it does.
Six things quattle is built around, and what each one looks like in your hands.
Encrypted first
Your key is made in your browser and never leaves it. File names, folder names and the files themselves are all sealed before anything is sent, so what reaches the server is bytes nobody here can open.
Sharing that ends
Send a file as a link and decide how long it lives. Set an expiry, let it burn after a single open, put a password on it, or revoke it later and watch it stop working immediately.
Taking files in
Make a link that only takes files in. Anyone holding it can send you something without making an account, and what they upload is encrypted the moment it arrives.
Folders you share
Share a folder and everyone inside it works in the same place, with changes appearing for all of you. Only the owner pays for the storage, so the rest of the group needs nothing but an account.
No email, ever
There is no email address, because there is nothing to send you. A username and a passkey are enough, recovery codes cover the bad day, and no part of it asks who you are.
Made to automate
Give a script or a Shortcut its own token and let it drop files in while you are elsewhere. Read tokens fetch files back out from the command line, and webhooks tell your own systems when something lands.