Tech Audit turns a code upload into a prioritized review report. Ego Eimi designed and built the product around the analysis: progress, findings, billing, access and a report a team can share and act on.
A code review is useful when a team can understand the findings and decide what to fix. Running a model against files is only one step; the product also needs input handling, status, severity and explanations.
Tech Audit brought that process into a subscription application. Account access, billing and reporting therefore formed part of the same delivery as the AI analysis.
The Next.js and React interface presented Gemini-powered findings around security, quality and maintainability. Server-sent events carried progress from upload through the finished report.
TypeScript services on Vercel used Drizzle, Supabase and PostgreSQL. Stripe Checkout, the customer portal, subscription gates and webhook handling supported billing, with PostHog for product analytics.
The delivered product connected analysis to the surrounding SaaS workflow. A team could submit code, inspect progress and use the report as an input to its engineering decisions.
Automated findings need engineering review and do not establish that a codebase is free of vulnerabilities. Ownership includes source-code handling, model configuration, billing webhooks and report access. In a takeover, those application boundaries deserve the same attention as the analysis engine.
Project contribution: Ego Eimi. The scope described above identifies the work behind this case.
Editorial review: Ego Eimi · Updated September 6, 2026 · About the team
Your technology
Start with the business
Tell us which system matters, what has changed and who controls it. We will define a reviewable next step. Read Foundation and the commitments and evidence.
