I built a 31-tool utility platform solo — here's the architecture behind it
Over the last several months I've been building Tools1Hub, a free online toolkit that now spans PDF editing, image conversion, developer utilities, file conversion, and a newer "Data Studio" category. Here's how it's put together, and a few problems I had to solve along the way.
The stack
Frontend: Next.js, deployed on Cloudflare Pages
Backend: Node/Express on Render's free tier, for tools that need real server-side processing (scraping, price tracking, SEO monitoring)
SEO: a config-driven architecture — a single site-config.ts drives metadata for every tool page instead of hand-authoring dozens of blocks
The two-file pattern
Every tool follows the same structure: a server-rendered page.tsx that owns SEO/metadata, paired with a "use client" component that owns interactivity. This kept 31 tools consistent without turning into copy-paste chaos, and made it trivial to onboard new tools quickly since the pattern is identical every time.
Data Studio: the newest category
The original tools were mostly stateless, one-shot conversions (convert this PDF, resize this image). The Data Studio category is different — it's built around a shared lib/data-studio/ engine and includes:
Data Pipeline Studio — clean and transform messy datasets
Competitor Price Tracker — monitor product prices over time
Currency/Crypto Rate History Charter — visualize historical rate data
Website/SEO Change Tracker — get notified when a page or its SEO signals change
These tools need persistent state and repeated scraping, which meant a different backend shape: single-route-per-tool conventions, rate limiting, and an in-memory TTL cache to keep API quota usage under control on a free-tier backend.
Lessons learned
A config-driven SEO layer pays for itself fast once you're past ~10 pages
Consistent file patterns matter more for velocity than clever abstractions
Free-tier backends force you to get serious about caching early, not later
Still actively expanding this (new Data Studio tools, ongoing SEO work). Would love feedback from anyone who's built something similar, or has SEO/backend-quota lessons to share.
Top comments (0)