Aservus
Free PDF tools that never upload your files
Two Weeks in — here's what building Aservus taught me about privacy-first products I launched Aservus (aservus.com) a month ago. It's a suite of 23 free PDF tools that run entirely in your browser. The core idea: your files should never have to leave your device just to be merged or compressed. Here's what I've learned in month one: 1. Privacy is a feature people actually care about.
The #1 thing people mention is "I was worried about uploading my documents." We solved that with WebAssembly — files never touch our servers.
2. Free + no sign-up is hard to compete against. We're up against iLovePDF, Smallpdf, Adobe. Our angle: they upload your files. We don't. That's the differentiator.
3. Getting the first backlinks is the hardest part. We're on Sourceforge, SAAShub, Product Hunt, Capterra. Working on editorial links now. Still very early.
Would love feedback from IH on the privacy angle and how to grow an audience around a free tool with no paid tier. https://aservus.com
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.
-
1
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?
-
1
Bambi_, yes — and the data is pretty clear on it. When I changed the hero description on the homepage from a feature list to just "Most PDF tools upload your files to a server. Aservus doesn't." the time-on-page improved noticeably. People stopped and read instead of bouncing immediately.
I think the reason is that "never uploads" is not a feature claim, it is a trust signal that arrives before the user has to do anything. They do not need to try the tool to believe it. They can verify it themselves by opening DevTools and watching the network tab while processing a file. Zero outgoing requests. That kind of verifiable honesty converts better than any feature list because it removes doubt at the exact moment doubt is highest, which is before the first click.
The friction-free angle you mentioned is the second layer of the same thing. No account means no commitment. No watermarks means the output is actually usable. Together they remove every reason to hesitate. Privacy gets people to try it. Frictionlessness gets them to keep using it.
-
1
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)?
-
1
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.
-
-
-
I want to share something I built and the thinking behind it.
A few months ago I was using iLovePDF to compress a contract I needed to send. It worked fine. Then I thought — wait, I just uploaded a sensitive legal document to a random server in Europe. Do I know what happens to it there? No. Did I read their privacy policy? No.
That bothered me. So I started looking for a PDF tool that processes files locally. I could not find one that was both free and had all the tools I needed. So I built one.
It is called Aservus — https://aservus.com
Here is how it works technically. Most operations use WebAssembly compiled libraries running entirely in the browser. When you merge or compress a PDF, the processing happens on your device using your CPU. The file never touches a server. The only exception is complex conversions like PDF to Word where local processing is not yet technically feasible — those go through a server but are deleted immediately after.
What I built: 23 tools total — PDF merge, split, compress, protect, sign, watermark, rotate, repair, PDF to Word, Word to PDF, PDF to Excel, Image to PDF, PDF to JPG, HTML to PDF, AI Paraphraser, QR Code Generator, Word Counter, Email Extractor, and more.
Everything is free. No account required. No watermarks. No daily limits.
What I have learned so far: Privacy is the message that resonates most. When I describe Aservus as "the PDF tool that never uploads your files" people immediately understand the value. That single sentence does more than any feature list.
The hardest part was not building the tools — it was getting anyone to know the site exists. Which is why I am here posting on Indie Hackers today.
If you work with PDF files and care about privacy, I would genuinely love your feedback. What tools are missing? What could be better? What would make you switch from whatever you are using now?
Happy to answer any technical questions about the WebAssembly implementation. I am still working on the platform to make it better for the users as they grow and I am always looking at the data and their input that they share with me as well.
-
2
this is clean — and the local processing angle is a really strong trust signal
one thing i’d look at is how quickly a new user understands what makes this different from tools like ilovepdf or smallpdf
right now it feels solid, but highlighting that distinction more immediately could help with conversion
-
1
Thank you Brady for showing interest, that is exactly the feedback I needed to hear. You are right — the distinction is there but it is buried. I am working on making "your files never leave your device" the very first thing a new visitor understands, not something they discover after reading. The trust signal only works if it lands in the first three seconds. Appreciate you being direct about it.
-
-
1
The insight: "Privacy is the message that resonates most." Not because people are paranoid, but because they've uploaded a hundred documents to random servers and never once thought about where they went. You're not selling encryption. You're selling the removal of a background anxiety they didn't know they had.
-
1
Victor, this is honestly the best description of what Aservus does that I have ever read and I built it. "The removal of a background anxiety they didn't know they had." That is exactly it. People have uploaded hundreds of sensitive documents to random servers and never once stopped to ask where those files went. I am going to use this framing in how I talk about the product going forward. Thank you for articulating something I was feeling but couldn't express this clearly.
-
1
That's it Zain, That framing already existed in the product, you just hadn't named it yet. Most founders search for the right feature to add. You already built the right feeling. Now you just have to say it out loud
-
-
-
1
Very nice indeed. I have to agree that privacy is key too. Does the document keep the reference linking when you convert the word doc ? Are any links in the doc live? I know one of the biggest things for me was when I used to create a tone of training documents for students is the linking and the ability to create navigation to different sections witin the document. To be honest as far as I can tell the tool seems fantastic.
~Robert D
-
1
Thankyou Robert, great question. When converting PDF to Word, Aservus preserves hyperlinks that are embedded in the PDF structure. Internal navigation links (bookmarks within the document) depend on how the original PDF was created — if they were exported from Word originally, they typically survive the round trip. If the PDF was scanned or printed to PDF, those navigation structures won't be present to recover. For training documents specifically, I would recommend starting from the original Word file if you have it and using our Word to PDF tool to create a clean version. Happy to answer any other questions.
-
2
Thank you so much fro answering my question. I appreciate it and keep up the outstanding work. :)
-
-
2 Comments
What I like:
— WebAssembly means no file upload. That's not just privacy, that's speed.
— Free + no sign-up removes every barrier to entry.
— You're competing with giants (Adobe, Smallpdf) but you have one thing they don't: trust.
Quick questions from someone who's watched similar products grow:
1. How are you planning to monetize? You mentioned 'no paid tier' — but servers cost money.
2. Have you considered a white-label version for businesses? Companies would pay for privacy-first PDF tools.
3. What's your strategy for SEO? 'Free PDF tools' is competitive, but 'privacy-first PDF' is less crowded.
The backlinks struggle is real. Have you tried reaching out to privacy-focused blogs or newsletters? They love this angle.
Keep going. This has real potential.