Everything you can run on a DGX Spark

I spent a week going through every tool in the local AI ecosystem. Inference engines, coding agents, vector databases, image generation, personal tools. Here is what is actually worth installing.

Everything you can run on a DGX Spark
📌
Series: Running Local, building a private AI stack from scratch. This is Part 3. Part 1 and Part 2 are here.

After getting vLLM and VS Code Copilot running in part 2, I spent a few days going through everything else the DGX can run. The local AI ecosystem is enormous right now. Tools launching every week, repositories with five-digit star counts, every framework claiming to be production-ready.

I made a list and researched each one. This post is that list, with verdicts. The categories are inference, routing, coding agents, web UIs, vector databases, agent frameworks, image generation, voice, and personal tools. Most of it I skipped. Here is everything I looked at and what ended up on the machine.

Inference engines

vLLM is what you should default to on the DGX. It was built for NVIDIA hardware from the ground up. Everything else is a tradeoff: Ollama is simpler but slower, llama.cpp is portable but CPU-first, NIM/TensorRT-LLM is fastest but locked to the NVIDIA stack.

ToolStarsWhat it doesStatus
vLLM50k+High-throughput production serving, PagedAttention, built for NVIDIA✅ Using
SGLang18k+vLLM competitor, better speculative decoding, gaining ground on SparkWorth watching
llama.cpp80k+GGUF, portable, CPU-first. Slower than vLLM on SparkMac side only
Ollama162k+llama.cpp wrapper, dead-simple local servingMac side only
LM Studioprop.GUI for running models, good for non-codersSkip
NVIDIA NIM / TensorRT-LLMNVIDIABest Spark performance, locked to NVIDIA stackEventually

Routing

LiteLLM sits between every tool and the models. Every agent, every UI, every script points at LiteLLM and never touches vLLM directly. Swapping models or adding a tier is a config change. OpenRouter is useful on the Mac side for reaching paid cloud models alongside the DGX.

ToolWhat it doesStatus
LiteLLMOpenAI-compatible router, your existing setup✅ Using
PortkeyCloud-leaning router with observability focusSkip
OpenRouterCloud meta-router for paid models alongside DGXMac side

Coding agents

VS Code Copilot covers interactive in-editor work. It does not cover autonomous work: read this codebase, find the bug, open a PR. That is a different class of tool. OpenCode handles interactive terminal sessions, OpenHands handles async autonomous tasks. They are complementary.

ToolStarsUXNotesStatus
OpenCode172kTerminalClaude Code-style, model-agnostic, MCP support, slash commands✅ Installed
OpenHands74kWeb UI + sandboxAsync autonomous, Docker-sandboxed, file-a-ticket workflow✅ Installed
Cline63kVS CodeIDE-native, plan/act modeSkipped
Aider46kTerminalgit-native, simpler, direct file editsSkipped
CrushgrowingTerminalCharm's pretty TUI agentSkipped
Continue.dev24kVS Code / JetBrainsAutocomplete-heavy, lighter than ClineSkipped

Web UIs

Open WebUI is the default and I already had it running. AnythingLLM is worth adding if you want a turnkey "drop docs, query them" interface. The others are polished but redundant if you have one UI you like.

ToolStarsWhat it doesStatus
Open WebUI70k+The default ChatGPT-like UI for local models✅ Using
AnythingLLM54k+Full RAG + chat in one, ingests docs, builds vector indexIf you need RAG UI
LibreChat22k+Polished multi-provider chatSkipped
Lobe Chat50k+Pretty UI, plugin-heavySkipped

Vector databases

I already had LanceDB from OpenClaw's memory plugin and pgvector through Postgres. Neither hit a wall, so I added nothing else. If either does, Qdrant is the pick for serious self-hosted RAG.

ToolStarsWhat it doesStatus
Qdrant23k+Rust, fast, production-grade self-hosted RAGIf LanceDB/pgvector hit a wall
Weaviate13k+Built-in hybrid search, AI-nativeSkipped
ChromaDB22k+Python-friendly, simple, easy to start withSkipped
LanceDB8k+Embedded, file-based, via OpenClaw memory plugin✅ Have it
pgvector16k+Postgres extension, best if you already have Postgres✅ Have it

