Share a Hex notebook or app
Hex has two sharing modes: inside the workspace, or on the public internet. Most analysis lives in the gap — the client who commissioned it, the exec who does not want a seat, the partner under an NDA.
Export the analysis
Export the published app as HTML from Hex, or render the notebook yourself:
jupyter nbconvert analysis.ipynb --to html --embed-images --no-input -o analysis.html
--no-input drops the code cells, which is usually right for a client-facing
copy. --embed-images makes the file
self-contained so it renders identically
wherever it lands.
Drag it into the app, or publish it from a scheduled job:
curl -fsS -X PATCH "https://commareports.com/api/v1/reports/$REPORT_ID" \
-H "Authorization: Bearer $COMMA_API_TOKEN" \
-H "Content-Type: application/json" \
-d "$(jq -n --rawfile html analysis.html \
--arg title "Weekly retention — $(date +%F)" '{title: $title, html: $html}')"
What the published copy gives you
- Access per report — unlisted, domain-gated, team-only, or private, decided per analysis rather than per workspace. See the sharing model.
- Anchored threads — "this cohort excludes trials, right?" sits on the chart. See commenting on HTML.
- Revisions at one URL — one report id per recurring analysis; the link in the email thread never goes stale.
- A schedule — scheduled HTML reports re-publish it without anyone remembering to.
Limits
- Entry HTML: 5 MB. Embedded images and inlined chart libraries add up; attach large assets or downsample the data.
- Assets: 25 MB per file, 250 MB and 500 files per report.
- 60 requests/minute per token.
Try it
Comma is free — unlimited reports, unlimited commenters, unlimited revision history.