Built with Open reimplementations
ollaya
Jev-compatible API server for open decision models. Ollama for decision models: pull and serve 29 model families (Laya, pplx-decider, Clef, Winnow, coba...) locally or self-hosted behind /v1/systemone. The TypeSafe SDK works unchanged: set its base URL and pick an open model. CLI, desktop app, Docker, MCP server, public bench.
1.4k ★ on GitHub
What it is
Run open decision models locally, the way Ollama runs LLMs.
The homepage listed on the repository, ollaya.dev, puts it like this: System 1 for AI agents. Ollaya serves open decision models on your own machine, behind a self-hosted, Jev-compatible API: typed, calibrated answers in milliseconds for routing, guardrails, triage and tool approval.
What the README says it does
- One binary. ollaya serve runs the daemon; ollaya run, pull, list, ps, show, rm,
- TypeSafe-compatible. POST /v1/systemone, /v1/decisions and GET /v1/models are
- Native API. /api/decide adds routing information and timings. /api/pull streams
- Weights come from their authors. Ollaya publishes only small ONNX graphs, about 3 MB each.
- For agents. ollaya mcp serves the models to Claude Code, Claude Desktop, Cursor and other
From the project’s README.
Where the decision sits
ollaya calls the hosted decision API rather than running its own weights. That keeps the project small and means its behaviour moves whenever the vendor ships a new model version. It also means an API key and a network round trip sit in the path of every decision.
Models it references: Jev, JevK5, laya.
How active it is
Created 2026-09-23, last pushed 2026-10-30, 1,433 stars and 89 forks when we read it on 2026-11-02. Everything in this category is weeks old at most, so a stale push date means something different here than it would on a mature project. Check the repository before you depend on it.
Find out what your data actually supports
We turn your historical decisions into a frozen test set, then tell you which model, which threshold, and how much of it you can safely automate.