What people actually build with Jev, by use case
Most “Jev use cases” pages are a static list someone wrote once. This one is generated from the directory: the counts below move as builds arrive, and every listing behind them was judged by Jev on submission.
Updated September 2026 · 6 min read
The directory right now
19 builds are listed, spread across 4 of 21 use cases. Click a category to see the listings in it.
| Use case | Builds | What belongs here |
|---|---|---|
| Tools & Apps | 11 | Standalone developer tools, CLI companions, desktop and web apps |
| Agents & Browsers | 6 | Autonomous agents, browser automation, multi-step tool use on live sites |
| Games & Real Time | 1 | Games, real-time control loops, latency-budgeted decisions |
| Robotics & Devices | 1 | Robot arms, drones, embodied control, on-device inference |
| Ads & Marketing | 0 | Ad creative, campaign copy, marketing content generation |
| Benchmarks & Evals | 0 | Benchmarks, eval harnesses, scoring and model comparison suites |
| Coding & Code Review | 0 | Coding agents, code review, refactoring, PR and repo automation |
| Context & Memory | 0 | Context engineering, memory layers, retrieval that persists across sessions |
| Documents & OCR | 0 | Document parsing, OCR, PDF, form and scanned-page understanding |
| Ecommerce | 0 | Storefronts, catalog and listing work, orders and returns |
| Inbox & Support | 0 | Inbox triage, ticket routing, customer support automation |
| Open Source | 0 | Open-source repos, self-hosted releases, community forks |
| Routing & Model Choice | 0 | Model routing, cost or latency arbitrage, choosing which model serves a request |
| Sales & Leads | 0 | Lead qualification, outbound sequences, outreach automation |
| SDKs & Integrations | 0 | Client SDKs, framework adapters, protocol or provider integrations |
| Search | 0 | Search engines, retrieval, deep research over the open web |
| Security & Abuse | 0 | Security analysis, abuse and fraud detection, prompt-injection defense |
| SEO & GEO | 0 | SEO and GEO — ranking in search results and being cited by AI assistants |
| Social Feeds | 0 | Social posting, feed curation, creator and community workflows |
| Trading & Markets | 0 | Trading bots, backtesting, market monitoring |
| UI | 0 | UI generation, design-to-code, frontend QA |
Counts come from this site's own submissions and update as builds arrive. Empty categories are kept visible on purpose — they show what the taxonomy covers, not what has shipped.
Most upvoted builds
Directory order is community upvotes only — never money. The sidebar spotlight is the single paid surface, and it is labeled as such.
- GitHub - waddle-zoo/signal-weave: Typed decisions for operational signals in BI. Powered by TypeSafeAI JevTools & Apps · 1 upvotes
- GitHub - KyleKreuter/jev2048: Let Jev (TypeSafeAI) solve 2048Games & Real Time · 1 upvotes
- GitHub - maddygoround/typesafeai-cli: Give your AI agent a CLI companion who has access to TypeSafe AI's Jev.Tools & Apps
- GitHub - DeepBlueDynamics/typesafe-arena: A playground for TypeSafeAI's Jev ModelTools & Apps
- GitHub - malevrigns/agent-jev: AgentJev-0.6B - a fast 'System One' decision model for AI Agents: feed it any unstructured state (diffs, tracAgents & Browsers
- GitHub - charleeagni/JevPiano: @typesafeai 's Jev controls the 2 hands and each finger to play the piano in real-time. Jev only "sees" whatRobotics & Devices
How to read the counts honestly
- Counts are listings, not usage. One popular build can outweigh ten experiments. The number tells you what got submitted, not what runs in production.
- Every listing passed a Jev review for Jev-ness before it counted. whether the link is a Jev build at all — the full criteria are here.
- Categories are assigned by the model, not by the submitter. That keeps them consistent, and it means a mis-filed build is a model error rather than a self-promotion choice.
The canonical list from the vendor
Separately from what is listed here, TypeSafe publishes the categories they see teams deploying Jev into. It is a good checklist when you are deciding whether a decision in your own system is worth extracting:
- Support triage
- Content moderation
- Résumé screening
- Lead scoring
- Code-review risk
- LLM guardrails
- Data extraction
- Churn signal
Notice the shape of that list: every item is a small, high-volume judgment that used to be either a brittle rule or an overkill LLM call. None of them are writing tasks. That is the pattern to look for in your own code.
What is deliberately not here
Some categories in the wider Jev conversation have no representation in this directory, and we would rather leave them empty than pad them with filler:
- Fine-tuning and self-hosting. Jev is a hosted model — there are no weights to fine-tune or run locally. Pages promising otherwise are describing the tooling, not the model.
- Category pages with nothing in them. We do not generate a landing page per use case until enough real builds exist to justify one. Empty pages are thin content and waste a crawler's budget.
- Vendor benchmark re-posts. Our eval table lives in one place with its caveat attached, rather than being restated in a new article each week.
Common questions
How many use cases does Jev have?
Where does the build data come from?
Why are some categories empty?
Can I filter the directory by use case?
BuiltOnJev is an independent community project, not affiliated with TypeSafe AI. Specs and eval numbers come from TypeSafe's published materials; directory figures come from this site's own submissions and are updated as builds arrive.