The utility, wired end to end
CustomHosted runs on the same tier-one infrastructure as the biggest names on the internet — a global edge network, object storage, dedicated compute, DNS, and certificates, all provisioned as code and billed at one predictable monthly rate.
The stack, end to end
Six pieces, one bill. Here's what each one does and how it earns its place.
- Edge network
Static assets are cached at hundreds of points of presence around the world, so a visitor in Nairobi and one in Toronto both hit a server that's practically next door. When a point of presence doesn't have the file yet, it fetches it once and serves everyone behind it from cache after that — with surge capacity built in for the day a link takes off.
- Object storage
Every static site, build artifact, and backup lives in durable object storage — eleven nines, replicated across multiple facilities so one hardware failure never touches your data. It doubles as the origin the edge network pulls from and the vault your nightly backups land in. See Files for what happens once your app starts writing to it.
- Dedicated compute
Anything dynamic — an API, a database, a full application — runs on an instance that's yours alone, sized to the workload and billed at one fixed monthly rate. No per-request metering, no surprise invoice after a busy week, just a server provisioned as code and patched on a schedule.
- DNS
Name servers with a 100% availability SLA route every request to the right place before anything else happens. We manage the records and the failover; you keep the domain and the final say over where it points.
- Certificates
TLS is issued and renewed automatically, months ahead of expiry, with no calendar reminder required. Every property gets end-to-end encryption by default — no plaintext hop, no expired-certificate outage.
- Everything as code
The edge configuration, the compute, the DNS records, the certificates — every piece of your stack is declared in code, versioned, and reviewable like any other change. Nothing is clicked together by hand, so nothing is a mystery six months later.
How your traffic flows
DNS and certificates sit in front of both paths — every request resolves through our name servers and arrives already TLS-terminated. What happens to it next — the redirects, the cache, the response headers — is covered in full on Delivery.
Static request
- 1
Request hits DNS
Our name servers resolve the domain and point it at the edge network.
- 2
Edge serves from cache
If the asset is already cached at the nearest point of presence, it ships immediately.
- 3
Origin fill on a miss
An uncached request pulls once from object storage, caches the result, and serves everyone behind that edge node from then on.
Dynamic request
- 1
Request hits DNS
Same name servers, same TLS termination, no separate setup required.
- 2
Proxy takes the request
A TLS-terminating proxy in front of your instance handles the handshake and forwards it internally.
- 3
Dedicated compute answers
Your application, database, or API handles the request on the instance provisioned for it.
Everything as code
No console click-ops. Your stack is provisioned, versioned, and portable from day one.
Provisioned, not clicked
Edge config, DNS records, certificates, the instance itself — every part of your stack is declared in code and applied the same way each time. No console click-ops, no drift between what’s documented and what’s running.
Versioned
Every infrastructure change goes through the same review and history as your application code. A bad change rolls back the same way a bad deploy does.
Portable
Because it's defined as code instead of buried in a proprietary dashboard, your stack is exportable. There's no dashboard to migrate off of — it's already just code.
No lock-inYour domain, your DNS records, thecode that defines your stack— exportable on request, at no charge, whenever you ask for it. Seewhat the handover actually contains.
Trying to work out how this stack applies to your situation specifically? See who it's for — agencies, founders, and sites without a developer left to run them.
Always included
No add-on required for the basics. These are part of every plan, static or dedicated.
- TLS certificates
- DNS management
- Daily backups
- Monitoring & alerts
- Security patching
- A human who answers
Keep exploring
- What we host
A compatibility register naming every stack this platform actually runs.
- Static hosting
Static sites and SPAs served from the edge network, deployed on every push.
- Dedicated compute
A fixed-price instance for APIs, databases, and full applications.
- Databases
Managed databases, backed up nightly alongside the rest of your stack.
- Pricing
The full rate card — flat, predictable, and posted in the open.
- Performance
The measured page weight and request count behind this platform's edge network — not just the pitch for it.
- Migrations
Already running somewhere else? Point us at it and we move it — any app, any stack.
- Domains
What is actually in the DNS zone the row above summarises — the record sheet, and who owns each piece.
- In service
A register of representative deployments — what this platform actually runs.
Ready to start?
Tell us what you're running — one fixed monthly rate, within a business day.