gno.sh Publishing
Public URLs, secret links, invite-only spaces, and end-to-end encryption — how to choose.
gno.sh ships four visibility modes. Pick the one that matches how much control you need over who sees the share.
A plain, guessable URL. Anyone with the link can read. No auth, no gate. Good for open research notes, client-facing overviews, and anything you’d otherwise post on a blog.
URL shape:
https://gno.sh/share/<owner>/<slug>A long, unguessable token appended to the URL. Readers with the token open the page; anyone without it gets a 404. You can rotate the token at any time (old links stop working), revoke access entirely, or expire in 24 hours.
URL shape:
https://gno.sh/secret/<token>Readers must be signed in to gno.sh and be an accepted member of your organization. Good for team reference spaces, internal research, or client deliverables where you want an audit trail of who opened the page.
URL shape:
https://gno.sh/private/<slug>The published payload is encrypted with a passphrase you choose. Only ciphertext lands on gno.sh servers. Readers enter the passphrase in their browser to decrypt and read.
We cannot recover a lost passphrase — that’s the whole point. Store it somewhere safe.
URL shape:
https://gno.sh/locked/<token>