What is Netlify Drop good at?

Getting a folder onto the internet in about ten seconds with no account, no config and no build step. For a static site or a quick demo that is genuinely hard to beat, and if that is what you are doing you should keep using it.

What happens when I re-drop an updated report?

You get a new site at a new URL unless you deploy into an existing site. That is fine for a demo and bad for a report someone bookmarked — the link in last month's document now points at last month's numbers, or at nothing.

Why use Comma instead for a report?

Because a report needs three things a static host does not provide: per-report access control, one stable URL that accumulates revisions, and somewhere for the feedback to land anchored to the number it is about. Comma is free and does the same folder drop.

Reasonably, yes. Netlify for the site or the demo that should be a website; Comma for the coverage report, the notebook export and the dashboard that exist to be read once and discussed.

Netlify Drop alternatives

Netlify Drop is very good at its job. Drag a folder onto a page, wait a few seconds, get a URL. No account required, no netlify.toml, no build command, no DNS.

If what you have is a website, stop reading and use it.

The friction shows up when what you have is a report — a coverage summary, a notebook export, a Playwright run, a dashboard someone needs to look at once and comment on. Three things go wrong, and none of them are bugs. They are just what a static host is.

It's public

A dropped site lives at a public URL. Anyone with the address opens it, and there is no signed-in-only mode on the free tier — password protection and role-based access are paid features on higher Netlify plans.

For a marketing page that is the entire point. For a coverage report that quotes your source code, or a security scan that names your misconfigurations, it is the wrong default in a way that is easy not to notice until someone pastes the link somewhere.

Re-dropping gives you a new URL

Drop an updated report and you get a new site, unless you go through the extra step of deploying into an existing one. So the link in last month's planning doc points at last month's numbers — or at a site you deleted while tidying up.

Reports have a specific relationship with time: people want the current one, at the address they already have. A deploy-per-version model fights that.

There's nowhere to say "this number is wrong"

This is the one that actually matters, and no static host solves it because it isn't a hosting problem.

The report gets published, someone reads it, and the reaction goes into Slack as a screenshot with an arrow drawn on it. The observation is now detached from the thing it observed, and it expires from the channel scroll in a week.

What Comma does differently

Same folder drop — index.html becomes the report body, sibling assets upload alongside it with relative references rewritten, scripts run inside a sandboxed iframe so interactive reports stay interactive. Then:

Access per report — private, team, any signed-in user with the link, or public, with view / comment / edit on the link and per-person roles over the top. Free. Password gates, expiring links and domain-gating are Enterprise. See sharing & access control.
One URL, many revisions — PATCH a saved report id and each publish appends a revision at the same address. Any two are diffable, which for a test or coverage report is the most useful view there is. See publishing from CI.
Anchored comments — select the cell, leave a thread, and it stays on that cell across revisions. See commenting on HTML.

Where Netlify still wins

Being honest about this matters more than the comparison:

A real website with routing, redirects, custom domains, edge functions and a build pipeline. Comma is not a web host and does not pretend to be.
Public documentation that should be indexed and permanent.
Deploy previews wired into a repo — if you already have them, a docs or Storybook change should use them.
Anything that needs a custom domain. Reports live under commareports.com.

The rule of thumb

If the artifact exists so that people will read it and move on, a static host is right. If it exists so that people will respond to it, hosting is half the job and the interesting half is missing.

Try it

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

Drop a report folder →