BrokenRepo gives you a real, multi-file MERN codebase with a genuine bug hidden inside. No skeleton code, no upfront hints. You read the code, form a hypothesis, fix it, and run tests to confirm. Built because most of us can solve DSA problems but freeze at a real error message, and Amazon's 2026 OA now tests exactly this.
Which Vercel product did you use? What new capability did it give your team, and how did that shape the product you launched?
Maker
I used Vercel to host the entire frontend, deployed straight from GitHub. Since I'm building this alone and not spending on infrastructure right now, having deploys handle themselves through Vercel's Git integration meant I could focus on the actual product, the sandbox execution, the challenge content, the debugging flow, instead of managing servers or deployment pipelines myself. I also used Vercel's domain connection to point my custom domain, brokenrepo.tech, directly at the deployment, and I'm using Vercel Analytics alongside Umami to track real visitor behavior since launch.
Report
Maker
📌
I noticed something about myself and a lot of developers I know. We're comfortable using AI tools to write code fast, but the moment a real app throws an error, we freeze. DSA skills don't help much when you're staring at a stack trace in an unfamiliar codebase.
This isn't just a personal gap either. Amazon's 2026 OA has started including a dedicated debugging section alongside DSA rounds. Companies are testing for this directly now.
So I built BrokenRepo. You get a real Project with multiple files and a genuine bug hidden inside, described only by its symptom. No hints unless you ask. You read the code, form a hypothesis, fix it, and prove it with real tests running in a live sandbox.
It's free, no signup needed to try your challenge. This is v1 and I'd love honest feedback, especially if something breaks along the way.