Static sites, served from the edge
Marketing sites, docs, and SPAs, deployed on every push and served from a global edge network — TLS everywhere, caching that just works, and real control over 404s, 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.
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 — no pipeline to hand-wire, 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 repo, no problem — drop a build directory and it deploys the same way.
- 4
Preview, then roll back
Every deploy is a preview you can promote or roll back to, with the last one always one click away.
Performance & the edge
The same tier-one infrastructure the biggest names on the internet run on. 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, so visitors hit a server that’s practically next door — with surge capacity built in for the day a link takes off.
- TLS everywhere
Certificates are issued and renewed automatically ahead of expiry — end-to-end encryption by default, no plaintext hop.
- 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 you set yourself — not whatever a generic host defaults to.
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 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
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, then roll back" claim above, in full — what a staging environment is, and how a change gets promoted out of it.
- 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.
- Guide: static or dedicated?
Not sure this is the right fit? A decision guide to the question underneath the question.
- In service
A register of what we actually run — including static sites like this one.
Ready to start?
Tell us what you're running — one fixed monthly rate, within a business day.