verqen/

Private pilot · pre-deploy gate

Catch the bugs your AI-generated TypeScript ships to prod — before you deploy.

Verqen is an independent source-code review that runs on every pull request, grades it 0–100, and reports findings anchored to exact lines. The reviewer your AI assistant can't be — it wrote the code.

In private pilot with selected teams.

src/payments.tsD · 40/100
3export async function charge(amount) {
4const key = "sk_live_51Hx4aZ…";
● Critical · hardcoded secret

This key ships to the bundle. Rotate it and load from an environment variable — never commit live credentials.

01

Share a repository

Point us at a repo — public or private. No setup on your side.

02

We run the full audit

A multi-pass source-code review across security, types, architecture, and logic.

03

You get a graded report

A 0–100 production-readiness grade with every finding anchored to an exact line.

Currently in private pilot

We are onboarding a small group of teams shipping AI-generated TypeScript. Send us a repository and we will return a full graded audit — no commitment. Pricing is set per pilot.

Who's behind Verqen

Verqen is built by German Kosach, an engineer with a Swiss MBA. The review engine is open-source — you can read exactly how every finding is produced and grounded to a real line of code.

Frequently asked questions

What is Verqen?
Verqen is a GitHub-native code-review service that reviews every pull request — especially AI-generated TypeScript — and returns a 0–100 production-readiness grade with findings anchored to the exact changed lines.
How is it different from a linter or SonarQube?
Linters check style and known rules. Verqen reads the diff with its surrounding context and reasons about logic bugs, hardcoded secrets, broken types, and architectural drift, then grades the change and explains each finding in plain language.
Does my source code leave my infrastructure?
On managed plans, code is sent transiently to the review engine and is not retained — only the findings are stored, never your source. Enterprise self-host keeps the code entirely inside your own network.
Does it work on private repositories?
Yes. Pilot teams grant the repositories they choose, public or private, and Verqen reviews only those. Source code is sent transiently to the review engine and is not retained — only the findings are stored.
Does Verqen comment on pull requests?
Yes. Verqen posts its findings back to the pull request — a summary plus inline comments on the diff — and never re-opens a thread it already posted, so re-pushing a PR does not create duplicates.
How do I get started?
Verqen is currently in a private pilot with a small group of teams shipping AI-generated TypeScript. Request a free audit of one of your repositories and we will send back a graded report; pricing is set per pilot.