Publish a verifiable site
Publishing takes what you select in your vault and produces a live website whose signed notes carry their provenance with them. You can publish to Altretta's hosted service or export to a folder you host yourself.
Both paths require a Pro (or higher) plan. Hosted publishing additionally needs a connected Apilium account.
Choose how to publish
When you open the publish flow, you pick one of two paths:
Altretta publishes your site to sites.altretta.com/<slug> and gives you a verify URL readers can use to check it. Requires a Pro (or higher) plan and a connected Apilium account.
Altretta writes the complete site — pages, search, graph, and per-note provenance footers — to a folder on your computer, so you can host it anywhere. Requires a Pro (or higher) plan.
Publish to a hosted, verifiable site
Select what to publish
Nothing is published unless you check it. Tick the notes you want; each one becomes a page, with wikilinks rewritten to work at any depth in the site.
Name the site and (optionally) its slug
The slug becomes the address. It must be 3–63 characters of lowercase letters, digits and hyphens. If the name is already taken you'll be told and can pick another.
Confirm you understand it will be public
Hosted publishing asks you to tick "I understand this content will be public" before it will run. Anyone with the link can read what you publish.
Connect your Apilium account
Hosted publishing requires a connected Apilium account on a Pro (or higher) plan. If you aren't connected yet, Altretta will prompt you to sign in.
Publish
Altretta builds the themed site and uploads it. Your content goes live at sites.altretta.com/<slug>.
Share the two URLs
The result shows both a public URL (the live site) and a verify URL (on my.apilium.com/verify/<slug>). Both are copyable — share the public URL with readers, and anyone can use the verify URL to check that the site is being served exactly as you published it. The per-note check needs no URL at all: it runs in the reader's browser the moment the page loads.
A note whose frontmatter says publish: false or private: true is left out even if you tick it. That's deliberate: the note itself gets the final say, so a note you marked private can't be published by a stray click.
To update a published site after you've changed your notes, run the flow again and choose Publish again. The site and its verify URL are refreshed to match your latest source.
Export to a local folder
Select what to publish
Tick the notes to export. The same publish: false / private: true rule applies.
Choose local folder export
In the publish flow, pick local folder export and select a destination folder.
Host it anywhere
Altretta writes the full site bundle to that folder. Serve it from any static host.
A local export carries the per-note provenance footers and the embedded verification record, so the in-browser check works exactly as it does on a hosted site — including when the bundle is opened straight off disk over file://. What it does not carry is a verify URL, because there is no hosted bundle to attest to: nothing confirms that the copy a reader is looking at is the one you exported. It shows the discreet "Published with Altretta" mark instead of the badge. If you need readers to be able to check the hosting too, publish hosted.
What ends up on your site
Whichever path you choose, the published site is the vault as a real website, not flat HTML:
- A page per note, with wikilinks rewritten to resolve inside the site.
- Site contents navigation, a hero with search, and full-text search across the site.
- A light/dark theme toggle.
- A per-page outline ("On this page") and a mini-graph card in the right rail.
- A knowledge-graph page for exploring connections.
- A provenance footer on each note that carries a signed anchor.
- The 証 badge — "Verified · Altretta" on a hosted publish that earned it, "Published with Altretta" otherwise.
Export a single note with its provenance
Publishing a whole site isn't the only way to share. When you just want to hand someone one document, you can export a single note — as Markdown, HTML, or PDF. A signed note's export carries a footer with its provenance anchor, its signed-fact count and the export date, so the recipient gets a hash they can compare. It's the lightweight counterpart to a hosted site: one page, one footer, no slug.
A single-note export carries a provenance anchor, not a verify link — the recipient can compare the hash, but there is no hosted page for them to check it against. For reader-facing verification, publish a hosted site.
Next
The verify URL & Verified badge
Show readers how to confirm your site matches its signed source.
What a published site looks like
The chrome you get, and the two things you control.