Hivemind
Runs entirely on your own hardware

An AI assistant that never phones home.

Chat, retrieval over your own documents, code execution, voice and research agents — served from a machine you control. No third-party model API sits on the serving path.

See how it works
Checking the local gateway…

What it does

Every capability listed here is built and covered by tests. Anything not yet built is named as such, further down.

Chat with memory

Conversations persist, older turns compact into summaries, and durable facts you state once are recalled later. You can read, edit and delete everything it remembers.

Your documents

Upload a file and ask about it. Retrieval fuses vector similarity with keyword search, and answers cite the passages they used so you can check them.

Code that runs

Write Python and execute it in a sandbox with no network and a hard timeout — the same sandbox the model uses, so what you see is what it sees.

Voice, locally

Speech-to-text and text-to-speech run on this machine. Your microphone audio never leaves the host — which is the point of self-hosting a thing that listens.

Research agent

Plans sub-questions, searches, reads real pages and answers with sources. Bounded by design: capped steps, capped reads, and a wall-clock deadline.

Auditable by design

Every request is logged with its route, sources and tool calls, with personal data stripped at write time. The log is the audit trail and your future training set.

The model is a swappable part

One environment variable chooses where tokens come from: an in-process stub for development, llama.cpp on this machine, or vLLM on a GPU you rent. Nothing above that layer knows which it got, so upgrading the model is a config change and an eval run.

  • No external model API on the serving path, ever
  • Rented GPUs still count as yours — your container, your weights
  • Requests refuse to route to known third-party model hosts
# choose a backend $ HIVEMIND_PROVIDER=local ./scripts/dev.sh # ask what it can really do $ ./scripts/probe.sh --provider local PASS decode throughput 6.0 tok/s PASS time to first token 1647ms PASS stop sequences honoured # prove it still works $ ./scripts/test.sh 115 passed

Measured, not claimed

Figures from this machine — a 2019 Intel MacBook Pro with no CUDA, running CPU-only. A GPU backend is a different order of magnitude; these are the honest numbers for the hardware in front of you.

ModelDecodeFirst tokenEval score
Llama 3.2 1B, Q4_K_M6.0 tok/s1.6 s73%
Llama 3.2 3B, Q4_K_M3.0 tok/s5.8 s63%
Gateway overhead alone113 req/s86 ms p50

The eval suite is 16 chat cases plus 13 capability cases. That is too small to rank two models against each other — the gap above is a two-case swing — but large enough to catch a regression. Not yet built: image generation, vision input, and custom personas.