HN user

nip

556 karma

Founder of SimplePDF.com

Based in Amsterdam, Netherlands

benjamin [d o t] ee

Posts24
Comments170
View on HN
copilot.simplepdf.com 2mo ago

Show HN: Filling PDF forms with AI using client-side tool calling

nip
60pts29
copilot.simplepdf.com 2mo ago

Show HN: Filling PDF forms with AI using client-side tool calling

nip
7pts1
simplepdf.com 5mo ago

Show HN: I curated 130 US PDF forms and made them fillable in browser

nip
13pts0
commonforms.simplepdf.com 9mo ago

Show HN: Browser-based PDF form fields detection (YOLO-based)

nip
26pts3
simplepdf.github.io 2y ago

Show HN: Fill and sign PDF from any website with a single line of code

nip
16pts2
simplepdf.github.io 2y ago

Show HN: SimplePDF – Embed a PDF editor and annotator in your website

nip
11pts0
simplepdf.eu 3y ago

Show HN: Simplepdf.eu – a browser-based PDF annotator / editor

nip
47pts10
simplepdf.eu 4y ago

Show HN: An Embedded (iFrame) PDF Editor

nip
2pts0
github.com 4y ago

Show HN: I built an open source automation to extract keywords from PDFs

nip
7pts0
simplepdf.eu 4y ago

Show HN: Simplepdf.eu – privacy-focused PDF online editor

nip
10pts1
github.com 4y ago

Show HN: I built an open source automation to collect your bills

nip
10pts1
www.eestipank.ee 4y ago

Experiment with the digital euro illustrated new possibilities for blockchain

nip
2pts0
sixfold.medium.com 5y ago

Why we chose and why we don’t switch away from TypeScript?

nip
1pts0
sixfold.medium.com 5y ago

Doubling our ETA accuracy with machine learning in production

nip
4pts0
sixfold.medium.com 5y ago

Reducing database queries to a minimum with DataLoaders

nip
38pts14
sixfold.medium.com 5y ago

Preparing for the “known” unknown – scaling a service 10x in 30 days

nip
12pts1
www.entsoe.eu 5y ago

System split registered in the synchronous area of Continental Europe

nip
4pts0
www.theguardian.com 8y ago

Meet the professor who says facial recognition ​​can tell if you're gay

nip
2pts1
e-estonia.com 8y ago

Government Cloud: infrastructure as a service

nip
1pts0
techcrunch.com 8y ago

Uber’s European rival Taxify raises $175M led by Daimler at a $1B valuation

nip
4pts2
startupestonia.ee 9y ago

Estonian startup visa

nip
5pts0
www.ft.com 10y ago

China's robot revolution

nip
4pts0
www.theatlantic.com 10y ago

Tying Paris Back Together

nip
2pts0
mashable.com 11y ago

Programming Isn't Manual Labor, but It Still Sucks

nip
3pts0

like that, but (and I might be ignorant) can't you just change it's all in browser to something else and the users would be oblivious?

Excellent question! The answer is simple: we're known on the market, and trusted by our customer for this secure handling of PDFs. Should we decide to change that (unbeknownst to them), we would effectively kill our reputation and the company by extension.

