Why Guaardvark

• It runs on your machine. Language models, retrieval, agents and every generator run on your own hardware, through Ollama, ComfyUI and Guaardvark's own GPU services. No cloud API keys, no per-token or per-minute fees, nothing reported home. Web access, posting and every other outbound path stay off until you switch them on or start them, and all of them are declared in one file, egress.json.
• One 16 GB card runs the whole studio. Every image model and every video model except the two larger MiniMax H3 builds run on a single 16 GB NVIDIA card, along with chat and RAG, screen agents, coding swarms, music and voice. One orchestrator hands the GPU to each job, so a render and a language model never fight over VRAM (what runs on 16 GB).
• Your coding agent can drive it. A built-in MCP server, fifteen agent skills and plugins for Claude Code, Grok Build and Antigravity let Claude Code, Grok, Antigravity, Cursor, Codex, Gemini CLI and other agents run every flow: "make a music video from this song", "film this script", "train a LoRA of this character", "swarm this refactor".
• You approve what matters. Nothing posts and no voice is cloned without an explicit yes from you, and fixes Guaardvark writes for its own code wait for your review. The MCP server hides desktop, shell and browser tools unless you allowlist them.

Quick start

Linux with an NVIDIA GPU (16 GB for video, 12 GB for the Wan 2.2 5B; chat, RAG and agents run on less, see the hardware tiers). A fresh Ubuntu desktop has no curl or git; run sudo apt install -y curl git first.

curl -fsSL https://guaardvark.com/install.sh | bash

Then open http://localhost:5173. The script is install.sh from this repository: it clones to ~/guaardvark and runs ./start.sh, which installs everything on the first run. To read it before it runs, download it first (`curl -fsSL https://guaardvar

... View full README on GitHub