The network explorer
The witness network, verified in your browser.
A window into the witness network. Give it an identifier and the explorer pulls that identity’s records, then re-checks every one of them in your browser before showing anything as verified — so you never have to take the result on trust.
Nothing you search is trusted to the server — it only moves bytes.
Browse the federation.
The explorer works with any witness that meets the open standard — the network is the product, not any one node. Pick one below to browse the identities it holds, or open any node directly by its address at /node/<address>.
Or bring your own evidence.
Have an activity.json or an evidence pack already? Drop it in — it never leaves your machine. The verifier checks it entirely in your browser and shows you exactly what it proves, the same result auths verify gives at a terminal.
Open the evidence drop-zoneWhy you can distrust this page.
The explorer’s server only moves data around — it never decides whether anything is valid. It fetches the records a witness holds and hands them to your browser, and your browser re-checks each one against the relevant cryptographic keys before a single thing shows as verified. A dishonest explorer could hide a record from you — which the freshness labels are there to surface — but it can’t forge one, because the checking happens on your side, not ours.
That re-check runs right here in the page — it’s a small WebAssembly (WASM) build of the very same verifier the command line uses — so trusting this site is optional by design. It’s the same idea the whole network rests on: a witness is a small, plain signer you can check, not a service you’re asked to trust. And every label you see is drawn from a fixed list that ships with the tools, so the explorer can never make one up.
The cloud network.
Everything that proves is open and free: the protocol, the verifier, the full witness node, the watcher. What we sell is operation — uptime, a curated quorum, storage, and alerting. The gate is an account, never a code path.
Anchoring
metered by anchors / month
Submit your agents’ aggregates to a curated quorum that spans the diversity policy’s floors — distinct operators, jurisdictions, and clouds — and get back finalized, offline-checkable anchors.
Monitoring
metered by seeds watched
A hosted watcher over the histories you care about: duplicity and withholding alerts the moment a fork or a silence appears, dashboards over the same open artifacts anyone can re-check.
Pinning
metered by GiB-months
Ciphertext-only custody of your records keyed by (head, index), with availability proofs — and a signed non-response artifact if we ever fail to serve one. Honesty, contracted.
Pricing lands with the launch. And if you’d rather not pay us at all: everything above this section runs from published code, which is precisely the point — the docs walk every role through it.