# One inference box (DGX Spark) and multiple use cases...

> Source: <https://dev.to/harinezumigel/one-inference-box-dgx-spark-and-multiple-use-cases-5h9d>
> Published: 2026-11-22 11:05:44+00:00

**Recommendation:** Run prompt guard and judging on separate models from your main inference model, and keep distinct switchable config sets per use case so a single box can serve multiple workflows.
More in the playbook "Designing agent systems": <https://wpnews.pro/playbooks/agent-architecture>

While developing my [RAG-LCC](https://github.com/HarinezumIgel/RAG-LCC) experimental RAG, I had multiple use cases:

**RAG-LCC uses LLMs for:**

Although some of the tasks can be handled by the same LMM it is good practice to have other models then the inference one for prompt guard and judgement.

I use 2 sets of configurations, which I want to switch as convenient as possible.

**Coding assistance:**

I tried different models, which would be a separate discussion. But when I use local coding assistance, I cannot run the RAG tests because my Spark DGX can't provide it.

Building a RAG system taught me that managing the LLMs I use is an important part of my development flow. What started as some lines of python code has become a GitHub repo on its own.

If you want to have a look: [harinezumigel-llm-stack](https://github.com/HarinezumIgel/harinezumigel-llm-stack)

Feedback and ideas are welcome.
