Justsent
Private P2P file sharing with no cloud uploads, accounts, or storage caps.
Tagline
Private file sharing, no cloud needed
Share files directly. No cloud. No limits.
Fast handoffs for teams that hate uploads.
Open-source file transfer you can inspect.
The no-cloud file transfer client for people who want speed without uploading to a server.
The homepage repeatedly emphasizes direct transfers, no storage limits, and no cloud. That is the clearest category definition and differentiates it from traditional upload-link tools.
A privacy-first alternative to WeTransfer, Dropbox Transfer, and Send Anywhere.
These are the obvious substitutes because they all solve sharing files across devices, but Justsent’s angle is that files never sit in a third-party bucket and the product is open source.
A local-first file handoff tool for teams that hate waiting on upload queues.
The strongest pain-killer message is speed and simplicity: drag, generate a link, share it, and stream bytes directly from the sender. The LAN discovery and direct stream language supports a workflow built for immediate handoff.
Primary user
IT-savvy professionals who regularly move sensitive files between devices without wanting cloud upload exposure
ICP #1
Freelance designer sharing large client assets between a MacBook and a Windows desktop
Pain
They need to send big PSD/ZIP/brand folders fast, but Dropbox and WeTransfer force uploads, link expiry, and sometimes size limits or throttling.
Why this solves
Justsent sends files directly from device to device, so there is no cloud upload queue, no storage cap, and no middleman slowing the transfer.
ICP #2
Security-conscious operations manager at a small company moving confidential documents
Pain
They are uncomfortable putting contracts, invoices, or internal docs into third-party transfer services where files sit on someone else’s server.
Why this solves
The product explicitly avoids cloud storage, adds end-to-end encryption, and supports password protection before the stream starts, which maps to their confidentiality concerns.
ICP #3
Open-source developer who self-hosts or audits their tools
Pain
They distrust closed file-sharing apps and want something they can inspect, tweak, or build from source when needed.
Why this solves
Justsent is MIT-licensed, has a public GitHub repo, and the page explicitly invites users to inspect, modify, or host the core sharing stack themselves.
Strengths
- +The value prop is very clear in the hero: direct sharing, no cloud, no limits, no signup.
- +The feature section does a good job translating technical architecture into user-facing benefits like LAN speed, internet sharing, and password protection.
- +Open-source credibility is strong because the GitHub repo, MIT license, and contribution hooks are visible on the page.
Weaknesses
- −The page mixes real product language with obviously fake/demo wording like "fictional files" and "Select Demo File," which undermines trust for a file transfer app.
- −The "Download analytics" feature is framed in a way that sounds creepy because it mentions "IP address logs" without explaining consent, retention, or privacy controls.
- −There is no proof of reliability: no screenshots of actual transfers, no throughput benchmarks, no supported file size documentation, and no security details beyond vague encryption claims.
- −The product positioning is too broad right now; it tries to be LAN sharing, global sharing, privacy tool, and open-source platform all at once.
- −The page lacks concrete use cases and comparison points, so visitors are left to infer why they should switch from tools they already know.
Fix these
- Replace the demo/faux language with real product screenshots or clearly separate a sandbox demo from the actual download flow.
- Add a trust block that explains exactly how encryption works, what metadata is collected, and whether IP logs are optional, local-only, or exportable.
- Create a comparison table against WeTransfer, Dropbox Transfer, Send Anywhere, Snapdrop, and LocalSend focused on cloud upload, account requirement, file limits, and open-source status.
- Narrow the hero message to one primary wedge, such as "secure P2P file sharing without cloud uploads," and let LAN sharing be a supporting benefit.
- Add concrete performance and compatibility claims: max file size, average LAN speed, supported OSes, and whether transfers work across NAT/firewalls in real-world conditions.
Drop-in replacement copy
Headline
Share files directly. No cloud.
Private P2P transfers with no accounts, no storage caps, and no upload queue.
Send files without handing them to a server
Justsent moves files directly between devices instead of uploading them to cloud storage first. That means less waiting, less exposure, and no third-party bucket in the middle.
Share instantly on the same Wi‑Fi
Nearby devices can find each other automatically on the same subnet and start transferring right away. It feels like a local handoff, not a hosted file link.
Keep sensitive files locked down
Transfers are end-to-end encrypted and can be protected with a password before the download starts. It is built for client assets, contracts, and files you do not want sitting on someone else’s server.
Open-source desktop app you can inspect
Justsent is MIT-licensed and built with Tauri, React, and Rust. If you care about how your tools work, you can audit, modify, or self-host the stack.
FAQ
Does Justsent upload my files to the cloud first?
No. Files transfer directly between devices. Cloud relays are only used to help two devices connect when needed, not to store your files.
Can I send large files?
Yes. Justsent is built for large assets like PSDs, ZIPs, videos, and document packs. Check the current app docs for any platform-specific limits.
What happens if the other device is not on my Wi‑Fi?
Justsent can still connect over the internet using WebRTC STUN/TURN relays. The files still move peer-to-peer rather than being uploaded into permanent storage.
Is it secure enough for confidential files?
Transfers are end-to-end encrypted, and you can require a password before the download starts. If you need deeper assurance, the app is open source so the code can be inspected.
What platforms does it support?
Justsent is a desktop app built for modern Mac, Windows, and Linux workflows. It is designed for people moving files across mixed-device setups.
Just shipped Justsent. Private P2P file sharing for people who don't want Dropbox, WeTransfer, or another cloud bucket in the middle. No accounts. No storage caps. Direct device-to-device transfers. https://justsent.app
Built Justsent with Tauri, React, and Rust because I wanted fast transfers without shipping your files through someone else's server. LAN discovery, internet sharing, password protection, open source. Still polishing reliability and UX. Feedback welcome.
Need to send a 4GB design folder, a contract pack, or a zip with real client work? Upload queues, link expiry, file caps, and "sorry, too large" are the worst part. Justsent skips the cloud entirely.
1. Drag file in 2. Share the link or code 3. Transfer starts directly between devices Works on local Wi‑Fi or over the internet via WebRTC relay. No account. No upload queue. No storage bill.
The same complaint keeps coming up: "I don't want sensitive files sitting on another company's server just so I can send them once." That's exactly what Justsent removes. Open source, encrypted, direct transfer.
Justsent is live. A private P2P file sharing app for Mac, Windows, and Linux that moves files directly between devices. No cloud upload. No account wall. No arbitrary limits. Built for people who actually ship work.
I didn't build Justsent to be clever. I built it to remove the annoying part of sharing files: waiting for uploads, worrying about storage, and trusting a random transfer link. If the product disappears into the background, that's the point.
Contracts. Invoices. Internal docs. Client assets. Email attachments are clumsy, Slack is noisy, and cloud transfer links put your files on someone else's server first. Justsent sends them straight device-to-device.
Justsent auto-discovers nearby devices on the same subnet and starts the transfer without a cloud round trip. If you're remote, it also works over the internet. That means one tool for office, home, and client handoff.
A lot of people don't just want private file sharing. They want to inspect the code, understand the encryption, and know what happens to their metadata. Justsent is MIT-licensed because trust should be auditable.
Angle: privacy-first alternative to cloud transfer tools
I built Justsent because file sharing has a weird default: You want to send one file. The app asks you to upload it to a server. Then it gives you a link. Then you trust that server to do the right thing. That model is fine for some use cases. It's not fine for client work, internal docs, contracts, or anything you wouldn't want sitting in a third-party bucket. Justsent skips the bucket. It moves files directly between devices instead of uploading them to cloud storage first. No accounts. No storage caps. No waiting on a queue just to share a zip file. It also supports local Wi‑Fi discovery, internet transfers via WebRTC relays, password protection before download starts, and an open-source stack built with Tauri, React, and Rust. I'm sharing it because I think the market is still under-served on one simple idea: private by design should also be fast by nature. If you're the kind of person who hates sending sensitive files through a cloud transfer service, I'd love your feedback on what would make this your default tool.
Angle: technical but practical workflow story
Most file transfer products are built around the same compromise: Upload first. Share later. Hope the recipient downloads it before the link expires. For teams shipping large assets or moving confidential files, that creates friction in the exact place you want none. I wanted a desktop client that felt closer to "hand this over" than "stage a transfer." So Justsent does a few things differently: • Direct device-to-device transfer • Nearby discovery on the same Wi‑Fi subnet • WebRTC-based sharing when devices are not local • Password protection before the stream starts • Real-time transfer history and status tracking The goal isn't to be everything. The goal is to be the simplest answer to a specific job: move a file from one machine to another without involving cloud storage. It's open source, MIT licensed, and built with Tauri + Rust because I wanted it small, fast, and inspectable. If you share files across Macs, Windows machines, or both, what is the part of the flow you hate most today?
Angle: open-source and trust angle
People keep telling me they want a "secure file sharing app." What they usually mean is: Don't make me create an account. Don't store my files. Don't hide the transfer logic. Don't make me guess how the encryption works. That's the product direction for Justsent. It's an open-source desktop client for private P2P transfers, with LAN discovery, internet relays when needed, and password-protected downloads. The stack is public, the license is MIT, and the intent is simple: if you're going to trust a tool with sensitive files, you should be able to inspect it. I think there's a real audience here: freelancers moving client assets, ops teams moving contracts, developers who self-audit their tools, and anyone who's tired of cloud transfer defaults. What I'd love feedback on is not "should this exist?" It's: what proof would make you trust it enough to use it for real work? Benchmarks? Security notes? Compatibility matrix? Comparison table? That stuff matters more than marketing.
No visuals for this kit yet.
Tagline
Private P2P file sharing, no cloud uploads
Description
Send files directly between devices with no accounts, no storage caps, and no cloud upload step. Justsent supports LAN discovery, internet transfers, password-protected downloads, and open-source transparency.
Maker's first comment
I built Justsent because I was tired of the default file-sharing flow: upload your file to someone else’s server, wait for it to finish, then send a link and hope nobody mishandles it. That model is acceptable for casual sharing, but it feels wrong for client assets, contracts, internal docs, and anything sensitive. Justsent is my attempt at a simpler rule: if two devices can talk to each other, the file should move directly between them. No account wall, no storage bucket, no arbitrary file caps. It works on the same Wi‑Fi network and over the internet, and I kept the stack open source so people can inspect what it’s doing. I’m launching it now because I want to hear from the people who actually have this pain every week: freelancers, ops folks, and technical teams. If you try it, I’d especially love feedback on reliability, transfer clarity, and whether the trust story is strong enough to replace the tools you already use.
Pinned maker comment
I’d love feedback on three things: whether the no-cloud positioning is clear in under 5 seconds, whether the transfer flow feels trustworthy, and what proof you need before using it for sensitive files.
Meta
Sharing client files still means uploading them?
Targeting freelance designers, ops managers, and privacy-conscious professionals. This ad tests the assumption that people who share sensitive files want speed without a cloud middleman. Justsent sends files directly between devices with no accounts or storage caps.
Google Search
Private P2P file transfer app
Targeting searchers comparing WeTransfer, Dropbox Transfer, Send Anywhere, Snapdrop, and LocalSend. This ad tests whether "no cloud uploads" is a strong enough keyword-level benefit to win clicks from people already looking for a transfer tool.
Reddit Promoted
I got tired of cloud transfer links
Targeting r/SideProject, r/indiehackers, and r/microsaas readers who share files for real work. This ad tests the assumption that open-source, direct device-to-device transfer is more compelling than another upload-and-link product.
Subreddits
r/SideProject
Show the product, the problem it solves, and one honest lesson from building an open-source P2P transfer app.
Rules: No pure promo. Lead with the problem and build story. Engage in comments.
r/indiehackers
Share the go-to-market angle: why a no-cloud file transfer tool exists and what feedback you want from indie founders.
Rules: Must be transparent, useful, and discussion-driven. Avoid link dumping.
r/microsaas
Position it as a tiny utility that replaces a recurring workflow pain for freelancers and small teams.
Rules: Keep it specific, relevant, and non-spammy. Focus on product mechanics and lessons.
r/EntrepreneurRideAlong
Post a founder journey thread about making a privacy-first desktop utility and the distribution challenge.
Rules: Needs a story, progress, and reflection. Self-promo should be secondary.
r/privacy
Discuss the privacy tradeoff of cloud transfer services versus direct peer-to-peer sharing.
Rules: Be factual, avoid hype, and be ready to answer technical/privacy questions in detail.
Communities
Post a build log, a specific lesson about trust in file sharing, and ask for feedback on positioning and onboarding.
Launch with a technical angle: open source, Tauri/Rust stack, and the no-cloud transfer architecture. Keep claims concrete.
Join, read first, then ask for opinions on local-first transfer workflows and what they'd want before trusting it.
Cold outreach template
Hey {firstName} - saw your {context} and thought of Justsent. It’s a private P2P file transfer app with no cloud uploads, built for people who move sensitive files and hate WeTransfer-style links. If you’re open, I’d love 2 minutes of blunt feedback on whether this would fit your workflow.
Product Hunt timing
Launch on Tuesday at 12:01am PT. That catches the early US morning and still gives you the full day for product-minded users in North America and Europe, which fits an IT-savvy, desktop-first audience that checks tools during work hours.
Indie Hackers post ideas
- 01Why I built a no-cloud file transfer app instead of another link generator
- 02What I learned shipping an open-source desktop app in Tauri + Rust
- 03The trust problem in file sharing: what makes users believe a privacy-first tool?
Competitor alternatives
Current tone of voice
Privacy-forward, technical, and slightly playful; examples include "Private by design. Fast by nature." and "Share files directly. No cloud. No limits."
Your kit is ready. Sign up free to unlock, takes 10 seconds.
7 more X posts · 2 LinkedIn · Product Hunt copy · ad hooks · 100-user playbook · landing critique