Free is a product with a different contract
Forever-free static hosts—GitHub Pages being the canonical example—are excellent for certain jobs: open-source documentation, student demos, personal experiments, throwaway prototypes. Paid hosts like StaticHost sell a different contract: explicit site quotas, staging and team features on higher tiers, commercial predictability, and a support posture aimed at paying customers. Confusing the two contracts causes bitterness on both sides.
StaticHost is honest about the free side: there is a short trial (~1 day), then paid plans. There is no forever-free tier. That is not an accident buried in a footnote.
What GitHub Pages (and kin) get right
- $0 for public sites within policy.
- Git-native workflow many developers already use.
- Good enough TLS and custom domains for millions of docs sites.
- Social proof and tutorials everywhere.
Limits show up as soft product constraints: build environment rules (especially on the Pages gem whitelist historically), fair-use and acceptable use policies, less emphasis on multi-client agency staging, and branding or workflow assumptions tied to the Git forge. For many personal projects those limits never matter.
What you pay for on StaticHost
Plans (exact):
| Plan | Price | Sites | Storage | Notes |
|---|---|---|---|---|
| Starter | $9/mo | 1 | 2 GB | Solid for one production site |
| Pro | $30/mo | 3 | 10 GB | Staging |
| Scale | $65/mo | 10 | 30 GB | Agency volume |
| Business | $130/mo | 30 | 100 GB | Teams |
Included shape: zip or GitHub ingest of prebuilt files, HTTPS on preview immediately, custom-domain certificates after DNS verifies, deploy history/rollback. Not included: remote npm/Hugo/Jekyll builds, SPA fallback rewrites (try_files $uri $uri/ =404), cPanel, email, built-in CDN product, WordPress/PHP.
You pay to make that narrow shape dependable for commercial pages, client microsites, and portfolios that need staging discipline—see agencies and pricing deep dive.
Decision table
| Situation | Lean free | Lean paid (StaticHost) |
|---|---|---|
| Class assignment due Friday | ✓ | |
| Client landing page with staging | ✓ | |
| Open-source docs | ✓ | optional mirror |
| 12 marketing microsites | ✓ Scale | |
| Need platform functions | other paid platforms | not here |
| Need forever $0 | ✓ | no |
| Need email on same host | neither—use mail vendor / app host |
Portability reduces risk either way
Because both options serve static files, your dist/public/_site can move. Build locally; upload elsewhere. That portability is why starting free and upgrading later is sane—as long as you did not depend on a vendor-specific SPA redirect file as your architecture. StaticHost will not honor a Netlify _redirects SPA fallback fantasy; design routing for files or hashes from the start—SPA guide.
Cost honesty beyond the sticker
Free hosts cost attention when policies change or when you need a second non-production environment that is awkward to fake. Paid hosts cost money when you only needed a weekend demo. Match the contract to the job. Students: static hosting for students. Shopping: where to host.
Worked example: open-source docs on Pages, client microsite on StaticHost
A consultant maintains a OSS library. Docs build with VitePress into dist and publish to GitHub Pages for $0—fine for the commons.
Separately, a client needs a campaign landing page with legal staging, a vanity domain, and rollback during ad flight. That project lands on StaticHost Pro ($30): staging for counsel, production for ads, HTTPS preview before DNS, certificate after verification. The consultant’s CI already knows how to npm run build; for StaticHost it publishes artifacts instead of relying on remote npm (which StaticHost does not run anyway).
Same generator skills, two contracts. When the campaign ends, they tear down the paid site—campaign landing page—and keep the OSS docs free. Nobody expected forever-free client hosting on StaticHost after the ~1 day trial.
Failure table: free vs paid mismatches
| Symptom | Likely cause | Fix |
|---|---|---|
| Anger that StaticHost “isn’t free” | Expected Pages-like forever $0 | Use free hosts for free jobs; pay for commercial |
| Client site stuck without staging | Chose free host lacking staging workflow | Pro on StaticHost or equivalent |
| SPA works on Host A, 404 on StaticHost | Vendor rewrite dependency | Hash/SSG; read SPA guide |
| “Build failed” on StaticHost | Expected remote npm | Build in CI; upload files |
| Email missing on both | Wrong product category | Mail vendor |
| Surprise invoice for dead microsites | No teardown on paid tier | Delete sites; right-size plan |
Extra procedure: choose in fifteen minutes
- Write the job in one sentence (class demo vs client launch vs OSS docs).
- Circle must-haves: forever $0? staging? teams? vanity domain with managed cert after DNS?
- Circle must-nots: need PHP? need host functions? need SPA fallback rewrite?
- If forever $0 → free host (accept their rules).
- If StaticHost constraints fit (prebuilt files,
=404, no email/CDN product) → pick Starter/Pro/Scale/Business by site count. - If you need remote builds + functions + SPA fallback as one vendor logo → different paid JAMstack platform.
- Record the decision in the README so future you does not “optimize” into the wrong contract.
Paid is not morally better; free is not always fragile. The failure mode is lying about which contract you bought. Deeper plan math: static website hosting pricing.
Compliance, invoices, and procurement reality
Some companies cannot put the marketing site on a personal GitHub account’s free Pages project for procurement reasons: they need a vendor invoice, a named plan, and a place to hang access controls. StaticHost’s paid plans ($9/$30/$65/$130) exist partly for that world. Conversely, a student club should not burn budget on Business teams features when Pages or another forever-free host meets the assignment.
Write the constraint down—“invoice required” vs “$0 required”—before debating CDN mythology or SPA redirects. If procurement also demands a CDN SKU checkbox, StaticHost’s lack of a built-in CDN product is a hard filter; shop accordingly rather than forcing a fit. Portability of dist still means you can prototype on a free host and move the same artifact to StaticHost when the commercial contract starts, provided you never architected around a vendor-only rewrite file.
FAQ
Is StaticHost “free SSL on a paid plan”?
TLS is included with hosting after you are on a plan (and on preview during use). Hosting is not forever free.
Can I use GitHub Pages and StaticHost together?
Yes—Pages for public docs, StaticHost for client work, for example. Same generator, different deploy targets.
Why not offer a free forever tier?
Product positioning: short trial, then clear paid quotas. Other vendors cover the commons.
Does paid mean remote builds?
Not on StaticHost. You still build locally or in your CI.
Is $9 expensive versus S3?
Compare your time wiring CloudFront and certs. For one small site, Starter often wins on simplicity—S3 complexity contrast.