Deliver at the edge.
Win the millisecond.
NimbusCDN puts your game patches, live streams and storefronts on an anycast network that terminates, computes and defends in the same hop — so players download faster, viewers stop buffering, and carts stop getting abandoned.
Four products, one anycast hop
Most stacks bolt a WAF in front of a CDN in front of an origin. NimbusCDN runs delivery, compute, security and media on the same edge node — one TLS termination, one config, one bill.
Content Delivery
Tiered caching with regional shields, origin offload above 98%, instant purge in under 300 ms worldwide.
- HTTP/3 & QUIC by default
- Brotli, Zstd, range-aware
- Surrogate-key invalidation
Edge Compute
Run JavaScript, TypeScript or Wasm within 30 ms of every user. Cold start measured in microseconds.
- A/B tests & personalization
- Edge KV & signed tokens
- Git-based deploys, instant rollback
Edge Security
Always-on L3/L4 scrubbing plus a managed WAF and bot engine that scores requests before they cost you origin.
- 180 Tbps absorb capacity
- OWASP Top 10 managed rules
- Credential-stuffing & scalper bots
Media Services
Ingest once, deliver everywhere: live packaging, per-title encoding, DRM and thumbnails at the edge.
- LL-HLS & LL-DASH, ~2 s glass-to-glass
- Widevine, FairPlay, PlayReady
- AVIF/WebP image pipeline
Three industries. Three very different definitions of "fast".
A 40 GB patch, a live final, and a Black Friday product page stress completely different parts of a network. We tune the edge per workload instead of shipping one generic config.
Ship a 40 GB patch on launch day without melting your origin
Patch day is a self-inflicted DDoS: millions of clients requesting the same bytes in the same hour. Tiered caching collapses that into a handful of origin fetches, and range-aware delivery keeps resumable downloads saturating the player's link.
"We used to schedule patches at 3 a.m. to protect the origin. Now we ship at peak and watch the graph stay flat." — Director of Live Ops
Two-second latency live, without trading away rebuffer ratio
LL-HLS is easy to demo and hard to run at a million concurrents. Our edge packages per-viewer from a single mezzanine ingest, holds partial segments in memory, and degrades a viewer's ladder before it ever stalls.
"Chat was ahead of the stream on our old CDN. That complaint disappeared the week we cut over." — VP Engineering
Hold sub-second LCP through the flash sale, bots included
Peak traffic and peak fraud arrive together. We cache the personalized page at the edge, serve the right image format per device, and price out the scalpers before a request ever reaches your checkout service.
"The sneaker drop stayed up and the resale listings didn't appear for three days. That's the whole story." — Head of Digital
The p95 is the number that hurts
Averages flatter every CDN. We publish the tail: 95th-percentile time to first byte from 1,400 independent RUM vantage points, sampled continuously across all six regions.
Sample: 4.2 B requests, 1 Aug – 30 Aug 2026. Figures are illustrative placeholders for this design.
The fastest request is the one that never reaches your origin
Every NimbusCDN PoP is also a scrubbing centre. Filtering happens where the traffic lands, so mitigation adds no detour and no extra RTT.
Always-on DDoS
Volumetric, protocol and application floods absorbed at 180 Tbps. No redirect, no BGP swing, no "attack mode" you have to remember to enable.
Managed WAF
OWASP Top 10 rulesets maintained by our threat team, virtual patching for new CVEs, and your own rules in a readable expression language.
Bot & abuse control
Behavioural scoring separates a scalper from a shopper and a cheat client from a player — challenge, tarpit, or drop, per route.
Configuration that lives in your repo
Everything in the dashboard is an API call, and every API call has a Terraform resource. Version your edge the same way you version your app — with review, staging and one-command rollback.
// Serve game patches with range-aware caching + token auth. import { edge, cache, auth } from "@nimbuscdn/edge"; export default edge.handler(async (req, ctx) => { const token = await auth.verify(req, { ttl: 900 }); if (!token.valid) return new Response("forbidden", { status: 403 }); return ctx.fetch(req, { cache: cache.tiered({ shield: "auto", // nearest regional shield ttl: "30d", surrogateKey: [`build:${ctx.params.build}`], ranges: true, // resumable downloads }), }); }); // Invalidate every PoP for one build in <300ms: // nimbus purge --key build:2026.9.1
Know what the edge did, one second later
Not a five-minute-delayed rollup. Per-request logs stream to your SIEM or object store in real time, and the dashboard queries the same pipeline.
Stream to Splunk, Datadog, S3, GCS, Kafka or an HTTPS endpoint.
No 1-in-1000 sampling. Every request, every field, retained 30 days.
Hit ratio, origin health, WAF verdicts, latency percentiles per PoP.
Enterprise plans get a named TAM and a 15-minute P1 response SLA.
Questions we get in every evaluation
For a straightforward site: change a CNAME and you are live in under ten minutes. For a large media or gaming estate we run a staged cutover — 1% of traffic, then 10%, then 50% — with a side-by-side RUM comparison at every step, so you roll forward on evidence rather than faith. Most enterprise migrations complete inside two weeks, and we do the config translation from your current vendor.
Yes, and we recommend it for anything revenue-critical. Multi-CDN is a first-class setup here: use your own traffic manager, or ours, to split by region, performance or weight. Our real-time logs export in a format your existing steering layer can consume on day one.
Unmetered on every plan, including the free Developer tier. Attack traffic is not billed as egress and there is no surge fee for being targeted. We would rather you leave protection on permanently than switch it on after the outage has already started.
SOC 2 Type II, ISO 27001 and ISO 27018, PCI DSS Level 1 for the delivery path, and GDPR-aligned processing with a standard DPA and EU/UK data residency options. Studio-grade content protection is certified for multi-DRM workflows. Reports are available under NDA.
Through licensed in-country partner capacity, with ICP filing assistance included in the onboarding. It is configured as a region in the same dashboard and reported in the same logs, so you do not end up running a second, separate CDN operation just for one market.
Put your first terabyte on the edge tonight
Free tier, no card, no sales call. Or bring us a p95 number you are unhappy with and we will benchmark against it.