Every secret is a mosaic of public pieces.

The browser for OSINT, investigative journalists, and threat intelligence analysts.

macOS, Windows and Linux · Open source

How a secret comes together

  1. Collect. Every search result, quote and page you touch is saved with where it came from: engine, rank, URL, time.

  2. Keep. Pages are archived and timestamped by two independent authorities, so they still exist after they are deleted.

  3. Connect. The agent files people, companies and events, and links them with the quote that proves each link.

What it does

Six of the fourteen things HVNT33 does today. Each one links to the part of the manual that shows how.

  1. Search every engine at once

    Press ⌘K and one query runs on Google, DuckDuckGo, Bing, Brave, Startpage, Mojeek and Yandex, each in its own tab. Every results page you see is recorded for the case: engine, query, rank, title, URL, snippet and time. Consent pages and bot checks are reported, never bypassed.

    Searching in the docs

  2. A query language for what you've seen

    The Search Lab (⌘2) runs a Splunk-style language over everything the case has collected. sourcetype=serp | compare shows each URL’s rank on each engine. | changes shows what appeared, dropped or moved since the last run.

    Search Lab in the docs

  3. Capture evidence in one keystroke

    Highlight a passage or point at an image and press ⌘⇧S. The exact selection is saved with its paragraph, the page’s title, author, date and canonical URL, and the search that led you there. Image originals are archived with a SHA-256.

    Capturing in the docs

  4. An agent files it. You check it.

    Claude Code or Codex runs in a terminal in the same window. It reads each capture and files people, organizations, events and claims into the case, each with the exact quote it came from. Everything it files stays Unverified until you review it, and your reviews are recorded apart from its filing.

    You bring your own Claude Code or Codex. Page content never passes through the terminal; it receives only IDs.

    Agent workflow in the docs

  5. Remember what the internet forgets

    Snapshot any page as a replayable web archive (WACZ) with its text and a screenshot. DigiCert and FreeTSA each sign a timestamp over its hashes. The evidence package checks out with shasum and openssl, on any machine, without HVNT33.

    Snapshots are taken by the app’s own browser in a fresh session, with no cookies or sign-ins, through the case’s connection.

    Your own archive in the docs

  6. A connection per case

    Each case browses direct, through a SOCKS5 or HTTP proxy, or through Tor on its own circuit, so two cases can’t be tied together by IP address. Lock a case to its exit and it pauses the moment the route drops or moves. Snapshots and archive lookups use the same route. WebRTC is removed from every page.

    A route hides your IP address, not who you are. Logged-in accounts, fingerprints and habits can still identify you. HVNT33 is not Tor Browser.

    Connection per case in the docs

All fourteen features

Research you can stand behind

It stays on your machine

Local cases live in ArcadeDB and a checksummed evidence vault on your computer. They need no HVNT33 account, and the browser sends no telemetry. It contacts other services only to do what you ask: the engines you search, the Internet Archive, and two timestamp authorities that receive nothing but a hash.

Filing is not verifying

The agent organizes; it doesn’t vouch. Every record keeps the quote and capture it came from, and stays Unverified until a person checks it. Human reviews are recorded apart from agent filing, so anyone can see which is which.

Proof that doesn’t need HVNT33

An evidence package holds the archive, the text, a screenshot, a manifest and the timestamp tokens. Anyone can check it with standard tools:

shasum -a 256 -c SHA256SUMSopenssl ts -verify -data manifest.json -in timestamps/1-timestamp.digicert.com.tsr -CAfile /etc/ssl/cert.pem

Keep the investigation alive

HVNT33 Cloud will keep cases available across computers, let trusted collaborators examine the evidence, and give selected investigations a permanent public home.

The browser stays local-first. You choose which cases leave your computer, who can see them, and which records are ready to publish. Private research, shared work and public investigations remain separate.

See the Founding 100

An archive made by investigators

The long-term aim is a public network of source-linked investigations: people can follow a case, inspect its evidence, build on prior work and preserve material the web may lose.

Investigations, with the receipts

Published investigations show what was found, where each piece came from and how it fits. They are also sent as a quiet newsletter when there is something worth publishing.

Open the browser tonight

You need Node.js on macOS, Windows or Linux. Everything else, the server, the database and Tor, is built into the app. Signed installers are coming; for now you build it from source, which also means you can read every line.

Download and install

git clone https://github.com/kai-ten/hvnt33.git hvnt33cd hvnt33npm installnpm run setupnpm run desktop