How I Built ToolHub: A 138-Too... Note

How I Built ToolHub: A 138-Tool Static PWA That Stays Sub-Second

The author recently published a full architecture retrospective on building ToolHub, a suite of 138 in-browser web utilities that prioritize cleanliness, privacy, and zero bloat. The site is designed to be sub-second fast and fully offline-capable, with key engineering tradeoffs and technical decisions that enable these features. One of the key architectural highlights is the use of Next.js Static Export, which allows for a 100% static export model hosted on edge CDN, resulting in zero server maintenance and ultra-low time to first byte. This approach also enables infinite scaling, but requires that all dynamic content execute strictly on the client side in browser memory. The author also implemented a custom Service Worker caching strategy, which includes stale-while-revalidate for static assets and network-first for HTML document navigations, ensuring complete offline capability across all tools once cached. Additionally, the author developed a programmatic SEO engine that generates static tool pages with full JSON-LD structured data and automated internal linking meshes, all baked into static HTML at build time. The site also features a zero-CLS ad strategy, which prevents layout shifts by reserving explicit fixed-height layout slots for ad units before they load. The author has made the ToolHub site available for users to try, and has also published a full engineering deep-dive on their blog, where they share more details about the technical decisions and tradeoffs that went into building the site. The author is seeking feedback and suggestions from users, and is open to hearing thoughts on the architecture and ideas for new tools. Overall, the ToolHub project demonstrates a range of innovative technical approaches to building fast, offline-capable, and privacy-first web applications.