Publishing
Publishing turns any part of your vault into a live website that readers can verify — every page carries the signed bytes behind the note and re-checks them in the reader's browser, and a hosted site adds a verify URL for the hosting itself.
This is Altretta's publishing differentiator. Every published page carries the signed bytes behind the note — the signature, the signing key, the content hash and the source Markdown they cover — and re-checks them in the reader's own browser, offline. The same 証 seal you see inside the app travels with the page. See what the check proves and what it does not.
What you get
Publish a note, a folder, or a whole vault to sites.altretta.com/<slug> and Altretta produces a real, themed website — not flat HTML:
- A hosted site with contents navigation, full-text search, a hero, a light/dark toggle, and a page per note.
- A knowledge-graph page so readers can explore your vault the way you do.
- A per-note provenance footer on signed notes, carrying the note's signed anchor and the number of signed facts behind it.
- An embedded verification record on signed pages — the canonical signed bytes, the Ed25519 signature, the signing key, the content hash and the signed source — re-checked by a small script in the reader's browser, with no network access.
- A verify URL for a hosted site, on
my.apilium.com/verify/<slug>, which checks the served bundle against a portal-signed attestation. - The 証 Verified badge — but only once the in-browser check has actually passed (see below).
The badge is a claim, so it is only made once a check succeeded. It starts in a "checking" state, and a page with no valid signature behind it — or one whose note was edited since it was last indexed — falls back to a discreet "Published with Altretta" mark instead of "Verified · Altretta". A browser that cannot do Ed25519 reports that it could not check, never "verified".
Two ways to publish
Verifiable hosted site
Publish to sites.altretta.com with a verify URL and the Verified badge. Requires a Pro (or higher) plan and a connected Apilium account.
Local folder export
Export the site to a folder on your own computer to host anywhere. Also requires a Pro (or higher) plan.
Why verifiable matters
A published knowledge base is only as trustworthy as your readers' ability to check it. Because the bundle bakes in signed provenance, a published page can be checked without trusting us: the signature, the key and the signed source travel with the page, and the check runs in the reader's browser with no network access. It's the same signed history that backs your notes inside the app, now travelling with the site. A hosted site adds a verify URL that answers the second question — whether the host is serving what you published.
Publishing a whole site is the heavyweight option; you can also export a single note with its provenance footer as a lighter-weight, one-page share.
In this section
Publish a verifiable site
Step-by-step: choose what to publish, pick hosted or local, and share the URL.
The verify URL & Verified badge
How readers confirm a page matches your signed source, and when the badge appears.
What a published site looks like
The chrome you get, and the two things you actually control.
Related
Verifiable knowledge
The signed history and provenance that publishing bakes into every page.
Signed history
The Ed25519-signed DAG the per-note provenance anchors point into.
Team brain
Share knowledge privately with your team instead of publishing it to the world.
The Seal, in the glossary
Quick definitions for the seal, provenance, and the verify URL.