Git-Based Static Hosts
Stelae’s Git Push deploy target works with any static-site host that pulls from a git repository. This page lists hosts that work well with that flow. They all serve static HTML directly from your repo, updating on every push from Stelae. Pick based on region, free-tier limits, and ecosystem fit.
What to look for
- Region: EU vs. US matters for GDPR and visitor latency. EU-based hosts like statichost.eu and Codeberg keep traffic data inside the EEA.
- Free-tier limits: Most providers offer free tiers with bandwidth caps (typically 10 to 100 GB/month). For small blogs this is usually plenty.
- Custom domains: All hosts on this list support custom domains with free HTTPS.
- Setup complexity: Some hosts detect static sites automatically; others need a small build config (e.g. GitLab Pages requires a
.gitlab-ci.yml). - Open source vs. proprietary: If you care about running on FOSS infrastructure, Codeberg and self-hosted Forgejo are the closest matches.
Hosts
| Host | Region | Free tier | Notes |
|---|---|---|---|
| statichost.eu | EU (Sweden) | Yes (10 GB/month) | Stelae’s default deploy partner. Supports direct upload via API or git-based deploy. The most relevant choice for EU users; this documentation is hosted there. |
| Codeberg Pages | EU (Germany) | Yes, fair use | Non-profit, FOSS-aligned. Push to a pages branch; site is served at username.codeberg.page. Custom domains supported. Best fit if you prefer FOSS infrastructure. |
| Codefloe | EU | Yes | Forgejo-based git host with static hosting integrated via statichost.eu. Enable static hosting in your repository settings; no separate static-host account needed. |
| GitHub Pages | US | Yes | Most widely supported. Enable Pages in repository settings; set the source branch to whatever Stelae pushes to. |
| GitLab Pages | US, EU mirrors | Yes | Requires a .gitlab-ci.yml that publishes the static files. More setup than GitHub Pages, but works once configured. |
| Netlify | US | Yes (100 GB/month) | Connect your repo via the Netlify dashboard. Auto-detects static sites. Netlify Forms is built into the platform if you host here. |
| Cloudflare Pages | Global edge | Yes (generous) | Distinct from Cloudflare Workers (Stelae’s direct-API target). Pages connects to your git repo and rebuilds on each push. |
| Vercel | US | Yes | Optimized for JS frameworks but serves static HTML fine. Connect your repo; auto-deploys on push. |
Self-hosted
If you run your own infrastructure, you can serve the static files directly:
- Forgejo or Gitea with a web server (Caddy, nginx) pointed at the working tree of the pushed branch. Stelae pushes; the web server picks up the files immediately.
- Any git host plus a CI-driven rsync to your server. More setup, but full control over hosting region and infrastructure.
How Stelae’s Git Push fits
Stelae generates an SSH deploy key per site and uses it to force-push your static files to the branch you choose. The hosts above either serve the branch contents directly (Codeberg, GitHub Pages, Codefloe, self-hosted) or pick up the push and rebuild a static site (Netlify, Cloudflare Pages, Vercel). Setup details for connecting Stelae to a git repository are in the Deploying guide.