TypeSafe AI Raises $870M for Jev, an AI Built for Automation, Not Chat
TypeSafe AI has raised $870 million at a $7.5 billion valuation. The round was led by Andreessen Horowitz and was reported on Oct. 9, 2026. The company is the developer of Jev. TechCrunch
Sequoia and existing investor DCVC participated in the round. Wilson Sonsini advised TypeSafe AI on the financing, which the firm described as an $870 million Series A led by a16z. Bloomberg
Jev was released on Sept. 15, a few weeks before the fundraise report. TypeSafe claims one-third of Fortune 500 companies are already using Jev.
Jev uses a transformer architecture, the design behind most modern AI, but it is not a large language model. It does not output text. It outputs probabilities that TypeSafe calls calibrated decisions, scores meant to reflect true odds. TypeSafe positions Jev as suited for automating tasks rather than generating text or code.
TypeSafe describes Jev as the first of a new class of System One models. Those models are built to plug into code rather than be prompted by people, and to be used natively by machines. Andreessen Horowitz The company lists three technical components: a new architecture, a new sampler for choosing outputs, and a new training algorithm called Reinforcement Learning for Calibrated Decisions (RLCD).
TypeSafe was co-founded in 2024 by Diogo Almeida, Sasha Sheng and Erik Gafni. Almeida was previously a researcher at OpenAI. Sheng was formerly a research engineer at Meta.
Andreessen Horowitz published an announcement titled "Investing in TypeSafe AI" on Oct. 9. Separately, TypeSafe has said it is putting intelligence inside software itself so developers can build programs that reason.
The broader context here is an interface change, not only a model change. Most enterprise work with LLMs to date has had a person prompt the system and check text or code output. Jev proposes machine-consumed output, a probability a program can act on without a person in the loop.
In my view, the claim to test is calibration. A transformer that emits well-calibrated probabilities could reduce extra code for thresholds, retries and human review. It would not remove the need for evaluation, logging and rollback. If use by one-third of the Fortune 500 holds, it suggests early users placed it inside existing software, not as a chatbot alongside it.
Over the longer term, what this could enable, if the training method holds, is developers treating reasoning as a function call. Programs that reason are then ordinary programs with a probabilistic step inside. That is less visible than chat. It may prove more durable.