Is it possible to download as an app and disable internet (not sure if it's a feature of any browsers).

Back in the days, SimplePDF used to work offline. However maintaining that in conjunction with our paid customers features (where the online connectivity is mandatory) was too big of a maintenance burden. We decided a year ago to drop this support (silently), and no one has complained since then, confirming our hunch that it is not a high-demand feature.

Thanks! You caught a real bug: the form labels fed to the LLM were mangled. Now fixed: values land in the correct field.

On "what are we trying to solve":

Forms (PDFs, scanned paper) are still everywhere and aren't going away. SimplePDF Copilot exists to make the transition less painful. A few concrete use cases:

- Pre-filling repetitive forms from existing data sources (CRM, EHR, etc. via MCP/RAG). In most industries, employees fill forms by copy-pasting or retyping. With AI + tool calling, most of the form arrives pre-filled and the employee just corrects or adds the missing bits.

- Filling foreign-language forms. If you've moved to a new country, or know someone who has, you've had to fill out forms in a language you don't master.

- Understanding a contract before signing it. "Can I actually trust all the clauses here?" Reading proficiency changed the world by giving people a way to understand what they were signing. This extends it to legalese and odd clauses.

On Claude Cowork:

Different shape, and a different privacy model. Cowork drives a sandboxed virtual desktop: you can't see exactly what it's doing while it fills, and correcting a wrong value means another back-and-forth with the LLM.

Copilot works inside your editor: every change is visible as it happens, you can amend any field with one click, and the document never leaves your browser + it's LLM agnostic: bring your own (local or hosted).

Absolutely not insulting! In fact an excellent question!

Preview was an inspiration when I started SimplePDF, my goal was to make the "Preview" of the web, so that people without a Mac would benefit from a software matching Preview in ease of use and overall polish.

Adobe Acrobat: SimplePDF has "Simple" in the name as the philosophy is to keep it simple (both in ease of use, and features): I don't intend to support everything that Adobe Acrobat does. There's a lot of features that I could build that I intentionally do not, as they would bloat the UI and hard the overall usability. Most people have very simple needs and don't need advanced features (like scripting, etc).

We offer both:

- A privacy-focused PDF editor, free for individuals, used by 200k users monthly: https://simplepdf.com/editor

- The same editor, embeddable into one’s app for companies, with the same privacy guarantees (everything happens in the browser) + the resulting PDF is stored in their own storage (« bring your own storage »).

The majority of our paid customers are in healthcare where privacy is non-negotiable. Co-pilot extends that to the AI world (« bring your own AI »)

What are you using the PDF editor for?

I tried to make it clear with the popup message that appears when you start chatting: "Public demo. Use sample data only. Messages are processed by the selected AI provider."

But you're right that it's not as evident as I wanted to, I'm making a small copy update to make it clearer: "Public demo. Your chat messages leave your device and are sent to the selected AI provider. Use sample data only."

(Since there's support for local models, the popup is only displayed when NOT using your own model)

Thanks!

EDIT: the copy update is live, thanks again!

Just to be clear, this is a technical demo showing what's possible with client-side tool calling + local models: LLM-assisted form filling where no document data has to leave the user's machine.

Use cases range from:

- Filling foreign-language forms

- Navigating a contract before signing: "can I trust ALL the clauses here?"

- Pre-filling repetitive forms from existing data sources (CRM, EHR, etc. via MCP/RAG)

Copilot is designed to be embedded; our customers ship it white-labeled inside their own products.

Just to be clear, this is a technical demo showing what's possible with client-side tool calling + local models: LLM-assisted form filling where no document data has to leave the user's machine.

Use cases range from:

- Filling foreign-language forms

- Navigating a contract before signing: "can I trust ALL the clauses here?"

- Pre-filling repetitive forms from existing data sources (CRM, EHR, etc. via MCP/RAG)

Copilot is designed to be embedded; our customers ship it white-labeled inside their own products.

Agree on Smart-ID but the answer is to fix those flaws, not to replace the entire approach with one that depends on Google Play Integrity verdicts that even the German architects admit they can’t fully trust.

SIM-based solutions on their way out is a non-issue. For eSIM to support that use case, political will only is needed: the EU got Apple to abandon the lightning cable, this is not any different.

In light of all of these shortcomings with platform attestation, why go with the eIDAS 2 wallet approach at all? eIDAS 1 already solved this with Mobile-ID (SIM-based, no Google/Apple dependency) and Smart-ID (server-side key management with minimal platform reliance). What does the wallet model give you that justifies this level of dependency on two American corporations’ proprietary backends?

Especially considering that mobile-ID has been around since 2007.

WebMCP Proposal 5 months ago

The web was initially meant to be browsed by desktop computers.

Then came mobile phones with their small screens and touch control which forced the web to adapt: responsive design.

Now it’s the turn of agents that need to see and interact with websites.

Sure you could keep on feeding them html/js and have them write logic to interact with the page, just like you can open a website in desktop mode and still navigate it: but it’s clunky.

Don’t stop at the name “MCP” that is debased: it’s much bigger than that

The reason is simple: the TUI is the fastest way to provide any form of UI over the file system.

Want to do that with web technologies? You’ll need a browser AND a server or build an app using electron or tauri.

I still haven't figured out MCP or how/why to use them or why to bother. You run servers. I guess. It's too complex for my smol brain to understand

I know this is self-deprecating humor, but you do NOT have a smol brain: MCP servers are not as needed anymore now that Claude Code supports "Skills". They are also very token hungry as their spec is not lazy-loaded like the skills.

It was / and still is very useful if you collaborate with other engineers or want to perform operations in a non-stochastic fashion.

MCP servers are a way to expose a set of APIs (openAPI spec) to an LLM to perform the listed operations in a deterministic fashion (including adding some auditing, logging, etc). LLMs are fine-tuned for tool calling, so they do it really well and consistently.

Examples:

- Documentation / Glossary: MCP server that runs somewhere that reads a specific MD file or database that is periodically updated: think "what are my team members working on" / "let me look up what this means in our internal wiki".

- Gating operations behind authentication: a MCP server that is connected to your back office and allows you to upgrade a customer's plan, list existing customers, surface current. Super useful if you're a solo-founder for example.

It’s easy to pick on logic that failed and for which you have a very detailed and great post mortem write-up.

Yet you omit to acknowledge that the remaining 99.99999% logic written that powers Cloudflare works flawlessly.

Also, hindsight is 20/20

We do something similar that we call « Office a la Zoom »:

Two times a week, the weekly standup is extended by an hour, from 15min to 1h15.

People are welcome to jump in and out of that open zoom that acts as a water cooler corner: any topic goes, from work to personal hobbies, etc

We’re fully remote (US / EMEA / APAC)

Indeed very easy to code!

My point is about the need for a spec of this mechanism: without a spec, every company / org will roll out their own and result in 500 flavors of the same concept.

That’s where MCP shines: tool calling and tool discovery is already 1.5 years old (an eternity in ai land).

The MCP spec ensures that we can all focus on solving problems with tool calling rather than wasting time in cobbling together services that re not interoperable (because developed without a common spec / standard)