ToolNest is 134 free tools — calculators, converters, PDF utilities, developer helpers — and there is no backend behind any of them. No server, no database, no API, no accounts. Every tool runs entirely in the visitor's browser. Here's the architecture that makes that possible, and what it costs.
One page per tool, generated not hand-written
134 hand-written HTML pages would be unmaintainable, so the site is generated: a single build script turns a tool registry (name, category, inputs, formula, copy) into static pages. Adding a tool means adding one registry entry and rebuilding. The generated pages share one layout, one stylesheet and one script bundle, which is why the whole site feels consistent despite its size — consistency is a build property, not a discipline problem.
Client-side everything, by design
Every calculation happens in JavaScript on the page. That started as a simplicity choice and became the product's core promise: your salary, your weight, your PDF never leaves your device, because there is nothing for it to phone home to. The trade-off is real — anything that needs a server (live exchange rates, file storage, accounts) simply doesn't exist on ToolNest, and some tools are less powerful than their server-backed rivals. The privacy guarantee is worth more than the missing features.
Performance as a feature, not a metric
A calculator page that takes three seconds to become usable has already failed its user, who arrived mid-task with a deadline. The budget we hold: pages under 100KB of critical resources, no framework, no web fonts on tool pages, scripts deferred. Lighthouse scores stay green not because we chase them, but because a slow calculator is a contradiction — the whole point is the answer, fast.
Search is the hard part
Static sites give up live search. ToolNest's answer is a generated search index: a small JSON file built at deploy time listing every tool with its keywords, searched client-side as you type. It costs a few kilobytes and zero requests. The same trick covers the sitemap — generated, not computed — which matters when you want 134 pages indexed without a crawler budget.
What breaks at this scale
Three things, in practice. First, deploy size: 134 pages plus assets eventually trips hosting upload limits, so the build now splits output and the deploy order is planned, not assumed. Second, consistency drift: a fix applied to one generated page must be applied in the generator, or it silently reverts on the next rebuild — every "quick edit" to a live page is a bug waiting to happen. Third, the registry itself: at 134 entries, a typo in one tool's metadata ships to production unless the build validates every entry before generating — so it does, and the build fails loudly on bad data.
The honest bit
Zero backend is not a virtue in itself; it's a trade. You give up accounts, saved state, live data and server-side anything. What you get back is a site that costs almost nothing to run, loads anywhere, keeps nothing about its visitors, and can be rebuilt from one script on any machine. For a tool that answers a question and gets out of the way, that trade is the right one — 134 times over.
The site itself is at https://toolnest-xi-silk.vercel.app — 134 tools, free, no sign-ups, everything in your browser.
Top comments (0)