Who runs devwithjev, and how it works

Who runs it

The site is edited by Enzo (editor, Jev user since the launch). It is not affiliated with TypeSafe AI and receives no editorial direction from them; the only commercial relationship on the site is clearly labeled sidebar sponsorship. Income goes to hosting and API costs, nothing else.

How listings get in

Listings are not hand-picked from vibes. The pipeline runs hourly across X, Reddit, GitHub, and YouTube, and every candidate post is judged by Jev itself — jev-latest — with typed questions before anything is published:

• Does the author demonstrate they built something with Jev, rather than merely mentioning it?
• Does this specific post carry a demonstration — photos, video, or a linked repo/demo?
• Which category does the build belong to?
• How strong is the evidence, on a scored rubric?

Posts that fail the first question never reach the catalog. Posts that pass are summarized automatically from their own text: cost and latency figures are copied only when the author stated them, and the field stays empty when they did not — estimates are never filled in. You can report a broken link or an overstated claim any time via Submit a build; listings get corrected or withdrawn.

How the articles are made

The blog and guides are drafted with AI assistance and then reviewed, edited, and fact-checked by Enzo against TypeSafe AI’s official documentation before publication. Each article ends with the date it was checked and which sources it was checked against; if the docs change, the article gets updated or explicitly marked as describing an older state. Articles attribute every number to whoever measured it and say so explicitly when a figure is not ours.

We use Jev ourselves

This is not a site that only writes about the model — the review pipeline above runs on jev-latest in production, through the same state-and-typed-questions interface the guides describe. The live counters below come straight from the review queue.

Contact

Corrections, takedown requests, or questions: DM @enzo on X, or send a listing correction with its source via Submit a build. See also our privacy policy.