The Netlify Drop alternative without the platform
Everything you drop on Netlify,
without the deploy step.
Netlify Drop is the fastest way to get a file onto a URL. Drop it, get a link, done. The difference is what happens next. On Netlify the page becomes a project you claim into a team, and who can open it is a plan and team setting. Here it stays one artifact, and the gate is a setting on the page.
Route 01 – from your agent
Your agent publishes it right now.
Paste this into Cursor, Codex, Claude Code or any other agent. It publishes and hands back the URL.
Copies the full prompt, including what your agent should do once the URL comes back.
Route 02 – the way you already work
Drop the file, same as you do now.
One HTML or Markdown file. Same seconds to a URL, and the gate is a setting on the page rather than a team plan.
No file to hand?
- html + markdown
- up to 50 MB
- no signup
Either route returns a URL and a claim link. Claim it and you decide who opens it – anyone, named people, or your whole company.
Indigo Engineering
What Netlify Drop does, and where it stops
Netlify Drop takes a folder, a zip or a single HTML file and serves it at a generated URL with no account and no build step. Its own hero asks whether you have "files from an AI tool or your own computer" – which is exactly the job display.dev is built for.
Where it goes next is a platform. Netlify's own quickstart says a drop made without signing in is protected by a temporary password until you claim it; once claimed, whether it is public depends on your plan and your team's project-visibility setting, and anything finer than that means Password Protection or authentication in the project's code.
That is a deploy platform's answer to a sharing problem, and it is a reasonable one if you wanted a deploy platform. display.dev treats the gate as the point: publishing is one drop or one command, and visibility is a per-artifact setting rather than a team-and-plan configuration.
Netlify Drop behavior above is from its own page at app.netlify.com/drop and the Netlify Drop quickstart, checked 10 August 2026.
display.dev vs. Netlify Drop
| display.dev | Netlify Drop | |
|---|---|---|
| Publish with no account | ✅ | ✅ |
| Drag-and-drop a single HTML file | ✅ | ✅ |
| Publish from an agent, no browser | ✅ (CLI, API, MCP) | ❌ |
| Visibility set per page | ✅ | Per project, by plan and team |
| Restrict to named email addresses | ✅ | ❌ |
| Google Workspace SSO for viewers | ✅ (Pro) | Password protection / team login |
| Microsoft 365 SSO for viewers | ✅ (Pro) | Password protection / team login |
| A name against each view | ✅ | ❌ |
| Inline comments an agent can read back | ✅ | ❌ |
| Update in place at the same URL | ✅ | Redeploy |
| Multi-file site with a build step | ❌ | ✅ |
When Netlify Drop is the right tool
- A public site
- A landing page, a portfolio, a demo you want indexed. Public is the correct answer and Drop gets there fastest.
- A multi-file project with a build
- Netlify is a deployment platform with a CDN, build pipeline, functions and redirects. display.dev publishes one file; it is not trying to replace any of that.
- Something you will keep and grow
- If the artifact becomes a real site with a repo behind it, that is Netlify's job, not ours.
A drop zone is not access control
The speed is real. What Drop gives you is a temporary password and then a project, and neither of those is an answer to "who at my company can read this".
For an AI-generated report going to leadership, a client analysis or an internal dashboard, the question is which named people can open it.
- ✗A shared password is not a personOne secret, held by everyone told it, revocable for nobody.
- ✗No name against a viewWithout per-person sign-in there is no viewer list to show later.
- ✗Gating means adopting the platformProject visibility, Password Protection and team roles are team-and-plan settings on a project you now own.
- ✗The unit is a site, not a documentA one-file report becomes a deployment with a lifecycle you did not ask for.
Who can open it
The same open URL Drop gives you, when the content genuinely is public.
Named email addresses only. Each gets a one-time password by email, so access is per person and you can remove one without touching anyone else.
On Pro, anyone signing in with a verified company domain gets in through Google Workspace or Microsoft Entra ID. Remove them from your identity provider and the page closes to them.
Publishing stays one step. dsp publish ./report.html from the terminal, one sentence to your agent, or drop the file above. The URL comes back either way.
Pricing
Try it. No credit card.
- Included: 10 gated artifacts
- Included: Unlimited public artifacts*
- Included: 50MB storage
- Not included: Version history
- Not included: Google + Microsoft SSO
- Not included: Private artifacts
- Not included: Audit logs
display.dev branded
Individuals. Unlimited gated sharing.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 1GB storage
- Included: 10 versions
- Not included: Google + Microsoft SSO
- Not included: Private artifacts
- Not included: Audit logs
For teams that need company auth.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 25GB storage
- Included: 50 versions
- Included: Google + Microsoft SSO
- Included: Private artifacts
- Included: 90 days audit logs
For compliance-driven organizations.
From €499/mo
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: Custom storage
- Included: Unlimited versions
- Included: Google + Microsoft SSO
- Included: Private artifacts
- Included: 365 days audit logs
Try display.dev free
- Same drop-to-URL speed – with the gate as a setting on the page
- Publish from Cursor, Codex, Claude Code or any other agent
- First artifact in 15 seconds · No credit card
Common questions.
Is display.dev a Netlify replacement?
No, and it is not trying to be. Netlify deploys sites: builds, CDN, functions, redirects, custom domains. display.dev publishes a finished HTML or Markdown file to a URL you control the audience for. If your artifact is a report, a dashboard, a deck or a spec, this is the smaller and faster tool. If it is a web application, stay on Netlify.
Can I publish without an account, like Netlify Drop?
Yes. Publishing anonymously gives you a URL and a one-time claim link. The page stays live for 30 days; claim it and it moves into your organization, where you set who can open it.
Is a Netlify Drop page public?
Not immediately. Netlify's quickstart says an unsigned drop is protected by a temporary password until you claim it, and that what happens after claiming depends on your plan and your team's project-visibility setting. The distinction that matters is that it is a shared password or a team setting either way, where display.dev gates by identity – a named address, or your company's Google or Microsoft sign-in.
Does interactivity survive?
Yes. Charts, scripts, and interactive HTML all keep working – it is served as a page, not a download.
What about a folder or a zip?
Netlify Drop handles those and display.dev's anonymous flow is single-file. Signed in, dsp publish ./site/ publishes a directory with its assets.
Publish your first artifact in 15 seconds.
Free tier. No credit card. One-time password auth on free, Google + Microsoft SSO on Pro (€49/month flat).