Free static site hosting

Build it locally. Deploy it free.

StackHost Pages hosts HTML, CSS, JavaScript and static generators at no cost. One site per account, 100 MB of storage, SSL included, and a ready-to-use hostname on *.stackhost-africa.pages.dev.

When the site outgrows static hosting — a database, server-side code, more domains, staging environments — the same account moves it onto Managed Hosting without changing anything about the workflow.

Live today Dallas · DenverNo credit card required

StackHost Pages deployment pipeline A static artifact is built locally, uploaded to StackHost, validated, deployed to Cloudflare's edge network, and served at a branch-labelled hostname with automatic SSL. FREE FOREVER One account. One site. Zero cost. 01 YOU BUILD Static artifact HTML · CSS · JS · assets Hugo · Jekyll · Eleventy Astro · Next · Vitepress React · Vue · Svelte 100 MB max ZIP 02 WE VALIDATE Artifact check size · structure · files SSL provisioned automatic Hostname assigned branch.pages.dev READY TO DEPLOY GO 03 LIVE ON EDGE Global CDN fast everywhere SSL included no config needed Custom domain coming soon SERVING TRAFFIC YOUR HOSTNAME mysite.stackhost-africa.pages.dev Live in minutes · SSL automatic · Free forever 100 MB storage per account UPGRADE PATH When one static site becomes several, or needs a database, the same account moves to Managed Hosting. No migration · No re-deploy · Same workflow

Build locally, upload the artifact, we handle the rest.

What Pages is

Free hosting for sites that do not need a server.

Static sites are cheap to host at scale. Pages passes that saving on: $0 a month, one site per account, no credit card, no time limit.

Upload a built artifact — the output folder from Hugo, Jekyll, Eleventy, Astro, Next.js static export, Vitepress, or plain HTML — and StackHost deploys it to the edge with SSL and a hostname.

No git integration yet. After activation we email you a private upload link (valid for 7 days) — zip the build output and upload it there. Need a fresh link? Reply to the email.

Good fits for Pages

PortfoliosLanding pagesDocumentationBlog (static)Single-page apps

When the project needs server-side code, a database, multiple sites or staging environments, it moves to Managed Hosting. Both can sit on the same account.

How it works

Four steps from code to live site.

The workflow is the same one you would use for any static host. The difference is that the edge network, SSL and hostname are included at no cost.

When you are ready for more, the upgrade path stays inside the same StackHost account.

01

Build your site locally

Use any static site generator or write plain HTML. Run the build on your machine to produce the output folder.

Build
02

Create a free StackHost account

No credit card required. One Pages entitlement is added to the account automatically.

Account
03

Upload the artifact

We email you a private upload link after activation (valid for 7 days). Upload the zip there — StackHost validates the size, structure and file count before anything goes live.

Deploy
04

Your site is live on the edge

The hostname is ready, SSL is provisioned, and traffic is served from the global CDN. Custom domains are coming soon.

Live
What is included

Everything a static site needs. Nothing it does not.

Pages is free because static hosting is cheap at scale. You get the same edge network and SSL as the paid products, with a simple storage limit per account.

Free foreverOne site per account, no credit card, no time limit.
100 MB storageEnough for most static sites, documentation, portfolios and landing pages.
Global edge networkServed from Cloudflare's CDN with automatic SSL everywhere.
*.pages.dev hostnameA ready-to-use hostname the moment the deployment finishes.
Static onlyHTML, CSS, JavaScript, images and fonts. No PHP, no Node, no database.
Artifact validationSize, structure and file count are checked before anything goes live.
Dashboard and APIUpload through the StackHost dashboard or automate it with the API.
Same account as paid hostingWhen the project grows, Managed Hosting, Cloud VPS and Stack Servers are one click away.
Pages or Managed Hosting

One question decides it.

Both lanes live on the same StackHost account. The difference is whether the site needs server-side resources.

StackHost Pages

"It is a static site."

HTML, CSS, JavaScript and assets built locally and uploaded as an artifact. No server-side code, no database.

  • Free forever
  • 100 MB storage
  • Global edge + SSL
  • *.pages.dev hostname
  • One site per account
See how it works
Managed Hosting

"It needs a database or server-side code."

WordPress, Laravel, Node, Python or any stack that needs a server. StackHost manages the hosting environment while you focus on the application.

  • From KSh 850 / month
  • Multiple site slots
  • Databases and cron
  • Git and SSH
  • Staging environments
Explore Managed Hosting
Limits and fair use

Simple rules. No hidden costs.

The limits exist so the free tier stays sustainable. When a project outgrows them, Managed Hosting picks it up without changing the workflow.

What one Pages entitlement includes, and where the edges are
LimitValueWhy it exists
Storage100 MB per accountEnough for most static sites. Larger projects move to Managed Hosting.
Single file size25 MB maximumPrevents accidental uploads of very large media files.
File count20,000 per deploymentKeeps validation and deploy times reasonable.
Compression ratio100:1 maximumPrevents abuse of the storage allowance.
Upload link validity7 days from activationA leaked link must not stay a working upload path forever. Fresh links are one email away.
Not allowed in the zipnode_modules, .env, .gitStatic hosting has no use for them, and secrets have no place on a public site.
Sites per account1Pages is the free entry point. More sites use Managed Hosting.
Server-side codeNot supportedStatic only. PHP, Node, Python and databases need Managed Hosting.

These limits are the boundary between free and paid. A project that hits them is usually ready for Managed Hosting anyway — and the migration stays inside the same account.

Start free, grow when ready

Your first site does not need a server. Your fifth might.

Pages is the free entry point into the StackHost platform. When the project grows — more sites, a database, server-side code, staging environments — Managed Hosting, Cloud VPS and Stack Servers are all on the same account.

Deploying to Pages
  1. Build the site locally.Use any static generator or plain HTML. Run the build to produce the output folder.
  2. Zip and upload.Create a free StackHost account; after activation you get a private upload link by email. Zip the build output and upload it there.
  3. It is live.StackHost validates the artifact, deploys it to the edge, provisions SSL, and gives you a hostname.