I wanted to build a side project that:
- Costs almost nothing to run
- Requires minimal maintenance
- Could eventually generate passive income
- Actually provides value to people
A few weeks ago, I launched Toolpod — a collection of 48 browser-based developer tools plus a directory of 110+ free public APIs. Here's how I built it using AI-assisted development, and what I learned along the way.
The Idea
Developer utility sites have been around forever. JSON formatters, Base64 encoders, UUID generators — we all use them. But most are covered in ads, require sign-ups, or send your data to a server.
I figured I could build a cleaner version:
- All tools run client-side (your code never leaves your browser)
- No sign-ups
- Minimal ads (once AdSense approves)
- Multiple tools = multiple SEO entry points = organic traffic over time
The Stack
I kept it simple and cheap:
- Next.js 14 with static export
- Tailwind CSS for styling
- Firebase Hosting (free tier — 10GB storage, 360MB/day bandwidth)
- Domain: toolpod.dev via Porkbun (~$12/year)
Total monthly cost: ~$21 (Cursor subscription + domain amortized)
Since everything is statically exported, there's no server to maintain. Firebase's free tier is more than enough for a utility site.
The Method: Cursor + Claude
Here's where it gets interesting. I didn't write most of this code manually.
My workflow:
- Describe what I want to Claude in detail
- Ask it to generate the code
- Paste into Cursor or let Cursor's AI assist
- Test, tweak, repeat
For example, here's roughly what I told Claude for the hash generator tools:
"Build a SHA256 generator page with these features:
- Input text area
- Encoding selector (UTF-8, UTF-16, Hex, Base64)
- Output format selector (hex lowercase, hex uppercase, base64)
- HMAC support with secret key input
- Use Web Crypto API
- Match the styling of my existing pages"
And it just... worked. The AI understood the context, generated the component, and I had a working tool in minutes.
What I Built
48 tools across categories:
- Formatters: JSON, SQL, CSS, JavaScript, XML, YAML
- Encoders/Decoders: Base64, URL, HTML entities, Base32
- Hash Generators: SHA256, MD5, SHA3 with full encoding options + HMAC
- Converters: JSON↔YAML, JSON↔XML, CSV↔JSON, TOML↔JSON
- Generators: UUID, QR codes, passwords, cron expressions
- Text Tools: Diff checker, word counter, case converter, slug generator
- And more: JWT decoder, regex tester, color tools, chmod calculator
Plus an API directory:
110+ free public APIs organized by category (finance, weather, sports, AI, etc.). Each entry shows auth requirements, CORS support, and links to docs.
What Worked
1. AI-assisted development is a multiplier
I'm a data engineer by trade, not a frontend developer. Without AI assistance, this would have taken weeks. With it, I had a working site in a weekend and spent the following days polishing.
2. Static sites are underrated
No servers to maintain. No databases to back up. No costs that scale with traffic. For a utility site, this is perfect.
3. One tool = one SEO opportunity
Each tool page targets specific search terms ("json formatter online", "sha256 generator", "uuid generator"). Over time, these compound. I'm playing the long game.
What Didn't Work
1. Reddit hates new accounts
My first few posts got auto-removed by spam filters. If you're planning to promote on Reddit, build some karma first by answering questions before posting links.
2. AdSense takes forever
Still waiting on approval. Applied weeks ago. The site has all the "right" things (privacy policy, about page, real content), but Google moves slow.
3. Some tools are harder than expected
The basic stuff (JSON formatter, Base64) took minutes. But tools with edge cases (cron expression builder, JWT decoder with all algorithms) required more iteration.
The Numbers
- 48 tools built
- 110+ APIs in the directory
- ~$21/month total cost
- $0 in revenue (so far — waiting on AdSense)
- ~1 weekend for initial build, plus a week of polishing
What I'd Do Differently
Start with fewer tools. I could have launched with 10-15 tools and added more over time. Shipping fast > shipping complete.
Set up analytics earlier. I added Google Analytics late and missed early traffic data.
Write content from day one. Each tool page has educational content now ("What is SHA256?", "Common use cases"), but I added it later. Should have been there from the start for SEO.
What's Next
- Wait for AdSense approval
- Monitor Google Search Console for indexing
- Keep building karma on Reddit/DEV.to
- Add more tools based on what people actually search for
- Maybe open-source it?
Try It Out
If you want to check it out: toolpod.dev
If you're thinking about building something similar, my advice: just start. The AI tools available today make it possible to ship things that would have taken 10x longer a few years ago.
What side projects are you working on? I'd love to hear about them in the comments.
Top comments (3)
Thank you very much for your contribution and interesting insights. Yeah, same experience with reddit.
Tipp: You could make it installable as a PWA.
My current site project is a headless CMS for Firebase, simular to FireCMS, but simpler and other usefull stuff on how I'd imagine a good CMS.
Thanks! The PWA idea is solid and it would be useful for folks who want quick access without opening a browser tab every time. Adding that to the list.
What's your CMS project? Always curious to see what people are building on Firebase.
Some comments may only be visible to logged-in visitors. Sign in to view all comments.