drophost
drophost vs Cloudflare Pages
- drophost: no git required
- Pages: production CDN hosting
- drophost also shares documents
Git and account wiring
Pages wants a Cloudflare account and a repo. drophost wants a file. For agency previews, the wiring cost is the comparison. Cloudflare’s edge is unmatched for production; your preview should not require a platform tour. Free remains useful to validate the loop at 2 MB before you pay.
Network and production features
Cloudflare’s CDN, WAF, and platform integrations matter at production scale. drophost’s job is a correct, shareable preview URL—not edge configuration. Cloudflare’s edge is unmatched for production; your preview should not require a platform tour. Starter at €5/mo is the usual upgrade when passwords or domains appear.
Files and passwords
Pages is site hosting. drophost adds PDF/Word/Markdown projects and Starter passwords for private reviews. Cloudflare’s edge is unmatched for production; your preview should not require a platform tour. Pro at €12/mo fits teams that keep many parallel links online.
Static export compatibility
Astro, Hugo, and Vite exports zip cleanly onto drophost with named subdomains for asset paths. Same artifacts can later deploy to Pages from git. Cloudflare’s edge is unmatched for production; your preview should not require a platform tour.
Agents
MCP publish is chat-native. Pages automation is CI-native. Choose based on who is publishing. Cloudflare’s edge is unmatched for production; your preview should not require a platform tour.
Decision rule
Production on Cloudflare Pages → keep it. Preview + docs → drophost. Cloudflare’s edge is unmatched for production; your preview should not require a platform tour.
Wrangler versus a zip
If nobody on the call has Wrangler installed, you do not have a Pages preview—you have a meeting delay. Export, zip, drophost, continue the meeting. Cloudflare’s edge is unmatched for production; your preview should not require a platform tour.
Workers and platform features
When you need Workers, WAF rules, or deep Cloudflare integrations, Pages wins. When you need a URL before lunch, drophost wins. Write that on a sticky note for the team. Cloudflare’s edge is unmatched for production; your preview should not require a platform tour.
A realistic agency preview day
Morning: export the Astro build. Noon: stakeholder call in twenty minutes and nobody has Cloudflare access. Zip dist/, drop it on drophost, name preview-client.drophost.space, password on Starter, paste into Zoom chat. Afternoon: feedback arrives as screenshots against that URL. Evening: replace the zip. Tomorrow, if they greenlight production, open the git repo and deploy to Cloudflare Pages properly. The preview never polluted the production Pages project, and you never spent the call installing Wrangler. Cloudflare’s edge is unmatched for production; your preview should not require a platform tour.
Document handoffs beside the site
Pages will not host the PDF scope-of-work that travels with the preview. drophost will. Keep the HTML project and the PDF project in the same account, both passworded, both deletable when the SOW is signed. That pairing is why “just use Pages for everything” fails for client work even when Pages is the right production host. Cloudflare’s edge is unmatched for production; your preview should not require a platform tour. Prefer Pages for production on Cloudflare’s network; prefer drophost for the preview you need before anyone installs Wrangler. Pair PDF SOWs on drophost with HTML previews on drophost.
Avoiding preview sprawl in Cloudflare
Every disposable Pages project is another DNS and access policy to remember. drophost previews keep Cloudflare reserved for properties you intend to keep. When a preview graduates, then wire Pages from git with a clear name.
Access policies versus passwords
Cloudflare Access is powerful and heavy for a single client preview. A drophost password is proportionate. Escalate to Access when the property is real and long-lived.
Account invitations
Inviting a freelancer to Cloudflare for one preview is permanent-feeling. A drophost password is temporary-feeling. Match the feeling to the relationship length.
drophost vs Cloudflare Pages: feature comparison
| Feature | drophost | Cloudflare Pages |
|---|---|---|
| Git required | No | Typical |
| Drop a zip in browser | Yes | Limited |
| File sharing | Yes | No |
| Global CDN production | Basic | Yes |
| Password gate | Starter / Pro | Access policies |
| MCP / agent publish | Yes | CI / APIs |
| Best fit | Quick previews + files | Production sites |
Common questions
Is drophost a Cloudflare Pages alternative?
For zip previews without git, yes. For production CDN hosting on Cloudflare, Pages is the better platform.
Do I need Wrangler to preview on drophost?
No. Drop a zip in the browser or publish via MCP.
Can drophost share documents as well as sites?
Yes. Pages is site hosting; drophost also shares files.
Can I password a preview on drophost?
Yes on Starter and Pro.
Should production stay on Cloudflare Pages?
Usually yes. Use drophost for reviews and handoffs, then deploy to Pages from git when ready.
Related
Skip Wrangler for a two-day review
Drop the static export on drophost for stakeholders. Keep Cloudflare Pages for the production site on git.