Our own servers
The V1-style static blueprint: your files served from our fleet with our CDN and DNS and a Let's Encrypt certificate, isolated per site. The default footprint-pool path, and the strongest control for footprint-sensitive PBN sites.
Static & app hosting
Three backends for static and app hosting, one deploy choice
Static and app sites deploy to whichever backend suits the job — our own fleet, Cloudflare Pages, or GitHub Pages on your connected account. Same Static product, same custom domains, CDN, DNS and certificates; the backend is a per-site choice at deploy, on both the Footprint-Free and Mainstream lines, from the dashboard and the MCP.
- 3 backendsour fleet, CF Pages, GitHub Pages
- Per-site choicepicked at deploy
- Both linesFootprint-Free and Mainstream
- Mix is a plusfootprint diversity for PBN
Choose the backend at deploy
Static hosting means files and a build served fast with a custom domain, a CDN and a certificate. Where those files live is the choice you make per site.
Cloudflare Pages
Deploy to Cloudflare Pages for edge delivery plus real application power — client-side JS, Pages Functions and bindings for KV, D1, R2, Durable Objects and Queues. On our Cloudflare account or your own.
GitHub Pages
Deploy to GitHub Pages on your connected account — a free, first-class static option for mainstream sites. Offered on the PBN line too, but flagged footprint-weaker so you choose with the trade-off in view.
One product, one control surface
Whichever backend you choose, the rest is identical — so the decision is about fit, not about learning three different systems.
- Custom domains work the same way on all three, with both apex and www served and the non-canonical one 301-redirected.
- The backend is a deploy-time option, chosen per site on the dashboard and exposed on the MCP for bulk and AI-driven deploys.
- Certificates, DNS and CDN are handled for you regardless of where the files land.
- Mixing backends across a network is a footprint plus for the Footprint-Free line, not a complication.
- Move a site between backends with a redeploy — the domain and DNS travel with it, no rebuild.
FAQ
When is static or app hosting the right choice?
When your site is a build rather than a database-backed CMS: a marketing site, docs, a landing page, a JAMstack or single-page app, or a footprint-diverse PBN property. You get speed and a small attack surface, and with Cloudflare Pages or GitHub Pages you can add edge functions and real data where you need them.
Can I change the backend later?
The three backends sit behind one Static product, so the concept — files, a build, a custom domain, our CDN and DNS, a certificate — is the same across them. Moving a site between backends is a redeploy, not a rebuild, and your domain and DNS come with you.
Which backend is best for a PBN?
Our own fleet and Cloudflare Pages are the strong footprint choices, and mixing backends across a network adds diversity. GitHub Pages is offered too, but flagged footprint-weaker because it shares GitHub's infrastructure and cannot hard-block backlink crawlers — so it is not the PBN default.
Do I choose per site or once for the account?
Per site, at deploy — it is a deploy-time option on the dashboard and the MCP. Different sites in the same account can use different backends, which for the Footprint-Free line is a footprint plus.
Related
Pick a backend and deploy
Start a card-free 7-day trial and deploy a static or app site to our fleet, Cloudflare Pages or GitHub Pages — the choice is a deploy-time option, on both product lines.
Start free