BuiltOnJev

Open-source Jev: what is actually open, and what is not

“Open-source Jev” is one of the most common searches around the model and one of the most commonly answered wrong. The model is hosted. The ecosystem around it is not. Those are different claims, and mixing them up wastes people's time.

Updated September 2026 · 5 min read

The split, stated plainly

ThingOpen?Detail
Model weightsNoJev runs on TypeSafe's servers and is reached over an API. Nothing to download, fine-tune or self-host.
Training methodDescribed, not releasedRLCD is documented in the launch material; the recipe and data are not public.
Tooling & integrationsYesMCP server, SDKs, routers, community indexes — the part you actually build against.
Why this matters
If your requirement is “must run on our own infrastructure”, Jev is disqualified — no amount of open tooling changes that. Plenty of pages imply otherwise by describing the open ecosystem without stating that the model itself is not part of it.

What is open, concretely

  • awesome-jev — community index of Jev projects
  • jev-mcp — MCP server so agents can call Jev as a tool
  • LangChain integration — official-ish Jev integration for chains
  • pi-jev-router — complexity router that grades a request before picking a model

The MCP server is the one most people are looking for: it lets an existing agent treat Jev as just another tool, without writing integration code.

Reaching it without a direct account

You do not have to go direct. Jev is available through the major gateways, which is often the fastest route if you already use one:

  • Vercel AI Gateway
  • OpenRouter
  • Cloudflare

The trade-off is the usual one: a gateway adds a hop and its own pricing on top, in exchange for unified billing and one SDK across models. For a model this cheap, the hop is often the more significant cost.

Open-source Jev repos in this directory

These listings point at public repositories rather than hosted products — the open-source side of the ecosystem, as submitted here:

Listing a repository here is not an endorsement, and it says nothing about the licence of the project itself.

How to evaluate an “open Jev” claim

  • “Open-source” usually means the wrapper. Check whether the repo contains inference code or just calls an API. If it has no weights and no runtime, it is a client.
  • “Self-hosted” usually means the gateway. You can self-host a proxy in front of Jev; you cannot self-host Jev.
  • “Fine-tuning Jev” is not a thing. There is no fine-tuning API and no weights to tune. If a page offers it, it is describing prompt or option-list tuning, or it is wrong.
  • Check the licence, not the label. Community projects vary widely and the word “open” in a README is not a licence.

Common questions

Is Jev open source?
No. Jev is a hosted model from TypeSafe AI reached over an API; the weights are not published. What is open is the surrounding tooling — MCP server, SDKs, routers and community indexes.
Can I self-host Jev?
Not the model. You can self-host a gateway or proxy in front of it, but inference happens on TypeSafe's servers.
Can Jev be fine-tuned?
No. There are no published weights and no fine-tuning API. What people usually mean is tuning the option list or the prompts around it, which happens in your code.
What is awesome-jev?
A community-maintained index of Jev projects and tooling. It is a good starting point, though it is community-run rather than official.

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.