MARKDOWN SURVIVES.
Both keep human-readable Markdown in the durable story and derive search machinery around it.
06 // COMPETITIVE DISSECTION
OUR SO-CALLED
COMPETITION.
GBrain is what happens when a second brain asks for a platform team. Vagus is what happens when a search tool refuses to become your employer.
BEFORE THE TRASH TALK
PIN THE CODE.
STATE THE CAVEAT.
VAGUS260c23a
v0.13.0GBRAINb99f4c8
v0.46.24.0This is not a controlled benchmark. Compared from pinned repository snapshots on 2026-08-20. Architecture was inspected; the products were not run head-to-head. GBrain scale and quality figures are project-reported. Vagus performance figures are not used as comparative proof.
COMMON ANCESTRY
YES, THEY
RHYME.
WORDS + MEANING.
Both combine lexical and semantic retrieval instead of pretending embeddings replaced exact terms.
RRF, NOT VIBES.
Both use reciprocal-rank fusion to let independent retrieval paths vote.
LOCAL IS REAL.
Vagus is local by contract. GBrain also has an embedded PGLite, no-server path.
AGENTS INVITED.
Both are built to be called by coding agents, not admired as another notes dashboard.
INDEXES ARE DERIVED.
Neither requires surrendering every memory to an opaque hosted-only database.
THEN THE ARCHITECTURE SPOKE
SAME ANIMAL.
DIFFERENT ZONING.
Search your notes. Return evidence. Exit.
- PARA Markdown vault
- SQLite + Tantivy + usearch
- local embedding + optional local rerank/rewrite
- no resident service, no cloud call
Ingest the world. Graph it. Synthesize it. Schedule it. Serve it. Authorize it. Repeat overnight.
- PGLite or Postgres + pgvector
- typed graph + schema packs
- LLM synthesis + gap analysis
- jobs, OAuth, teams, remote MCP
EXHIBIT A
PUT THE TRADEOFFS
UNDER OATH.
| Question | Vagus | GBrain | What it costs |
|---|---|---|---|
| Job description | Personal PARA retrieval and assisted filing. | Personal/company memory spanning ingestion, graph, synthesis, jobs, identity, and access. | One is a tool. One is a platform wearing a CLI. |
| Implementation | Rust; a self-contained binary with no versioned runtime. | TypeScript/Bun source with a documented compile-to-executable path. | “But JavaScript” is the lazy joke. Surface area is the serious one. |
| Source of truth | Markdown vault first; search projections are rebuildable. Usage provenance is the named exception. | Markdown/Git brain repo can stay canonical; PGLite/Postgres carries retrieval and operational state. | Both let you own files. Only one grows a database contract into a product category. |
| Process model | Index, search, return, disappear. No daemon in any Vagus tier. | Local PGLite and stdio can run without a DB server; the marquee dream-cycle deployment is explicitly 24/7. | “Always a daemon” is false. “The full promise wants infrastructure” is not. |
| Retrieval | BM25 + vectors → fixed unweighted RRF; exact oracle, optional local reranker, reproducible qrels. | Hybrid RRF plus graph recall, aliases, intent/source boosts, reranking, dedup, and token policy. | Inspectable restraint versus a much richer ranking machine. |
| Models | Local after download. Base embedder is about 1.23 GB; optional models add more disk and RAM. | Keyword search can be keyless; semantic and synthesis paths can use hosted or local providers. | Vagus sends a hardware invoice. GBrain may send a provider and operations invoice. |
| Organization | Fixed PARA, with filing proposed by an agent and approved by a human. | Schema packs, typed edges, multiple sources and brains, agent-shaped evolution. | A strong opinion versus a programmable ontology. |
| Collaboration | A deliberately personal, per-machine index. | Team brains, OAuth scopes, federated reads, Postgres, and remote MCP. | If access control is the problem, Vagus is not even applying for the job. |
| Answer shape | Returns evidence; the host agent reads and answers. | think synthesizes an answer with citations and explicit gaps. | A clean retrieval boundary versus an integrated reasoning layer. |
RUST VS TYPESCRIPT
RUST DIDN'T WIN
BECAUSE RUST.
It won this architectural argument because Vagus knew when to stop.
TypeScript didn't lose. It was asked to staff a database, MCP server, OAuth surface, schema system, job queue, provider gateway, admin UI, and a dream cycle.
VAGUS // DEFAULT
$ vagus search "what did we decide?"
→ evidence returned
$ pgrep -x vagus
[ exit 1 ]GBRAIN // FULL PLATFORM LANE
$ gbrain serve --http
→ MCP + OAuth + admin
$ gbrain autopilot --install
[ dream cycle scheduled ]FAIRNESS INTERRUPT: GBrain can run locally, keyless, with PGLite and stdio. We checked. Its serious advantages—shared access, continuous enrichment, durable jobs, remote brains—simply live beyond that minimal lane.
NO STRAW MEN ALLOWED
GIVE GBRAIN
ITS DUE.
Typed graph traversal, cited synthesis, gap analysis, schemas, and durable jobs are real capabilities Vagus does not pretend to replace.
GBrain supports embedded local use, compiled executables, and serious Postgres-backed team deployments without abandoning Markdown/Git ownership.
Its README reports 155,795 production pages and 66 autonomous cron jobs. That is project-reported—not independent, not a Vagus comparison, and still not nothing.
THE RULING
CHOOSE YOUR
INVOICE.
YOU NEED A BRAIN
WITH STAFF.
You need a typed organizational graph, shared brains, access control, continuous ingestion, synthesized answers, and jobs that survive the chat session.
PAY IN SERVICES, SCHEMA, PROVIDERS, AND OPERATIONS.YOU NEED YOUR BRAIN
TO ANSWER AND EXIT.
Your notes already live in Markdown. You want local hybrid recall, explicit PARA, human-approved filing, and no resident system waiting to become a lifestyle.
PAY IN MODEL DOWNLOADS, LOCAL RAM, AND NARROWER AMBITION.OUR SO-CALLED COMPETITION?
IT ISN'T.
GBrain is a memory operating system. Vagus is a retrieval reflex. If you need the former, Vagus was never bidding. If you need the latter, why are you hiring infrastructure?
PINNED EVIDENCE
DON'T TRUST THE COPY.
READ THE CODE.
- V01Vagus local/offline, no-daemon, Markdown-authority, Rust runtime contract ↗design/requirements.md // pinned
- V02Vagus feature and architecture overview ↗README.md // pinned
- V03Vagus model footprint disclosure ↗README.md // pinned
- V04Vagus RRF implementation ↗src/search.rs // pinned
- G01GBrain production, graph, benchmark, and daemon claims ↗README.md // project-reported // pinned
- G02GBrain local PGLite and keyless path ↗README.md // pinned
- G03GBrain Bun compile scripts ↗package.json // pinned
- G04GBrain search versus synthesized think ↗README.md // pinned
- G05GBrain hybrid + graph retrieval pipeline ↗docs/architecture/RETRIEVAL.md // pinned
- G06GBrain capabilities, engines, and Markdown/Git source of truth ↗README.md // pinned
Snapshot claims can age. The commit links cannot. If either architecture changes, update the argument instead of quietly moving the goalposts.
Enough architecture. Want the smaller invoice?
install Vagus →