drophost
drophost vs Vercel
- drophost: zip or paste, plus files
- Vercel: git builds and serverless
- Not competitors for production apps
Different layers of the stack
Vercel runs builds and serverless functions. drophost serves static files and uploads. If you need SSR, ISR, or edge functions, drophost is the wrong product. If you need a static export or a document link, Vercel is optional ceremony. Serverless platforms earn their keep on apps; static handoffs should not inherit that weight. Free remains useful to validate the loop at 2 MB before you pay.
Preview culture
Vercel’s PR previews are excellent inside an engineering team. Client stakeholders who are not in GitHub often struggle with that loop. A passworded drophost subdomain on Starter is a calmer external preview. Starter at €5/mo is the usual upgrade when passwords or domains appear.
Static export path
Next.js static export, Vite, and CRA builds can be zipped and hosted on drophost when output is plain HTML/CSS/JS. Watch asset paths—use a named drophost.space subdomain. Stay under plan storage (Free 2 MB; paid plans higher). Pro at €12/mo fits teams that keep many parallel links online.
Files Vercel does not try to share
Word briefs, Markdown prompt packs, and PDFs are drophost jobs. Teams that only compare “hosting” miss half the product.
MCP versus Vercel CLI
Agents publish to drophost via MCP without vercel link. Engineers deploy to Vercel via git. Use each automation where it is native.
Decision rule
Production app → Vercel. Static preview or document handoff → drophost. Promote a preview to Vercel when it becomes a real product surface.
Static export gotchas worth knowing
Next.js static export and SPA builds often assume absolute asset paths. Host on a named drophost.space subdomain and retest. If the app needs serverless routes, it was never a drophost candidate—keep Vercel.
Stakeholder access without GitHub
Product managers outside the repo struggle with Vercel preview auth. A passworded drophost link is a calmer external surface while engineering keeps PR previews internally.
Marketing sites versus app platforms
A static marketing export does not need the Vercel platform. An authenticated Next.js app does. Mis-classifying the artifact wastes platform complexity. Host the export on drophost; keep the app on Vercel.
Env vars and secrets discipline
Never put secrets into a static zip you upload anywhere—including drophost. Vercel env vars belong to server runtimes you do not have on drophost. If the build needs secrets at runtime, it is not a static handoff. Prefer Vercel for apps with compute; prefer drophost for static exports and documents. If you need env vars at runtime, you already left drophost’s lane—stay on Vercel.
Design QA without deploy permissions
Design QA should not need Vercel team seats. Ship a passworded drophost preview for visual QA; keep Vercel permissions for engineers shipping the app that actually needs the platform.
drophost vs Vercel: feature comparison
| Feature | drophost | Vercel |
|---|---|---|
| Git CI / build | No | Yes |
| Serverless functions | No | Yes |
| Drop a static zip | Yes | Limited |
| File / PDF sharing | Yes | No |
| Password gate | Starter / Pro | Deployment protections |
| MCP / agent publish | Yes | CLI / APIs |
| Best fit | Previews and files | Production apps |
Common questions
Is drophost a Vercel alternative?
Not for production Next.js apps. Use drophost for static zip previews and file sharing without a git project.
Does drophost run serverless functions?
No. drophost serves static files and document uploads only.
Can I preview a React export on drophost?
Yes if you export a static build. Zip the folder with index.html and host it. Prefer a named subdomain for asset paths.
Should client stakeholders use Vercel PR previews?
Engineering teams love PR previews. External clients often prefer a passworded drophost subdomain without GitHub access.
Can drophost share a PDF proposal as well as a site preview?
Yes. Vercel does not replace a document handoff tool.
Related
Preview the export without a Vercel project
Zip your static build and drop it on drophost when you need a shareable URL—not another production deployment.