Kunok Joung

Spring IVE - AI codes your issues. You steer the value.

by
Every day — bugs via email, phone, Slack. Manual assignment. Developers patching half the day instead of building. No one knew the status until a client complained. The problem wasn't effort. It was the structure. Manual DevOps doesn't improve no matter how hard you try. So I built IVE. It watches your GitLab/GitHub issues. When one arrives, an AI agent writes the fix and opens a merge request. You just review and approve. Not replacing developers. Freeing them to build what matters.

Add a comment

Replies

Best
Kunok Joung
Maker
📌
Hi everyone! I'm the maker of IVE. I run a software solutions company. My developers were working fine in GitLab. The problem was me — the manager who had no visibility. Which issues were in progress, who was working on what, where the bottlenecks were — I had no way to know. When I asked for status updates, developers had to stop their work to write reports, and by the time those arrived, the situation had already changed. I only found out about problems when a client called to complain. I wanted to be proactive, but I couldn't even see what was happening. Meanwhile, developers were already using AI individually to handle issues. But since everything happened in their local environments, there was no trace left behind. Who made what decision, what code AI suggested — zero records. So I thought: if AI is going to do the work anyway, why not automate it from the moment an issue comes in? IVE watches your GitLab/GitHub issues in real time, and AI agents handle the first pass automatically. Instead of writing code from scratch, developers now review and approve the MRs that AI opens. Every step is recorded on the dashboard, with costs tracked automatically. The efficiency gain was beyond what I expected. Developers focus on verification. Managers no longer wait for reports. Try it now. And share your experience with me — I'd love to build something better together with those who share the same struggle!