Agent frameworks and orchestration

I looked at everything here. Most frameworks try to be the whole stack. The one I would actually install is n8n: workflow automation with AI nodes, 400+ integrations, the "GitHub webhook fires, DGX processes it, Slack gets a message" layer. The heavy frameworks (LangChain, Dify) are better suited to teams building products on top of LLMs than individuals running a personal stack.

ToolStarsWhat it doesStatus
n8n84k+Workflow automation with AI nodes, 400+ integrations, Docker✅ Installed
Dify73k+Self-hostable LLM app platform, visual workflow + RAG + APISkipped
LangChain / LangGraph100k+The kitchen sink, heavy and opinionatedSkipped
LlamaIndex39k+RAG-focused, lighter than LangChainSkipped
Flowise36k+LangChain UI, drag-and-dropSkipped
Langflow51k+Similar to Flowise, prettierSkipped
CrewAI30k+Multi-agent orchestration, role-based teamsSkipped
Onyx12k+Enterprise RAG, air-gappableSkipped
RAGFlow33k+Document-heavy enterprise RAGSkipped

Image generation

ComfyUI is the standard. Node graph, supports FLUX, WAN 2.2, and LTX-2, which are the validated models for the Spark. The others are fine but ComfyUI has won this category.

ToolStarsUXStatus
ComfyUI60k+Node graph, max control, FLUX and WAN 2.2 support✅ Installed
SD WebUI Forge12k+A1111 fork, 30-75% faster, tab UISkipped
A1111145k+Original, classic, slower than Forge nowSkipped
InvokeAI25k+Node + simple UI hybridSkipped
SwarmUI6k+Multi-GPU distributed generationSkipped
Fooocus41k+Midjourney-like simplicitySkipped

Voice and audio

I run faster-whisper on the DGX as an always-on transcription endpoint. Everything else in this category requires a specific voice use case I do not have yet.

ToolWhat it doesStatus
faster-whisperWhisper STT, much faster than reference implementation✅ Installed
WhisperXWhisper + speaker diarization + word-level timestampsIf you need diarization
F5-TTSBest-in-class open TTS, voice cloningSkipped
XTTS-v2Multilingual voice cloningSkipped
PiperLightweight TTS, fastSkipped

Personal tools

This was the category that surprised me most. None of these require a DGX: any always-on home server would do. But since the machine is already running, they are free to add. These are also the use cases that make local AI actually worth it: things you would never hand to a cloud provider.

ToolStarsWhat it doesStatus
Immich64k+Self-hosted Google Photos, face recognition, semantic search via CLIP✅ Installed
Paperless-ngx25k+Document management, OCR, wireable to local LLM for classification✅ Installed
Karakeep14k+Self-hosted Pocket, bookmarks, notes, PDFs with AI auto-tagging✅ Installed
AnythingLLM54k+Turnkey RAG over docs, drop files and chat with themIf you need RAG UI
Obsidian + pluginsprop.Notes with LLM plugins that hit local endpointsIf you use Obsidian

Immich is self-hosted Google Photos: face recognition, semantic search, everything you would pay Google for, running locally on your own hardware. Paperless-ngx handles documents with OCR: drop a receipt, contract, or tax scan and it finds it. Karakeep is self-hosted Pocket with AI auto-tagging. I use all three.

What I deliberately did not install

The trap with a machine this capable is that everything seems worth trying. The filter I kept using: does this solve a problem I have today, or one I am imagining? Most tools that seemed fascinating failed that test.

If you cannot name the specific workflow a tool enables, skip it for now. Install one thing, use it for a week, then decide. What is actually running on the DGX now is what I built SparkMonitor to track, and I will cover that in a future post.

Subscribe to Sahil's Playbook

Clear thinking on product, engineering, and building at scale. No noise. One email when there's something worth sharing.
[email protected]
Subscribe
Mastodon