What HVNT33 does

Fourteen things, all shipped and all in the open-source app. Where a feature has a limit, the note under it says so.

macOS, Windows and Linux · Open source, AGPL-3.0

  1. ISearch 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. IIEvery page, as data

    A panel docks beside the page (⌘3). On a results page it lists rank, domain and snippet, which other engines returned the same URL, and whether the case already captured, cited or visited it. On any other page it shows what the page declares: author, published and modified dates, canonical URL, and the sites it links to most.

    The page as data in the docs

  3. IIIA 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

  4. IVCapture 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

  5. VAn 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

  6. VIThe case, with its sources attached

    Records carry their source quotes and a status (Unverified, Corroborated, Verified, Disputed). Connections carry their evidence. Arrange the map and export it as SVG, read the timeline, and choose what enters the case from captures staged for review.

    Using HVNT33 in the docs

  7. VIIThe Wayback Machine, beside every page

    See how many versions the Internet Archive holds of the page you’re reading, its first and last capture, and the version nearest its publication date. Archive now asks the archive to capture it.

    Archive now needs a free archive.org account. Lookups send the page’s URL to the Internet Archive; you can switch them to on-request.

    Web archive in the docs

  8. VIIIRemember 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

  9. IXKnow when a page changes what it says

    Watch a page every 6 hours, every day or every week. When its text changes, HVNT33 records the lines added and removed, with replays of the page before and after. sourcetype=change removed_text="*treasurer*" finds what a page stopped saying.

    Watches in the docs

  10. XA 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

  11. XIA separate identity for each case

    Each case keeps its own tabs and, by default, its own cookies and logins. Switching cases swaps the whole browser, so a research account in one case never shows up in another.

    Tabs and browser profiles in the docs

  12. XIIHand over a dossier

    Choose the records that matter and save an offline HTML dossier with the map as SVG, CSV and JSON, and the original files. Or export the whole case.

    Exports in the docs

  13. XIIIIt runs on your machine

    The server, the ArcadeDB database and Tor are built into the app, and local cases live on your computer in the database and a checksummed evidence vault. Local use needs no HVNT33 account and sends no telemetry. Connect to a hosted HVNT33 server when you choose, with the API token kept encrypted by your operating system.

    Architecture in the docs

  14. XIVBuilt on the assumption that pages are hostile

    Web pages run with no access to the app, the terminal or your files, and the end-to-end test proves it from inside a live page. Replayed archives run on a separate origin with no API. Requests to the server go through the native side only.

    Security model in the docs

Download HVNT33