Why I built Decker

Hi, I'm Jin.

When the pandemic hit in 2020, many businesses and public places closed. My kid was two years old, and I had to choose between continuing my business and taking care of him. I chose to take care of him. I spent the next five years as a full-time dad. I still think it was the right choice.

After five years, I tried to find work again as a technical product manager. It did not go well. Not many companies wanted someone who had been away for five years. AI was growing fast, and tech companies were hiring less, or not at all.

So I decided to build something of my own.

In the summer of 2025, I found Claude Code and started using AI to build software again. I also noticed that many people were getting stuck before they could even install it, so I made a small website called getclaudecode.com to help them get started.

Then I started building my own products.

The code was the easy part.

AI wrote the code quickly. I expected the rest of the work to get easier too: running the app, checking that it worked, finding what broke, and seeing whether the automatic checks passed and the update went live.

It didn't. All of that was still on me.

Even the first step kept stopping me. My localhost (the app running on my own computer) often would not start, so I kept typing the same thing to my AI: “The server is not running. This site can't be reached. Please restart it.”

Each fix was small. And that was with just one product.

Soon there was more than one.

AI let me work on several products at the same time. Each one had its own terminal window, its own AI session and its own localhost. Before long, my screen was full of terminal windows. I had to stop and think about which one belonged to which product, which localhost was still running, and where its errors were.

Two apps would try to use the same address, and one of them would not start. Keeping track of all of them became a job in itself. None of it was building. It was managing.

I was used to the terminal, and I could run npm run dev myself. It still got confusing. For designers, creators, product managers and solo founders who build with AI, it is much harder. They don't want to learn terminal commands or switch between windows. They want to see their app working and get back to making it better.

So I built Decker.

Decker is the missing workflow for vibe coding. Drop in the folder your AI coding tool made, and Decker runs it with a working local URL. It keeps status and logs in one place, and when something breaks, it copies a clear report for your AI. When the app works, you can share a preview link, or check that the automatic checks passed and your latest changes went live. Decker does this for every product you build.

I kept asking my AI to restart the server, so now Decker lets your AI do it. Connect your AI coding tool (Claude Code, Codex or Cursor), and it can check your projects, read the logs, and start or stop a localhost for you. With Lifetime, it can also start a Share, but only after you allow it.