Sudip Mani Gautam
Full-stack software engineer and open-source builder passionate about local-first computing, browser-native performance, and liberating everyday productivity tools from predatory subscriptions.
Creator of iCreatePDF, architecting client-side WebAssembly pipelines that process sensitive legal, medical, and financial documents with zero cloud exposure.
A Personal Note to Every User
“When you lock the front door of your home, you don’t mail a copy of your key to a corporation across the globe. Yet for years, the software industry conditioned everyone to believe that merging a contract, compressing an invoice, or signing a tax document required sending the file across the internet into someone else’s cloud storage.
I built iCreatePDF to prove that software can be fast, capable, beautiful, and respectful without asking for your email address, without extracting monthly fees, and without your data ever leaving your own hands. This tool belongs to you as much as it belongs to me.”
Guiding Engineering Principles
Local First, Cloud Never
If a calculation can happen on the user’s processor, routing it through a data center is an architectural failure and a privacy compromise.
No Artificial Paywalls on Utility
Merging two sheets of paper or compressing an invoice shouldn’t cost a monthly subscription. Basic digital utilities belong to everyone.
Radical Auditability
Security isn’t a marketing badge. If you can’t inspect the source code running on your machine, you don’t own your privacy.
Conversations on Building iCreatePDF
Sudip answers frequent questions about architecture, challenges, and the open-source philosophy.
What originally sparked you to create iCreatePDF?
I have always held a deep philanthropic conviction that digital privacy is an essential human right, and that developers carry an ethical responsibility to protect the public. For years, document platforms treated private records as commercial commodities—forcing unverified cloud uploads, demanding recurring subscriptions, and tracking personal files. I believed people deserved complete respect and absolute data sovereignty. With modern browser technologies like WebAssembly, multi-core Web Workers, and WebCrypto, I set out to engineer a free public utility that empowers everyone while ensuring their files never touch an external server.
Why did you choose WebAssembly and client-side processing over a standard cloud backend?
Traditional SaaS companies build backends because backends enable vendor lock-in, recurring subscriptions, and data harvesting. Client-side WebAssembly flips the script. By compiling native C++ and Rust PDF processing engines directly into browser bytecode, we achieve near-instant execution speed without running server farms. This means zero hosting overhead for storage, zero risk of data leaks from our end, and guaranteed privacy for users.
What was the toughest technical hurdle in making 67+ tools work completely in-browser?
Memory management and thread responsiveness. When someone drops a 300MB scanned PDF with hundreds of pages into a browser tab, a naïve JavaScript implementation will instantly choke and crash the tab. We had to architect an asynchronous Web Worker pipeline that streams binary byte arrays, manages ArrayBuffers cleanly, and uses OffscreenCanvas for rendering. The result is that heavy operations run smoothly in the background while the UI remains buttery smooth at 60 FPS.
Why release iCreatePDF under the AGPL-3.0 open source license?
Trust is not something you can demand with a fancy privacy policy statement written by lawyers. You have to prove it with code. Under AGPL-3.0, anyone in the world can inspect our repository, audit every single line of code, run it locally, or contribute improvements. It ensures that iCreatePDF remains forever free, transparent, and owned by the community rather than venture capitalists.
What is your vision for the future of document tools?
We are expanding beyond simple one-off file tools into comprehensive, autonomous workflows. With our new node-based PDF Workflow Builder, users can visually construct complex pipelines—like deskewing scanned pages, running offline OCR, applying dynamic watermarks, and packaging encrypted archives—all executed entirely on their device without a single API key or subscription.
The Technologies That Power the Project
Hand-selected libraries, compilers, and browser APIs utilized to achieve 100% offline document processing.
Near-native speed computation
Type-safe reactive architecture
Underlying document manipulators
Multi-threaded background compute
Hardware-grade client encryption
Lightweight native desktop runtime
Vector stream & font parsing
100% offline optical character recognition
Have an Idea, Feature Request, or Security Audit?
Sudip reads every email and reviews pull requests openly on GitHub. Whether you found an edge case with a corrupted PDF or want to request a new client-side tool, get in touch directly.