What is the simplest way to put an HTML report online?

It depends on what happens after it is online. If nobody needs to respond to it, a static host — GitHub Pages, S3, Netlify Drop — is fine and free. If the report exists so that people will react to it, hosting is only half the job: you also need per-report access control and somewhere for the reaction to land, anchored to the number it is about.

Why not just use GitHub Pages for reports?

Pages is built for a site, not for a per-run artifact. It is public unless you are on an Enterprise plan, it deploys from a branch or an action rather than from a file, and there is no way to comment on the rendered output. It is the right tool for documentation that ships with a repo, and the wrong one for a coverage report from build 4,812.

What about S3 or a bucket behind CloudFront?

It works and it scales, at the cost of a bucket policy, a distribution, a cache invalidation and an access story you now maintain. For a report that lives a week, that is a lot of infrastructure — and it still leaves you screenshotting the chart to discuss it.

Do I need a BI tool like Hex or Mode for this?

Only if you need the notebook and the warehouse connection. If the analysis is already done and the output is HTML, a BI platform is a large amount of product to adopt in order to host a file. Comma integrates with them instead — publish the rendered output and keep the notebook where it is.

Yes. Publishing, collaboration and scheduled routines are included. The only paid surfaces are optional prepaid AI compute for routines — or bring your own key and pay nothing — and sales-led Enterprise contracts.

HTML report hosting alternatives

There are a lot of ways to get an HTML file onto the internet, and most of them are fine. The question worth asking first is not "how do I host this?" but what happens after someone opens it.

If the answer is "nothing — they read it and move on," a static host is the right tool and you should use the one you already have. If the answer is "they need to tell me the third chart is wrong," hosting solves half the problem and leaves you screenshotting the other half into Slack.

These comparisons are written on that basis. They try to be honest about where each tool is genuinely better.

Static hosts

GitHub Pages alternatives — Pages is excellent for a site that ships with a repo. It is awkward for a per-run artifact: public by default off Enterprise, deployed from a branch or an action rather than a file, no comment layer.
S3 static hosting alternatives — a bucket, a policy, a distribution and an invalidation, maintained forever, for a report that lives a week.
Vercel alternatives — built for applications and deploy previews. A report is neither.
Netlify Drop alternatives — the fastest folder-to-URL there is, and public by default with a new URL every re-drop.
tiiny.host alternatives — the closest thing to a drag-and-drop peer, and the comparison is mostly about what happens after the upload.
GitHub Gist HTML alternatives — Gists don't render HTML; the workarounds all have caveats.
Cloudflare Access alternatives — when the requirement is really "hosted, but only for us."
surge.sh alternatives — one command from a folder to a public URL, with no history and no identity behind it.
Firebase Hosting alternatives — a good CDN with no per-page access control; gating one report means writing a Cloud Function.

Rendering HTML that lives in a repo

GitHub serves raw files as text/plain, so the page never renders and everyone ends up on a proxy.

htmlpreview.github.io alternatives — rewrites the page client-side, which is why fonts, fetch() and relative data files break.
raw.githack alternatives — the sturdier proxy: correct Content-Type, public repos only, pinned to a git ref rather than published.

Notebooks and data tools

nbviewer alternatives — great for public notebooks, no story for private ones and no interactivity.
Posit Connect alternatives — a serious platform with a serious footprint. Sometimes correct; frequently more than the job needs.
Hex alternatives · Mode alternatives — full BI platforms. If you need the warehouse connection and the notebook, use them. If the analysis is done and you have HTML, they're a lot of product to adopt in order to host a file.
Datapane alternative — for teams whose Datapane deployment is now their problem.
RPubs alternatives · Quarto Pub alternatives — both are one-click publishing to the open web. Neither has a private mode, versions, or a comment layer.
Deepnote alternatives — a full collaborative notebook platform, when the readers never run a cell.
Streamlit Community Cloud alternatives · Hugging Face Spaces alternatives — free app hosting with a runtime, a queue and a sleep timer, for output that mostly gets read.

Sending, tunnelling and docs

ngrok alternatives — a tunnel lives exactly as long as your laptop is open. Fine for webhooks, wrong for "take a look when you get a minute."
WeTransfer alternatives — moves the file and stops; the recipient downloads an .html their machine may refuse to open.
Read the Docs alternatives — for private docs, per-build review links, and comments from people who will never open a pull request.

Reviewing a website

Marker.io alternatives — BugHerd, Pastel, Userback and Vercel preview comments, compared by who does the fixing: a person working tickets, or a coding agent reading comments over MCP.

Head-to-head

Comma vs Google Docs — the comment model people actually want, applied to a document format Docs can't render.
Comma vs Claude Artifacts — publishing an AI-built page vs getting it reviewed, restricted and revised at one URL.
Comma vs ChatGPT Canvas — drafting a page with the model vs collecting your readers' comments on the exact line.
Comma vs CodePen — sharing code to play with vs sharing a finished page for review.
Comma vs Observable — building a chart in a JavaScript notebook vs getting the finished report reviewed.
Comma vs Hex · Comma vs Mode · Comma vs Display

Or keep the tool and add the link

Several of these aren't really alternatives — they're upstream of Comma. Keep the notebook where it is and publish the rendered output:

with Jupyter · with Colab · with Quarto · with marimo · with Hex · with Mode

What Comma does that a host doesn't

Anchored comments. Select a table cell or a paragraph, leave a thread, and it stays attached across revisions. See commenting on HTML.
Per-report access. Private, team, domain-gated, or link — decided per report rather than per bucket. See sharing & access control.
Revisions at one URL. PATCH a saved id and each publish appends a revision; any two are diffable. See publishing from CI.
A sandbox. Report HTML runs with allow-scripts and no allow-same-origin, so interactive reports stay interactive without getting access to anyone's session. See the security model.
Agents as first-class authors. The same scoped token works over REST and MCP, so Claude Code and Cursor publish and reply to comments directly.

What it isn't

It is not a CDN, not a web host, and not a BI tool. If you want a website, use a static host. If you want a warehouse-connected notebook platform, use one. Comma is for the document that already exists and needs an address and a conversation. See the mission for the longer version.

Try it

Comma is free — unlimited reports, unlimited commenters, unlimited revision history.

Publish a report →

Host an HTML file · Upload an HTML file, get a link
Share an HTML report · Pricing
Glossary — static hosting, presigned URLs and the rest, defined