Open on ProductHunt

Quietbench

Free, no-signup dev tools that run entirely in your browser

Web AppProductivityDeveloper ToolsGitHub
4votes7commentsLaunched 23h agoWebsite

By Aniket Saini

Sonnet 4.6 fasst Produkt + Kommentar-Tonalit盲t in vier S盲tzen zusammen (~0.5 ct, einmal pro Post).

About

Most bookmarked dev-tool sites get slower and more ad-heavy over time, or start gating basic features behind a signup. Quietbench is a small suite of the utilities I reach for most often - JSON formatter, regex tester, cron builder, WCAG contrast checker, and API request tester - built to stay fast, free, and signup-free. Everything runs entirely client-side in your browser. No accounts, no data sent to a server, no ads. Built with React, Vite, and TypeScript, deployed on Cloudflare Pages.

Top comments4 of 7

  • [REDACTED]路26h ago0
    Hey everyone 馃憢 I built Quietbench because I had a handful of bookmarked utility sites - JSON formatter, regex tester, that kind of thing - that kept getting slower, more ad-heavy, or started gating basic features behind a signup over time. So I built my own small suite: JSON formatter with a tree view, a regex tester with live highlighting and plain-English explanations, a cron builder that shows your next 5 run times, a WCAG contrast checker, and a lightweight API request tester. Everything runs entirely in the browser - no accounts, no data sent anywhere, no ads. Built with React, Vite, and TypeScript, deployed on Cloudflare Pages. This is very much a solo side project, and I'd genuinely love feedback - especially anything that feels broken, confusing, or missing. What utility would you want added next?
  • [REDACTED]路11h ago1

    the all-client-side approach is genuinely nice鈥攏o waiting on a server roundtrip just to format some JSON, and nothing leaks anywhere. love that the regex tester shows matches in real time as you type.

  • [REDACTED]路12h ago1

    With everything running client-side, are there any size limits I should expect on the API request tester, or does it fall back gracefully when a response gets too large to render smoothly in the browser?

  • [REDACTED]
路
21h ago
1

the all-client-side approach is a really thoughtful choice, especially for tools like these where you don't want your test data leaving the machine. love seeing utility sites that respect that.