001
Your own runtime
Every site runs in its own isolated process with its own resources. Another customer's traffic spike is not your outage.
01 / platform
Hosting and
compute, engineered.
Nexus runs business websites and services on infrastructure we build and operate ourselves. Your site gets its own isolated runtime, deploys without downtime, and secures itself — no shared tenancy, no queueing behind someone else's traffic.
02 / what you get
Built for sites that
have to stay up.
002
Deploys without downtime
Releases are prepared completely, then swapped atomically. Visitors never see a half-deployed site — and rollback is instant, because the previous release never left the disk.
003
Security that maintains itself
Point a domain at Nexus and TLS provisions on the first request, then renews on its own. Certificates are only ever issued for domains we manage.
004
Fast by construction
HTTP/3, assets pre-compressed at deploy time rather than per request, and immutable caching on fingerprinted files. Speed is built in, not bolted on.
005
Your domains, your certificates
Bring any domain. Attach it and it's live — no per-domain fees, no support ticket, no ceiling on how many you run.
006
Watched continuously
Health, certificate expiry, disk and every site are checked every five minutes, with alerts on state change — so a problem reaches us before it reaches your customers.
007
Backed up, and proven
Encrypted hourly snapshots with retention going back weeks — and a scheduled drill that actually restores them. A backup nobody has restored is a rumour.
008
Applications, not just pages
Static sites and server-side functions run side by side. Forms, checkout, webhooks and APIs are first-class, not add-ons.
03 / architecture
Three layers.
Nothing hidden.
Most hosting is a black box you rent. This is the whole system — small enough to explain in a paragraph, which is the point.
edge
tls · routing · compression
control
registry · releases · certificates
runtime
one isolated process per site
The edge terminates encryption and serves files. The control plane is the single source of truth for every site, release and domain — the edge is only ever a projection of it. The runtime keeps your code apart from everyone else's.
04 / measured
Numbers from this
page, not a brochure.
Everything below is measured against the server delivering the page you're reading right now.
~1s
to provision tls
h3
http/3 + brotli
0
maintenance windows
5min
health check interval
1h
backup interval
The animation behind this page is the same idea applied to graphics — 160,000 points solved on the GPU in a single draw call. We build the infrastructure, and the things that run on it.
05 / roadmap
What we're
building next.
Everything above is running today — monitoring and verified backups shipped this week. These are next, listed here because knowing what a platform can't do yet matters as much as knowing what it can.
-
Next
Managed databases & object storage
Postgres with point-in-time recovery, and S3-compatible storage for media and uploads — provisioned per client, alongside the site rather than bolted onto it.
-
Next
DNS and email at your domain
Authoritative DNS so attaching a domain needs nothing from you, and mailboxes on your own domain instead of a third party's.
06 / get started
Put your site
on Nexus.
Bring an existing site, or have one built. Either way it ships to infrastructure engineered for it, on a domain you own, secured automatically from the first request.