Self-host jevos
jevos-v5Yes/no, choice and score decisions from a local CPU model
- Stars
- 926
- Port
- 8017 (HTTP API server (POST /v1/systemone, GET /health))
What is jevos?
jevos is a small decision model plus a single server binary that gives probabilistic answers to yes/no questions, multiple-choice routing and scored ratings, and it speaks the TypeSafe Jev wire format so existing Jev SDK code keeps running locally. It targets rule-driven decisions (refund eligibility, ticket routing, tone scoring) done entirely on your own hardware: inference is CPU-only, in roughly 28-130 ms per request, with an 8,192-token context and about 1 GB of memory. The server exposes POST /v1/systemone and a /health endpoint, can answer one-shot decisions from a request file without running as a service, and accepts an optional bearer key; the model also ships as GGUF for llama.cpp and as an OpenVINO INT8 build. Installation means downloading the release archive for Windows, Linux or macOS (Apple silicon), placing the model beside the binary, and launching ./jev serve. The project is MIT-licensed; in the author's own benchmarks it is much faster and free versus Jev's cloud API but less accurate on the harder tasks, so they advise validating it against your own questions first, and the score output type is still marked early.
Should you self-host jevos?
jevos scores 50/100 on selfhost.directory (how scoring works) and ranks #4 of 7 in Local AI. It has 926 GitHub stars.
It shipped 4 stable releases in the past year. The latest, jevos-v5, came out on 17 October 2026. New versions land roughly every 2 days.
Setup is easy: most people get it running in one sitting. It is MIT-licensed and written mostly in C++.
Its closest alternative on selfhost.directory is unsloth (85/100, 78 667 stars). It scores higher overall, so compare the two before you pick. See jevos vs unsloth side by side.
Features
- 8,192-token context
- API key protection
- Confidence output
- Health endpoint
- Jev-compatible REST API
- Local CPU inference
- Multiple-choice classification
- Offline CLI decisions
- Scored ratingsListed as "✓ (early)" in the project's own comparison table.
- Yes/no probability answers
jevos README
More in LLM Inference
koboldcppSelf-hosted, open-source (AGPL-3.0) single-file GGUF LLM server with a bundled KoboldAI Lite web UI and OpenAI-, KoboldAI- and Ollama-compatible API endpoints.
lemonadeSelf-hosted, open-source local AI server that runs LLM, vision, image, speech, and transcription models on your own GPU or NPU and serves them through OpenAI-style APIs.
libre-chatLibre Chat is a self-hosted, open-source chatbot web service powered by local LLMs like Mixtral or Llama 2, with web UI, API, streaming responses, and document-based QA.
llama.cppllama.cpp is an open-source, self-hosted LLM inference engine written in C/C++ that runs quantized models locally on CPU and GPU with minimal dependencies.
llamactlSelf-hosted control plane that manages llama.cpp, MLX, and vLLM inference servers through a web dashboard with a unified OpenAI-compatible API.
llama-gptSelf-hosted, open-source ChatGPT-style chatbot that runs Llama 2 and Code Llama locally, with a web chat UI and an OpenAI-compatible API.
LLMKubeOpen-source Kubernetes operator running LLMs on NVIDIA, AMD, Intel, and Apple Silicon with pluggable runtimes and hybrid routing.
LumabriLumabri is a self-hosted, open-source system for running LLMs across LAN computers by distributing layers with donor approval, offering terminal and web chat.
mistral.rsmistral.rs is a self-hosted, open-source LLM inference engine in Rust serving OpenAI-compatible and Anthropic-compatible APIs with built-in web UI.
OllamaOllama is a self-hosted, open-source platform for running LLMs locally on macOS, Windows, and Linux with a REST API and official SDKs.
ollama-intel-gpuA self-hosted Docker image running Ollama on Intel Arc GPUs via IPEX-LLM, drop-in replacement for Nvidia Ollama with same API on port 11434.
production-stackSelf-hosted, open-source Helm stack that scales vLLM across a Kubernetes cluster, with KV-cache-aware request routing and a Prometheus/Grafana monitoring dashboard.
0 comments