drophost
drophost vs Netlify
- Netlify: git builds and production
- drophost: drop a zip, get a URL
- Use both: Netlify prod, drophost previews
Pipelines versus finished exports
Netlify shines when main is continuous delivery: npm build, env vars, branch deploys, lock bots on PRs. drophost has no build pipeline. You upload already-built HTML. That is a feature when the cost of wiring a new Netlify site exceeds the value of a two-day client preview. Production complexity is a feature for apps and a tax for throwaway previews—budget accordingly. Free remains useful to validate the loop at 2 MB before you pay.
Netlify Drop overlap—and the file-sharing gap
Drop a folder on Netlify Drop and you get a URL. drophost matches that shape for static zips and pasted HTML, then adds document projects, passwords on Starter, named subdomains, replace-in-place, and MCP. If your “site” is actually a PDF proposal half the time, Netlify is the wrong hammer. Starter at €5/mo is the usual upgrade when passwords or domains appear.
Plan reality for previews
drophost Free hosts lean sites within 2 MB on one project. Starter €5/mo adds passwords, custom domains, branding removal, 100 MB, and 8 projects—enough for several concurrent client previews. Netlify’s free tier is generous for production hobby sites; still, identity and project setup are heavier than a drophost drop. Pro at €12/mo fits teams that keep many parallel links online.
When Netlify must win
SSR-adjacent workflows, edge functions, split testing, and long-lived production domains belong on Netlify (or similar). drophost serves static files only—no Node runtime for your site. Do not host an app that needs a server on drophost.
Agent publish without linking a repo
MCP publish_site lets an agent ship an HTML zip from chat. That path avoids creating a GitHub repo just to satisfy a deploy hook. Pair it with Netlify later if the preview graduates to production.
Practical split used by freelancers
Prod marketing site → Netlify with git. Client-specific prototype → drophost named subdomain, password on Starter. Proposal PDF → drophost file project. One brain, two hosts, fewer “can you add me to the Netlify team?” emails.
Cost of a throwaway Netlify site
Creating a Netlify site, connecting a repo, and inviting a stakeholder for a two-day review is real overhead. drophost’s cost is an upload. Promote to Netlify when the preview graduates to something you will maintain.
Forms and functions are a tell
If you need Netlify Forms or Functions, you have left drophost’s job. If you only need HTML and a password, you have not. Let that tell decide before you create another Netlify site name you will forget to delete. Prefer Netlify when git and production matter; prefer drophost when the export is already built and the audience is a client, not a pull request. MCP covers the agent-built HTML case without a repo.
drophost vs Netlify: feature comparison
| Feature | drophost | Netlify |
|---|---|---|
| Git CI / build | No | Yes |
| Drop a zip or folder | Yes | Netlify Drop |
| PR preview URLs | No | Yes |
| File / PDF sharing | Yes | No |
| Password gate | Starter / Pro | Platform features |
| Serverless functions | No | Yes |
| MCP / agent publish | Yes | APIs / CLI |
| Best fit | Quick previews + files | Production deploys |
Common questions
Should I use drophost or Netlify to host a static site?
Use Netlify when you want git builds and production deploys. Use drophost when the site is already built and you need a URL today.
Is drophost like Netlify Drop?
Close for sites. You drop a zip or paste HTML and get a live URL. drophost also hosts documents, not only sites.
Does drophost run npm build?
No. Export the site first, then drop the zip. There is no build pipeline.
Can I keep production on Netlify and previews on drophost?
Yes. That split is common: Netlify for prod, drophost for client-specific prototypes and PDF handoffs.
Can an agent deploy to drophost without a git repo?
Yes. MCP publish_site uploads a finished zip from chat without creating a repository.
Related
Need a URL this afternoon, not a pipeline?
Export the site, zip dist/ with index.html, and host it on drophost while production stays on Netlify.