I've spent the last 2 months building Notoo - a browser workspace (docs, markdown, code, drawings, API requests behind one file tree) plus 31 PDF and image tools. Launching on Product Hunt Aug 9th 2026.
A while back I needed to merge two PDFs—nothing dramatic — [a signed contract and an ID scan]. I did what everyone does: searched, clicked the first result, and then sat there with my finger over the upload button.
I didn't know who ran that site. I didn't know where the file would sit afterward, or for how long. I uploaded it anyway because I needed the file merged, and I felt uncomfortable about it. Then it added a watermark and told me the third file needed an account.
Around the same time I had a different, smaller annoyance. I'd open a notes app for a quick thought, then a second tab for a code snippet, a third for something that needed real formatting, a fourth to sketch what I meant. One idea, four apps, four logins, and nothing where I left it.
Both problems had the same shape: my computer could obviously do this work, and I was renting someone else's server to do it instead.
So I built Notoo. It's a workspace where the file extension picks the editor — write a doc, drop in code, sketch a diagram, all in one file tree — and 31 PDF and image tools sitting next to it. All of it runs inside your browser tab. Your files never leave your machine, because there's no server for them to leave to. No account, no page limits, no watermarks.
It's free. It can afford to be — nothing I built costs me anything when you use it.
Launching on Product Hunt on Aug 9th 2026. Would love it if you broke it: notoo.app
And if you've built something local-first - how did you ever get people to believe the "nothing is uploaded" part?
Links: notoo.app · tools.notoo.app
The local-first approach is really interesting. i especially like the idea that the same problem sits behid both the privacy issue and having to jump between different apps. curious now that Notoo is launching , what do you expect to become the biggest time sink for you outside of actually building the product?
The privacy angle feels especially interesting because the product is asking users to trust a claim they can’t necessarily verify just by using it.
Curious what you think will actually make someone believe “nothing is uploaded” rather than simply take the claim at face value?