Full technical truth on the left. Plain words on the right. Read whichever column is yours — they say the same thing.
Each event is signed with an Ed25519 key generated offline on your machine, and hash-linked to the event before it. Segments are sealed with Merkle roots and timestamped onto a public record, so “when” is not our word — it's checkable. Illustrative values, real format:
{
"v": "logbook/v1",
"ts": "2026-06-26T20:41:07Z",
"kind": "witness/v1",
"body_hash": "sha256:9f2c41…e77a",
"prev": "sha256:a3f1c2…09bc",
"pub": "ed25519:7Qk3…Zt9M",
"sig": "ed25519:xJ4R…kW2c"
}
Change any byte and the chain shows it — tamper-evident by construction. Check it with any standard Ed25519 library: you don't need HOM3's software to verify HOM3's word.
It's a diary that shows rips. Every page is stitched to the page before it, and stamped with a date no one can backdate. If anyone tears a page out or rewrites a line — even us — the stitching shows it.
You never have to take our word for anything. That's the whole idea.
All outbound traffic passes one gate with three positions: sealed (nothing out — the default), allow-list (only destinations you named), and open. Every request — allowed or blocked — is written to a live egress ledger: destination, time, and which room asked. First-connection certificates are pinned so a swapped endpoint can't impersonate a trusted one.
There's one door out of the house, and the handle is on your side. It ships locked. If you open it a crack for one visitor, the doorman writes down everyone who passes — and you can read the list any time.
The package ships with its dependencies vendored — no Docker, no compose files, no cloud account, no API keys, no package manager pulling from the network at install time. It bootstraps offline by default; the internet is optional at every step. Your data lives as plain files on your disk — no proprietary database to escape from. Uninstall is: delete the folder. Your files stay.
Download, unzip, run. That's the install. No accounts, no keys to paste, no fifteen-step guide. And if you ever leave, your things are just… files. Copy them anywhere. Nothing holds them hostage.
Every build's SHA-256 is published at /sha/. Download → hash → compare:
PC Get-FileHash HOM3pc.zip Mac shasum -a 256 HOM3mac.zip Linux sha256sum HOM3linux.zip
Every claim we make maps to code you can read — the source, block by block, each figure measured against the published tree hash. Source-viewable, line by line.
Before you run what we sent you, you can check its fingerprint against the one printed here. If they match, nobody swapped it on the way. Sixty seconds, once, and you never have to wonder.
The walkthrough stays a labeled simulation — even our marketing keeps provenance. Want the real console in motion? Ask for a bespoke walkthrough.
Convinced? Skeptical? Both are welcome here.
Own HOM3 — $300Skeptical? Good. Verify our claims yourself →