Show IH: I built a suite of dev tools that works 100% in the browser (Zero backend)
Hey IH,
I got tired of the friction involved in simple daily tasks. Why do I have to wait for an "upload" and "server processing" just to resize a PNG or format a JSON file? Most of these tools are either covered in ads, hidden behind a "Pro" paywall, or just plain slow.
I wanted something that feels like a native app but lives in the browser.
So I spent the last few weeks building noserver.app.
The concept is simple: Everything runs 100% on your hardware.
Instead of sending your data to a server and waiting for it to come back, I used WebAssembly (WASM) and the Canvas API to do all the heavy lifting directly in your browser.
The result:
Instant: No upload/download wait times. It processes as fast as your CPU allows.
No limits: No "3 files per day" or "10MB limit" nonsense.
No friction: No login, no "accept cookies" banners, no bloat. Just the tool you need.
The Stack:
I went with Next.js 15 and Tailwind v4. Honestly, using v4 was a vibe—the build speeds and the new CSS-first config made the dev experience actually enjoyable for once.
I shared this yesterday and got my first 17 visitors, which was a cool little "proof of concept" for me.
I’m looking for two things:
What’s a tool you use that feels unnecessarily slow or bloated? I want to add more modules.
Any feedback on the UI? I tried to keep it as minimal as possible to stay out of the way.
Check it out: https://noserver.app/
Zero-backend devtools are underrated, the UX win is instant trust and no signup friction. One thing that bit me on browser-only tools was large files, persistence, and sharing state across devices, so it may be worth deciding early which jobs stay fully local and which might eventually need an optional sync layer. Curious what part was hardest to keep client-side.
Zero-backend browser-only dev tools is a compelling distribution play — no infra costs, instant load, and users can actually trust what they're running since it's all client-side. The privacy story almost sells itself for sensitive developer workflows.
The challenge with browser-only tools: you're limited on what persistent state and config you can maintain. For AI-powered features in the browser, the prompt engineering layer becomes critical — if the prompt is hardcoded or vague, output quality is inconsistent across different inputs. I built flompt to solve exactly that: a visual prompt builder that runs entirely in the browser (SPA, no backend required for the builder itself) and decomposes prompts into 12 semantic blocks. Same philosophy as your stack — all the power, locally, in the browser.
A ⭐ on github.com/Nyrok/flompt would mean a lot — solo open-source founder here 🙏
Great project! I'm also launching LinksWatcher today to help affiliates track 'Zombie Pages' via AI. It's a tough day at #139 but we're hanging in there! Good luck with your growth.
Love thiss. running everything locally and cutting out the upload/paywall nonsense is such an underrated angle, feels way more respectful of users’ time and privacy. Great idea and great work!!
Love the zero-backend approach. The "no upload, no limits"experience is exactly how dev tools should feel. JSON/YAML converters and JWT decoders would be great additions — every online one I find is covered in ads.
I’m planning to add a few more modules this weekend, but I’d rather build something people actually need instead of just guessing.
If there’s a tool you use that feels clunky, slow, or forces you to create an account for no reason - let me know. I’ll try to 'noserver-ify' it. Also, would love to hear any brutal feedback on the current UI!