← Claude Project Dashboard

πŸ—ΊοΈ How We Built Our Own Local AI

The whole journey in plain English β€” every move, in order, so anyone can follow it and do the same. This page grows as we go: finished steps are solid, upcoming steps are dashed.
πŸ’‘The idea πŸ–₯️Check the machine πŸ”ŽResearch βš–οΈFact-check 🧭The picker page βœ…Choose the lineup πŸ“₯Install πŸ’¬Use it
1

The idea done

We wanted our own AI running on our own computer β€” private, free to use once installed, works with no internet. Cloud AIs (Claude, ChatGPT) stay in the toolbox for coding and the hardest thinking; the local AI handles volume, privacy, and drafts.

The move: decide what the local AI is FOR before downloading anything. Ours: β‘  reading documents and judging hypotheses, β‘‘ consulting-style reasoning, β‘’ turning call transcripts into SOPs.
2

Check the machine done

Local AI lives or dies on one number: graphics-card memory (VRAM). Ours is 8 GB (RTX 5060) β€” that's the desk the AI works at. Our 64 GB of regular RAM turned out to be a secret weapon: it's the overflow table that lets clever "MoE" models run far above our card's weight class.

The move: find your VRAM (Windows: Task Manager β†’ Performance β†’ GPU β†’ "Dedicated GPU memory") and your RAM. Those two numbers decide everything else.
3

Research β€” a crew of scouts done

The model world changes monthly, so we didn't trust memory: five AI research scouts searched the live web in parallel β€” one on the overall landscape for 8 GB cards, one on the Qwen family, one on every other family, one on reasoning models, one on the supporting tools (transcription, document search). A judge merged their 35 raw findings into one scored shortlist.

The move: never pick a local model from a months-old article. The "best" list changes every season.
4

Fact-check β€” three skeptics attack the list done

Three independent fact-checkers then tried to tear the shortlist apart β€” one checked every install command and download size, one checked nothing was outdated or missing, one challenged the scores against public benchmarks. They caught four wrong install commands, several scores that didn't survive the evidence, and two missing strong models. All fixed.

The move: whatever an AI tells you to download, verify the exact command against the official library before running it. One wrong tag and you get a 9.6 GB file that doesn't fit an 8 GB card.
5

The picker page done

Everything learned went into one interactive page: a Magic Quadrant where you slide levers for what matters to you and the model dots glide into place, a sortable report card, a card per model with its exact install command, and a "straight talk" section with the honest limits.

πŸ“„ Try it yourself: the interactive picker β€” open it, move the levers, hover the dots.

It then grew into an anyone edition: pick YOUR machine (PC, Mac, or no graphics card) and YOUR jobs from a menu of 13, and every chart, speed estimate, and recommendation adapts. A second research crew scored all 16 models on all 13 jobs and verified the speed rules; fact-checkers corrected five errors before anything shipped. There's even a button that writes a ready-to-paste prompt for your own Claude/ChatGPT, for an up-to-the-minute second opinion.

The picker's Magic Quadrant with levers, showing model dots colored by how they run on the selected machine
6

Choose the lineup done

Not one model β€” a small team, each with a job: Qwen3.5 9B as the fast daily driver (fits fully on the card), Qwen3.6 35B as the slow big brain (lives in RAM), Gemma 4 E4B as the polished writer, plus the document-search and transcription plumbing. About 55 GB all-in.

The move: pick 2–3 specialists instead of one compromise model. Storage is cheap; switching models is one click.
7

Install up next

Install Ollama (the engine), pull the lineup, add Open WebUI (the friendly browser face), and set the two settings that everyone gets wrong: the context size (so long documents don't get silently chopped) and the document-search model (before uploading anything).

πŸ“Έ Screenshot: Ollama installed & first model downloading
πŸ“Έ Screenshot: Open WebUI's first chat
8

Use it coming

First real jobs: load a document set and ask hypothesis questions with citations; feed in a call transcript and get an SOP draft back. Then compare answers against Claude to learn where the local AI is enough β€” and where it isn't.

πŸ“Έ Screenshot: first real document Q&A with citations
A living document β€” updated at every step. Full technical memory lives in this project's brain/ folder; the friendly version is this page.