Vibe Check: I Built a Free Comments System in an Afternoon

My wife wanted comments on our blog.

We run a family blog — part travel journal, part personal writing — and she wanted readers to respond. Totally reasonable. But we’re on Jekyll, and Jekyll doesn’t have a native comments system. Disqus is bloated and ad-supported. Paid solutions feel like overkill for a personal blog. And rolling my own per-site meant building the same thing three times.

So I built one tool that works across all of them. Built it in an afternoon — in between chores and hanging out with my daughter. It’s free.

The Problem Static Sites Have Always Had

Static site generators are great — fast, cheap to host, low maintenance. But no backend means no comments.

The standard answer was Disqus. It works, but it tracks your users, injects ads, and adds page weight you don’t want. Cleaner alternatives cost money, which is hard to justify for a personal blog you’re just trying to keep alive.

The other path is building your own — which I’d normally do once, for one site. Repeating that across three projects is the kind of friction that used to mean “don’t bother.” Not because it was impossible. Just because the cost was high enough that most people talk themselves out of it.

That calculation has changed. Which is kind of the whole point.

What I Actually Built

The tool is live at comments.managertools.xyz.

Sign in with Google. Create a project — one per site. Get an HTML snippet. Drop it in. Done.

Visitors can log in with Google to leave a comment, drop a heart, or subscribe. No database to manage, no server to babysit. Runs on Cloudflare’s free tier, so the operating cost is zero at normal traffic volumes.

Is it feature-complete? No. Will it scale to a million users? Also no. But it solves the problem I had, it works today, and you can use it for free.

What Vibe Coding Actually Is (And Isn’t)

I built this by vibe coding — steering an AI through the implementation with natural language, letting it write the code while I handled the judgment calls.

The speed is real. What would have taken two or three days two years ago happened in an afternoon. That’s not nothing.

But it didn’t replace the thinking. I still made architecture decisions. Thought through the data model. Considered the security implications of anything that touches user auth and stores public content. The AI wrote most of the code. I was responsible for all of the judgment.

If you know what good looks like, vibe coding lets you move fast. If you don’t, you ship something broken fast. The experience still matters — it’s just applied differently now.

The Part Nobody Warned Me About

Building the tool was the easy part.

I’ve spent 13 years getting better at building things, and honestly? Building is kind of easy now — at least for a well-scoped problem like this. The hard part turned out to be something I never had to think much about before: how do you tell people something exists?

This tool solves a real problem. It’s free. And I genuinely don’t know how to get it in front of the people who’d use it. I’m not frustrated about that — I’m just noticing it. The constraint shifted and I wasn’t ready for it.

For most of my career, the bottleneck was building. Now that’s not true in the same way. What’s left is distribution, audience, discoverability — all the stuff that has nothing to do with writing code. And I’m a beginner at that part.

I think a lot of builders are here right now and not quite naming it. We’re producing faster than we’re communicating. Things we ship disappear — not because they were bad, but because we never solved the last mile.

I’m still figuring it out. I don’t have an answer. But I think naming it is probably the first step.

Give It a Try

If you have a static site and want comments without paying or building your own, try it: comments.managertools.xyz. Free, five minutes, needs a Google account.

And if you’re a builder — what have you been putting off because it felt like too much to build? That math may have shifted more than you think.