Negative space is a feature
Most hosting guides sell inclusion. This one sells exits. StaticHost is good at HTTPS file serving for prebuilt HTML/CSS/JS and generator output. It is the wrong choice when your problem is not “serve files.” Choosing wrong costs a migration mid-crisis; choosing right starts with refusal.
Wrong choice: you need a server-side page renderer per request
Personalized HTML from private data on each hit, shopping carts you own on the origin, CMS admin runtimes like WordPress—these need application hosts. StaticHost will not run PHP or next start. If stakeholders demand WordPress, point them at a WordPress-capable host; do not stretch static hosting into a fake CMS tutorial.
Wrong choice: you require SPA path fallback
Your React/Vue app must use history URLs, cannot prerender, and cannot accept hashes. StaticHost answers unknown paths with 404 (try_files $uri $uri/ =404). Other platforms rewrite to index.html. If that rewrite is a hard requirement, use those platforms—SPA guide explains the constraint; it does not remove it.
Wrong choice: you expect the host to build your app
Your pipeline is “git push and hope the platform runs npm ci && npm run build.” StaticHost does not. Build in your CI or laptop, upload artifacts—git deploy. If remote build is non-negotiable, pick a JAMstack platform that sells it—where to host.
Wrong choice: you need host-native functions
Form logic, auth hooks, or image optimization endpoints “beside” the site as product features. StaticHost hosts files. External APIs are fine; inventing serverless on this origin is not.
Wrong choice: you need email, cPanel, or forever-free
No mailboxes, no cPanel, no forever-free tier (short trial ~1 day). Paid plans: Starter $9 (1×2 GB), Pro $30 (3×10 GB + staging), Scale $65 (10×30 GB), Business $130 (30×100 GB + teams). If $0 forever is the requirement, use a free host—free vs paid. If mail-on-same-panel is the requirement, use a stack that includes mail.
Wrong choice: you need a built-in global CDN product
StaticHost does not market a built-in CDN tier. Lean assets go far—fast static. If your RFP mandates vendor-owned edge POPs as a checkbox, shop CDN platforms.
Wrong choice: SSR-only frameworks without static export
SvelteKit without adapter-static, Astro with server adapters, Next without output: 'export'—wrong runtime. Export or move.
Right choice reminders (so this is not only negation)
Brochure sites, docs, portfolios, campaign pages, static exports, hash-routed SPAs, agency microsites with rollback—these fit. Start from what static hosting is and how to host a static website.
A refusal script you can reuse
“We can host the marketing site as static files on StaticHost. The app/API/WordPress piece needs a different host. Mixing them on one ‘cheap’ static plan will fail at the first dynamic requirement.”
That script saves accounts.
Worked example: the hybrid that should have been split on day one
A founder asks for “one host for everything”: marketing site, logged-in dashboard, and blog their intern will edit in WordPress. A single StaticHost site cannot absorb that sentence.
Correct split:
- Marketing — Astro or hand HTML, built locally, deployed to StaticHost on Starter or Pro. Custom domain
www.example.comafter DNS verifies. - Dashboard — stays on the app platform that already runs the API (
app.example.com). Do not pretend StaticHost will SSR session-personalized HTML. - Blog — either a static generator fed by a headless CMS (rebuild + redeploy) or WordPress on a PHP host at
blog.example.com. Not WordPress PHP on StaticHost.
The founder may push for one invoice. Give them one invoice from your agency if you must—but keep the runtimes honest. When they later paste /app/settings into the marketing host and see 404, you want that to be expected architecture, not a surprise. Document the split in the kickoff deck; link wrong choice for stakeholders who need a URL.
Decision procedure before you sign the SOW
Walk these questions in order. Stop at the first “wrong”:
- Will every public URL exist as a file (or hash route) after build?
- Can builds happen on a laptop or CI you control, without remote npm/Hugo on the web host?
- Are forms, auth, search, and checkout delegated to external APIs or separate app hosts?
- Is email a separate vendor conversation, not part of “website hosting”?
- Is forever-free an absolute requirement? If yes, StaticHost is out after the short trial.
- Does the RFP require a vendor CDN SKU as a checkbox regardless of measured need?
- Does anyone require WordPress admin or another PHP CMS on the same origin?
If you cleared all seven, StaticHost is in the running. If you failed any, name the alternative class of host in writing before kickoff. Mid-project migrations are how trust dies.
Failure table: symptoms that mean “wrong host,” not “bad zip”
| Symptom | What people try | What it actually means |
|---|---|---|
| Deep link 404 on refresh | Adding _redirects myths | Need SPA fallback host or SSG/hash |
| “Deploy” uploads source only | Begging for npm on server | Need remote-build platform or fix CI |
| Contact form never emails | Opening cPanel mail tickets | Need form SaaS / mail vendor |
| Editor cannot log into CMS | Looking for wp-admin on static host | Need PHP/CMS host or headless + rebuild |
| Personalized HTML per user | Hacking cookies into static files | Need application server |
| RFP CDN checkbox fails | Inflating “fast files” claims | Need CDN-product vendor |
| Budget requires $0 forever | Asking for coupon codes | Use forever-free hosts—free vs paid |
When the table row is architectural, stop polishing zips. Change the host or change the architecture.
How to exit gracefully if you already chose wrong
- Freeze feature work that depends on the missing capability.
- Stand up the correct host for the dynamic piece; keep StaticHost only for what remains static.
- Move DNS in deliberate steps: preview on the new host, lower TTL, flip, verify certs.
- Tell the client what improved (editor workflow, SPA fallback, functions) and what stayed (static marketing speed, rollback).
- Do not bad-mouth the old choice—own the mismatch and the fix.
Static hosting is not a moral failing when it is wrong; refusing to admit it is. Pair this guide with jamstack hosting for beginners when stakeholders confuse “static files + APIs” with “functions must live on the same logo.”
FAQ
Can I partially use StaticHost in a hybrid architecture?
Yes—static marketing on StaticHost, app on an app host, APIs elsewhere. Split on purpose.
Is “wrong” permanent?
No. If you later static-export the app, you can return.
Does deploy history make dynamic apps okay?
No. History only rolls back files.
What if my boss insists WordPress on StaticHost?
Show them the PHP requirement. Refusal is cheaper than a demo that lies.
Are functions available via hidden config?
No. Do not plan on undocumented behavior.