Sego
I am turning an AI code review tool into a small audit servi
I am building Sego, a local-first review layer for AI-generated code.
The product insight is simple:
AI coding tools make writing code faster, but they do not remove the need for review. For solo builders, vibe coders and small teams, the question after generation is often:
“Is this code safe enough to commit or ship?”
Sego reviews AI-generated diffs and produces structured findings with severity, file, line, evidence, risk and suggested fixes.
I am testing a service-first commercialization path:
- free audits for the first 20 AI coding users
- paid private audits starting at $19
- later productized workflows around PR review, local review artifacts and team dashboards
Website: https://sego-8dw.pages.dev/
GitHub: https://github.com/007M7/Sego-Agent
The current goal is not to build a big SaaS immediately. I want to validate whether AI coding users actually feel pain around reviewing generated code before shipping.
Would love feedback on the positioning and the first paid service offer.
9 Comments
The part I'd pay attention to is the difference between concern and behavior.
A lot of AI coding users will agree that review matters.
A smaller group will consistently slow themselves down to get that review before shipping.
Those sound like the same market until money enters the conversation.
I agree. We don't see "people who care about code review" as the real market.
The real market is users who are already shipping AI-generated code and have felt the cost of not reviewing it: broken deploys, unsafe changes, messy architecture, or expensive rework.
Sego is designed around that behavioral gap. The goal is not to ask users to slow down for review, but to make review part of the normal AI coding loop: after AI writes code, Sego checks the diff, saves structured reports, and gives a clear go / fix signal before shipping.
So the product direction is not “another review tool.”
It is a trust layer for AI coding workflows, especially for non-expert builders and small teams who move fast but need guardrails.
Possibly.
The part I'd be careful about is that "trust layer" can end up describing several different reasons people stay.
From the outside, it isn't obvious to me that those reasons necessarily point in the same direction.
That's where things usually get interesting.
That’s a very fair point.
I’m starting to think of “trust layer” less as one single reason people stay, and more as an umbrella for a few different retention reasons.
For some users, trust means: “I want to know this AI-generated diff is not obviously dangerous before I ship it.”
For others, it may mean: “I need a readable artifact I can hand to a teammate or client.”
For non-programmers, it may simply mean: “I need something to tell me whether I should worry.”
And for agent-heavy workflows, it may become more about continuity: saved context, review history, and recoverable decisions.
Those are related, but not identical. So the next step for Sego is probably to be more precise about which version of trust we’re validating first. Right now we’re starting with the narrowest behavior: after AI writes code, will users consistently run an independent review before committing or shipping?
If that behavior is real, the broader “trust layer” can grow from there. If not, the wording is too broad and we should narrow the product.
That's actually the part I'd be most interested in exploring further.
The question feels less like whether trust matters and more like what kind of trust ends up earning the right to shape the product.
Probably more than I'd try to unpack properly in a thread though.
Happy to continue by email if useful.
Yes, I’d really value continuing this by email.
You framed the exact question I’m trying to understand with Sego: what kind of trust is strong enough to change user behavior, not just sound good in a product description.
Could you DM me your email, or should I send mine here? I’d like to discuss it more seriously.
Appreciate that.
What's the best email to reach you on?
I've got a few thoughts on the trust question that are probably easier to explain properly outside the thread.
You can try sending an email here (2169214829@qq.com), and I will contact you as soon as possible, or you can add me on Discord (https://discord.gg/BkZNWRK6). Thank you for your interest in the Sego project!
Appreciate it.
Just sent something over.
Interesting problem either way.