Bring The Source
Of Truth Home.
Verity One runs locally on your machine — Postgres and a small API, kept close and private. One command builds it from source. Your local node is the source of truth; nothing about the install reaches past your desk unless you decide it should.
Verity One installs from source. The stable manifest is source-mode — there is no packaged or signed vo-cli binary, and no Homebrew or npm release yet. The installer clones the repo, pins it to the exact commit named in the manifest, and builds it on your machine. This page (verityone.app/download) is the human install landing; the branded machine origin that serves the installer and the signed release manifests is download.verityone.app. Source install still works exactly as shown below, and source install remains a supported parallel path — not a fallback.
COPY$ curl -fsSL https://verityone.app/install.sh | bash
The installer is served at verityone.app/install.sh (also mirrored at download.verityone.app, which hosts the machine-readable release manifests). It reads the live stable manifest, builds Verity One from source at the pinned commit, configures it, and prints the command to start your local node.
macOS prerequisite: the installer verifies the release manifest's Ed25519 signature with OpenSSL 3 before trusting it, and macOS ships LibreSSL. If you don't already have it, run brew install openssl@3 first — the installer fails closed with that exact hint if it can't find a capable OpenSSL 3.
COPY$ bun install --cwd ~/verity-one/mcp && bun run --cwd ~/verity-one/mcp build $ vo-mcp install --client codex
The source installer does not build the mcp/ package for you — build it once (first line) before vo-mcp install.
This wires a client to your local node over a stdio MCP server — the authoritative transport. Valid clients today are codex, claude-desktop, and generic. Your agents then recall from the same local memory.
New to the whole flow? The step-by-step onboarding ladder lives at /start#shortest — install, connect, and first recall, in order — so this page stays a reference, not a duplicate of it.
The same source path is open by hand. Read the pinned commit from the canonical manifest, clone the repo, check out that exact ref, and build. Nothing here downloads a prebuilt binary — there isn't one. Note: this manual path does not verify the manifest's Ed25519 signature — the one-line installer above does. Use it only if you're vouching for the ref yourself.
$ SHA=$(curl -fsSL https://download.verityone.app/releases/stable.json \ | bun -e 'console.log(JSON.parse(await Bun.stdin.text()).install.source_ref)') $ git clone https://github.com/markprobinson3-maker/VerityOne.git $ cd VerityOne $ git checkout "$SHA" $ ./scripts/bootstrap-local.sh $ bun run api/src/index.ts
bootstrap-local.sh is exactly what the one-line installer runs: it installs Postgres + pgvector + bun, applies the schema, registers your tenant and writes ~/.vo/config.json + the agent token, then prints the start command. (A bare bun install + db:setup skips the tenant + config + token, so agents can't authenticate.)
-
verityone.app/download
— the canonical human install landing page (you're on it). The
branded machine origin
download.verityone.appserves the installer and signed manifests below (its bare root is the product homepage, not this page). - releases/stable.json — the live stable manifest (channel, version, pinned source commit).
-
releases/stable.json.sig
— a detached Ed25519 signature over the manifest. The
curl … | shinstaller verifies this signature against the pinned release key before trusting the manifest'ssource_ref, and fails closed on a bad or missing signature. You can also verify it yourself against the published release public key. - install.sh — the one-line install script itself.
-
release notes
— the version-pinned notes referenced by the stable manifest
(
notes_url).
VO+ is a web bridge that can carry your memory beyond the desk on demand — it does not replace the local node.
Everything above runs entirely local, and the local node stays the source of truth. If and when you want recall from web MCP agents across browsers, phones, and tablets, VO+ is the optional layer that reaches there. It is a bridge, not a requirement, and none of it is needed to install or run Verity One.