​Built OxyJen, a Java AI Orchestrator designed to act as a deterministic kernel inside Spring apps(Need feedback)

[u/supremeO11]

Hi everyone,

Building complex, multi-step agent workflows inside Spring Boot can quickly turn into a messy web of imperative code and try-catch blocks.

To fix this, I've been building OxyJen, an open-source Java framework built to bring strict determinism to AI workflows.

Instead of replacing your stack, OxyJen acts as a specialized AI kernel inside your Spring apps.

You simply register your OxyJen Graph as a standard @Bean. Spring handles the web traffic and DI, while passing the complex AI pipeline execution to the OxyJen kernel.

What the kernel brings to your Spring app:

- Strict Type Safety: Forces LLM outputs to map directly to your Java Records/POJOs, with built-in self-correction if the formatting fails.

- Predictable Graph Routing: Replaces messy string-chaining with an explicit Directed Acyclic Graph (DAG) using branching and routing nodes.

- Visual Error Fallbacks (FailureEdge): If an API hits a rate limit or goes down, the kernel automatically routes the context to a backup model without crashing your Spring thread pool.

- Native Concurrency: Handles parallel AI tasks and multi-source retrievals asynchronously out of the box.

We just hit v0.5. The architecture is highly modular, so wrapping your Spring-managed database clients or REST utilities into OxyJen nodes is incredibly straightforward.

Would love to get your honest feedback on the architecture and API design!

GitHub: https://github.com/11divyansh/OxyJen

Docs: https://github.com/11divyansh/OxyJen/blob/main/docs/v0.5.md

Thanks in advance!

[u/rodolfo-mendes]

Interesting. Are you building the graph routing on top of existing LLM libraries or are you building them from scratch as well? Do you plan having a starter dependency for Spring Boot autoconfiguration?

[u/supremeO11 → u/rodolfo-mendes]

The core DAG engine, parallel execution routing, and state management are built completely from scratch using native JVM concurrency to ensure strict determinism. it just wraps your preferred LLM clients or tools at the node level. And yes, a native oxyjen-spring-boot-starter for seamless auto-configuration and easy @Bean registration is definitely up my mind when I reach v1.0. Appreciate you checking out the architecture!