Deliverd compared with Netlify Drop
Drag the folder, get a URL.
Then decide who the URL is for.
Netlify Drop is the fastest way to get generated HTML onto the web: drag a folder, get an address. For a page that is meant to be public, it is hard to improve on. It stops being the answer when the folder is a client's report and the address should open for four named people and nobody else.
Private by default · Unlimited viewers · No card required
Credit where it is due
What Netlify Drop does well
Seconds, no account required
Drop a folder and it is live at a netlify.app address. You do not even need to sign in first; a dropped site waits an hour for you to claim it.
Updates by dropping again
Drag the updated folder onto the site and it becomes the live version. No build step, no pipeline.
Everything Netlify is underneath
Once claimed, the site is an ordinary Netlify project: a global edge, HTTPS, custom domains and, on paid plans, password protection and team-only visibility.
The boundary
Where it stops
Everyone, your Netlify team, or one shared password
An unclaimed drop hides behind a temporary password. Claimed, the site is either open to everyone, private to your Netlify team and the collaborators you invite, or behind a single password shared with every reader on a paid plan.
A password is not a person
One shared password cannot be revoked for one reader, does not say who opened the site, and will not satisfy anyone asking how access is granted and removed.
Dropping again replaces what was live
The updated folder becomes the live version. The report a client signed off on last month is a deploy in a list, not an address you can send them back to, and nothing tells them the numbers changed.
Nobody knows who read it
What a static host records is requests. That is not the same as knowing that the client's finance director opened the report on Tuesday, and it is not an audit trail.
Every point above was read from Netlify's Drop quickstart and site-protection documentation on 10 September 2026. Products change; if something here is out of date, tell us and we will correct it.
Where Deliverd fits
What you get instead
Access decided per request
Every open is evaluated against the report's audience and your organisation's sharing policy. Forwarding the link forwards nothing.
The identity they already have
SAML and OpenID Connect single sign-on for the major directories, with verified one-time codes for readers outside any of them. No shared password anywhere.
Versions, kept and reversible
Publishing again updates the same address and keeps what was there. Compare, roll back, or pin the report to one version, and readers are told when it changes.
A record, without instrumenting anything
Views, versions, access changes and share links are written to an audit trail you can export, retained to your policy.
As quick as a drop
Publish the same folder with one CLI command, or drop it on the publish page. Root-absolute asset paths are rewritten at publish time, so a Vite build renders as built.
Questions.
Is this as quick as dragging a folder?
Nearly. Drop the folder on the publish page, or run one CLI command, and name the audience in plain English. The extra step is the point: the address opens for the people you named.
Can I keep using my own domain?
Yes, on Team and above. Verify it with a DNS TXT record and reports serve from your hostname, with the certificate handled for you.
What about a genuinely public report?
That works too, if your organisation allows public links. The difference is that it is a decision recorded against the report rather than a property of where the file happens to sit.
Can my CI publish it?
Yes. A REST call or the CLI from any pipeline, with a scoped token. There is also an MCP server if you would rather the agent did it.
Everything after “generate the report”.
Free to start. No credit card.