Week 1 Update: What happened after I launched a privacy-first PDF tool
One week ago I posted about Aservus — a free PDF toolkit that processes files locally in your browser so your files never get uploaded to a server.
I want to share what has actually happened since then because I think the data is useful for anyone else building a free tool and trying to grow it without a budget.
What I launched with:
23 tools across PDF editing, file conversion, and utilities. Everything free. No account required. No watermarks. No daily limits. Most operations run entirely in the browser using WebAssembly.
The one line that changed everything:
I tested a lot of ways to describe Aservus. The one that consistently made people stop and pay attention was this:
"Most PDF tools upload your files to a server. Aservus doesn't."
That single sentence does more work than any feature list. People immediately understand why it matters. They have uploaded contracts, invoices, passport scans, and medical documents to iLovePDF and Smallpdf without ever thinking about where those files went. The moment you name that anxiety, they feel it.
Victor Okefie put it better than I could in the comments of my last post: "You're not selling encryption. You're selling the removal of a background anxiety they didn't know they had." That is now how I think about the entire product.
What I am focused on this week:
Getting Aservus in front of people who are already frustrated with the upload model. That means writing on platforms where developers and privacy-conscious users already spend time. Dev.to, Hashnode, Medium. Answering questions on Quora where people are actively searching for PDF tool alternatives. Submitting to directories where people discover new tools.
No paid ads. No budget. Just distribution.
The question I am sitting with:
For those of you who use PDF tools regularly — what would actually make you switch from whatever you are using now? Is it privacy? Is it the fact that it is free with no limits? Is it the number of tools available? Or is it something else entirely?
I am genuinely trying to understand what makes someone switch, not just try something once. Would love honest answers from this community.
Aservus is at aservus.com if you want to try it before answering.
Totally get this. I think privacy is the main driver, but also friction-free use, no account, no watermarks matters a lot. Curious, have you seen certain tools get noticeably more clicks just from emphasizing the “never uploads” line?
That’s a really sharp way to frame it, “verifiable honesty” hits. Makes sense why it outperforms feature lists, especially when users can literally confirm it themselves.
I like how you broke it into layers too: privacy gets the click, frictionlessness keeps them. Curious, have you thought about making that “verifiability” even more explicit on the page (like a quick visual or prompt to check DevTools)?
This is a great question Bambi_, that's actually on our roadmap — we've been thinking about a small "Verify it yourself" section on the tool page that shows a live network monitor indicator while a file is being processed. Zero outgoing requests, visualized in real time.
The challenge is making it accessible to non-technical users. Most people don't know what DevTools is. So we're exploring something simpler — maybe an animation that shows the file staying inside the browser boundary, no arrows going out. Visual proof without requiring any knowledge of dev tools.
If you have thoughts on what that would look like for a non-technical audience, genuinely curious. You've framed the trust problem better than most of our own internal discussions have.