
Doctransfer
Stop Paying for DocSend. Share, Track, and Protect Documents
Creating DocTransfer—a serverless, zero-knowledge alternative with premium features.
The Tech Stack: Leveraging React, TypeScript, Vite, Supabase, and Clerk.
Deep Tech Breakdown: Explaining how client-side AES-256/OpenPGP vault encryption, page-by-page PDF analytics, WebAuthn biometrics, and webcam snapshots were built directly into the browser to keep server hosting costs near zero.
The Strategy: How offloading processing to the client allows you to offer premium security features for free or at a highly disruptive price.
About
DocTransfer is designed to disrupt highly overpriced document-sharing platforms like DocSend (which costs upwards of $250/month per user),DocuSign by providing an enterprise-grade, zero-knowledge alternative.

2 Comments
This is a great technical post, but you are describing your moat as if it were a hosting-cost trick. "Offload processing to the client so server costs stay near zero" reads like a margin story. It is actually the whole strategic point, because that one architectural choice buys you two things DocSend cannot have at the same time: zero-knowledge, meaning you literally cannot read the documents, and near-zero server cost, so you can undercut them. One decision, both advantages.
And it is defensible for the reason that matters: DocSend cannot follow you client-side without breaking the server-side visibility their whole product is built on. So stop leading with "cheaper than a $150 invoice," because price is the one fight Dropbox wins by dropping a number tomorrow. Lead with the thing only your architecture allows: "the document room that cannot read your documents." Let the disruptive price be the line you mention second, because "we cannot read your files" is a moat and "we are cheaper" is a coupon.
One coherence check, because your brand is privacy and one feature cuts against it. Client-side encryption protects the sender, good. But webcam snapshots and page-by-page tracking of whoever opens the file is surveillance of the viewer, which is the opposite of privacy from their seat. For a term sheet or a legal file that is a legitimate security feature, but out of context it can make a privacy-first brand wobble. Decide the story on purpose: you protect the sender's document and give the sender proof of who engaged, and say plainly that this is a security tool, not a spy tool. One question: is your buyer paying for privacy, or for control over who sees the doc? Because those two pull the page in slightly different directions.
This is technically strong, but I’d be careful not to lead too much with the stack.
The buyer pain is not really “serverless zero-knowledge file transfer.” It is more direct: DocSend is expensive, and founders still need secure deck/document sharing with analytics, access control, and trust.
The strongest wedge might be early founders, agencies, or small sales teams who want DocSend-style control without paying enterprise-style pricing.
I’d probably test the promise around:
“Secure document sharing with analytics, without the $150/month DocSend bill.”
Then the encryption, biometrics, webcam snapshots, and client-side processing become proof points, not the headline.
If this is still early, I’d focus less on explaining how the browser architecture works and more on finding 20 to 30 people already complaining about DocSend, pitch decks, investor updates, or sales collateral tracking.