drophost
drophost vs GitHub Pages
- drophost: zip or paste, no git
- Pages: repo-first deploys
- drophost also shares files
Git as a requirement versus an option
GitHub Pages assumes a repo, a branch, and often Actions. That is correct for engineering docs. It is overhead for a designer exporting HTML from a tool that never saw git. drophost’s path is sign in → Website → zip → URL. Repositories are wonderful for software; they are ceremony for a one-week HTML walkthrough. Free remains useful to validate the loop at 2 MB before you pay.
Custom domains and permanence
Pages offers free custom domains on public repos with well-known DNS docs. drophost custom domains start on Starter at €5/mo. For a long-lived open-source docs site, Pages is hard to beat on price. For a client preview you will delete in a month, drophost’s project delete is a cleaner end-of-life. Starter at €5/mo is the usual upgrade when passwords or domains appear.
File sharing outside the site
Pages hosts a site. drophost hosts sites and files. The same account can password a PDF on Starter while the HTML prototype sits on another project. That bundling matters for agencies. Pro at €12/mo fits teams that keep many parallel links online.
Build constraints
Pages can run Jekyll and Actions-based builds. drophost never builds—bring the finished output. Static exports from Vite, Astro, Hugo, and Jekyll all work if index.html is in the zip.
MCP versus Actions
Actions deploy to Pages from CI. MCP publishes to drophost from an agent session without a workflow YAML. Different automation cultures; both valid.
Decision rule
Choose GitHub Pages for repo-backed public docs. Choose drophost for git-free previews, document handoffs, and agent publish. Promote a drophost preview to Pages only when the content deserves a repository.
Open-source docs versus client previews
Public docs that welcome forks belong on GitHub Pages beside the repo. Closed client walkthroughs usually do not. Putting private review HTML in a public Pages repo is a common accident—drophost projects make the privacy choice explicit with optional passwords.
Monorepo politics
Not every preview deserves a folder in the company monorepo. Pages deploys from repos create review noise and CODEOWNERS ping spam. Host the disposable preview on drophost; merge to the docs repo only when content is real. Prefer Pages when the docs deserve a repository; prefer drophost when creating a repo would be theater. File sharing beside the site remains a drophost advantage Pages will not grow into.
Docs engineering versus sales engineering
Docs engineering wants PRs and previews from git. Sales engineering wants a link before the call. Both can be right on the same day if production docs stay on Pages and the call preview lives on drophost.
Private previews
Public Pages repos leak unfinished docs. drophost passwords on Starter keep previews closed without paying for a private Pages setup you will throw away.
Branch protection overhead
Branch protections are correct for docs sites and absurd for a Thursday mock. Skip the branch; upload the zip.
drophost vs GitHub Pages: feature comparison
| Feature | drophost | GitHub Pages |
|---|---|---|
| Git required | No | Yes |
| Drop a zip in browser | Yes | No |
| File / PDF sharing | Yes | No |
| Custom domain | Starter / Pro | Yes (public repos) |
| CI builds | No | Actions / Jekyll |
| MCP / agent publish | Yes | Actions |
| Best fit | Quick previews + files | Repo-backed sites |
Common questions
Is drophost a GitHub Pages alternative?
For quick static previews without a repository, yes. For repo-backed production docs sites, GitHub Pages is often better—especially with free custom domains on public repos.
Do I need git to host on drophost?
No. Paste HTML or drop a zip with index.html.
Can drophost also share PDFs and Word files?
Yes. GitHub Pages is site hosting only. drophost shares files and hosts static sites.
When should I promote a drophost preview to GitHub Pages?
When the content deserves version control, PRs, and a long-lived public docs URL.
Does drophost run Jekyll builds?
No. Bring a finished static export. Jekyll, Hugo, Astro, and Vite outputs all work if index.html is in the zip.
Related
Skip the repo when you only need a preview
Drop a static export on drophost instead of creating a GitHub repository just to get a public URL.