Static sites, served from the edge
Marketing sites, docs, and SPAs. Deploy on every push, and the edge network serves every visitor. TLS is on by default. You get real control over 404 pages, redirects, and security headers.
Built for what ships from a repo
If it builds to static files, it belongs here, not on a server you have to patch. Need a contact form too? A static plan takes one, with a small endpoint briefed in behind it. See Forms.
Marketing sites
Landing pages and brochure sites that need to load instantly, everywhere, for every visitor.
Documentation
Versioned docs sites, changelogs, and knowledge bases served straight from your repo.
SPAs & web apps
Client-rendered apps with an API elsewhere. The front end ships from the edge network.
Landing pages
Campaign and launch pages that spike in traffic and need capacity on day one, not day two.
How deploys work
Push to main, it's live in minutes. No pipeline to maintain, no lock-in if you leave.
- 1
Connect your repo
Point us at the repository. There is no pipeline to hand-wire, and no keys to babysit.
- 2
Push to main
Every push builds and ships automatically, live at the edge in minutes.
- 3
Or upload a build
No repository? Drop a build directory instead. It deploys the same way.
- 4
Preview, then roll back
Every deploy is a preview first. Promote it, or roll back to the build before it — that older build is already made and kept on hand.
What happens between "push" and "live", hop by hop, and what a failed build does instead of breaking anything: see Deploys.
Performance & the edge
A global edge network handles the caching and delivery. See the measured page weight and request counts this produces at Performance.
- Global edge network
Your site is cached at points of presence around the world. A visitor hits a nearby server, not one on the other side of the planet. The edge network answers the crowd. Static Pro and its siblings have no server to queue behind — the only real limit is transfer, and transfer is priced flat.
- TLS everywhere
Certificates are issued and renewed automatically, well ahead of expiry. Every hop is encrypted, with no plaintext step in between.
- Caching that just works
Assets are cached at the edge and invalidated on every deploy, so visitors always see the version you just shipped.
- Real control
Real 404 pages, redirect rules, and security headers, set by you, not a generic host default.
The redirect rules, the cache classes, and the exact headers you get are all on Delivery.
What's included
All part of the flat static rate. No add-on is required for the basics.
- Global CDN with edge caching
- TLS certificates, auto-renewed
- DNS managed end to end
- Deploys from git push or upload
- Real 404s, redirects, security headers
The next change is a sentence, not a project
A static site is not a dead end. When the page needs to change, you say what to change, and The Loop carries it the rest of the way. CustomLabs briefs it. A CodeHerder agent opens the pull request. See Brief a change for how to write a good one, and Content for the full path a word takes to go live.
- 1
You notice itYou
A page needs new words, a price changed, or a section is missing. Nothing here watches for this. A person reads the live site and sees it.
- 2
You describe itYou
Say what the page should say instead, in plain language. No ticket template, and no technical wording needed.
- 3
Briefed as a changeCustomLabs
Written up the same way any other change request is. The iteration add-on is what covers it.
- 4
An agent opens the pull requestCodeHerder
The change lands as a real pull request against the repository, with the test suite run against it.
- 5
A human reviews and mergesCustomLabs
Someone reads the diff before it goes anywhere near production — nothing here is auto-applied blind.
- 6
It ships through the same pipelineCustomHosted
The same pipeline that deploys everything else on your stack ships this too — no separate process to babysit.
- 7
You're told it's doneCustomHosted
A note confirming what changed and that it merged, in the same shape as every other note on this site.
- Downtime per change
- None — there is no running process to restart.
The CodeHerder iteration add-on covers each change, at $25/mo. This site is a static build on the same shape, shipped the same way. It has shipped 132 changes since 2026-07-07. See Built in the open for the real ledger.
Keep exploring
- Pricing
The full rate card — flat, predictable, and posted in the open.
- Platform
How the edge network, compute, DNS, and certificates fit together end to end.
- Delivery
The redirect rules, the cache classes, and the response headers behind this page's "real control" claim, in full.
- Dedicated compute
A fixed-price instance for APIs, databases, and full applications.
- Databases
Managed databases, backed up nightly alongside the rest of your stack.
- Migrations
Already running somewhere else? Point us at it and we move it — any app, any stack.
- Environments
The "preview" half of the claim above, in full — what a staging environment is, and how a change gets promoted out of it.
- Deploys
The "roll back" half of the claim above, in full — merge to live, hop by hop, and what a failed build does instead of breaking anything.
- Performance
The measured page weight and request count behind this page's own edge-caching claims.
- Scaling
Outgrow Static Pro? The ladder, the move minute by minute, and when a bigger box is the wrong answer.
- Content
A static build has no admin screen — how a word, a picture, or a new page still ships as a briefed change.
- Guide: static or dedicated?
Not sure this is the right fit? A decision guide to the question underneath the question.
- In service
Worked examples of the loop, including static sites like this one.
- Forms
Can a static site take a contact form? Yes — what catches it, and what it costs.
Ready to start?
Tell us what you're running — one fixed monthly rate, within a business day.