Asad M.

I've been vibecoding all year, and the thing that kept biting me wasn't bugs it was drift: the gap between code that works and code that's actually production-ready.

So I built DriftDetector: https://drift.reweaver.ai

Free, no signup, ~a minute:

• Paste any GitHub repo URL (public or private)

• It scans nine dimensions of production readiness security, accessibility, reliability, design consistency, AI code governance, and more

• You get one Production Drift Ratio (0 1, Low to Severe), exact file/line locations, which commit opened each gap, and time-to-fix estimates

One thing we didn t really have doubts about when launching WIT was the main use case.

Then the Product Hunt community came to check the product out and some of the feedback made us look at that use case from a different angle.

We run 10+ image models plus Veo 3.1 and Seedance 2.0 behind one studio. Until recently every generation record stored the prompt and the output file and nothing about which model produced it. When there was one model that was fine.

With a router it means every quality complaint ends in a shrug. Someone says the face drifted between the image and the video, and I can't tell them whether that was the model, the seed or the upscale step, and I can't reproduce it either because the router might pick differently next time. So the report goes in a doc and dies there.

Writing model, version and the reason the router picked it onto every output has done more for quality than any prompt work we did this year. Not because the models got better. Because complaints stopped being about the product in general and started being about one model in one situation, which is a thing you can actually fix.

The open question for me is whether users should see it. I want to show the model on every output. My cofounder thinks it just gives people something to argue about and moves the conversation off the work. If you route across models, do you expose that or keep it internal?