DEV Community

Felipe L
Felipe L

Posted on Originally published at automationscookbook.com

Ollaya: Open-Source, Jev-Style Decision Models for AI Agents

What Happened

Ollaya released a new open‑source framework that implements Jev‑style decision models. The framework blends rule‑based logic with AI inference and offers a lightweight, plug‑in‑ready alternative to heavy proprietary engines. Developers can embed complex decision logic into AI agents or n8n workflows using a simple, declarative syntax for conditions, actions, and fallbacks.

The release ships with a core library, a command‑line interface, and example workflows that show how to combine Ollaya with popular LLMs and data connectors. Ollaya is vendor‑agnostic and runs on any LLM backend—OpenAI, Anthropic, or a local model.

Why This Matters for Builders

  • Modular Decision Logic – Separate decision rules from model prompts. Audit, test, and update logic without retraining or redeploying agents.
  • Reduced Vendor Lock‑In – Open source and LLM‑agnostic. Switch between cloud and on‑prem solutions without rewriting logic.
  • Improved Reliability – Rule‑based fallbacks prevent runaway or nonsensical LLM responses, delivering predictable behavior in production.
  • Easier Collaboration – Declarative syntax fits version control and CI/CD pipelines, letting data scientists and ops engineers edit the same decision files.
  • Cost Efficiency – Limit expensive LLM calls to only when needed. Reduce token usage, especially for high‑volume automation workloads.

FAQ

Q: Can Ollaya replace my current decision engine?

A: Ollaya complements existing engines. It acts as a lightweight wrapper that decides when to invoke an LLM rather than replacing full‑fledged rule engines.

Q: How do I integrate Ollaya with n8n?

A: Use the provided n8n node or run Ollaya as a microservice exposing a REST API. Your n8n workflow can call this API to evaluate decisions.

Q: Is Ollaya suitable for real‑time decision making?

A: Yes. The core library is written in Node.js and executes in milliseconds, making it fit for low‑latency use cases such as chatbots or real‑time data processing.


Originally published on Automations Cookbook.

Top comments (0)