CONCEPT — NVIDIA NEMOTRON × FASTLY EDGE

The CDN for tokens.
Cache the diff, not the whole prompt.

Nemocore.ai fuses NVIDIA Nemotron with Fastly's global network to treat inference the way the edge already treats content: classify it, diff it, route it, cache it, purge it, and protect it. Same primitives, new payload.

74%
token cost reduction cited for diff-based caching (NVIDIA Switchyard)
300+
edge locations available for geo-aware model routing
90K+
app & API deployments already protected by Fastly's WAF
Built on the same engine behind Fastly's Diff API · instant purge · real-time Varnish/Apache streams
The edge Nemocore inherits
On average<150msregional mean purge time to clear cached context globally
More than5 trilliondaily requests already served on the underlying network
Almost90%of Fastly WAF customers run in full blocking mode
Global622 Tbpsedge network capacity available for routing
Up to32%faster time-to-first-byte than other CDNs
On average<150msregional mean purge time to clear cached context globally
More than5 trilliondaily requests already served on the underlying network
Almost90%of Fastly WAF customers run in full blocking mode
Global622 Tbpsedge network capacity available for routing
Up to32%faster time-to-first-byte than other CDNs
Fastly network figures, cited as reported on fastly.com — inherited by Nemocore's edge layer, not independently measured.
Built on the same edge network already trusted by
SpaceX
Ticketmaster
GIPHY
Kayak
Priceline
Betterment
Affirm
1stDibs
Gannett | USA Today Network
Paramount
SpaceX
Ticketmaster
GIPHY
Kayak
Priceline
Betterment
Affirm
1stDibs
Gannett | USA Today Network
Paramount
The problem

Every org re-sends context it already sent.

Agent workloads resend near-identical context turn after turn — the same repo, the same policy doc, the same customer record — paying full token price every time, with no consistent policy for which model or region should even see it.

What CDNs solved decades ago
What token routing hasn't solved yet
Cache static assets at the edge
Cache prompt / context deltas near the request
Route by latency & origin health
Route by model capability, cost, and geography together
TTL & purge for stale content
TTL & purge for stale — or sensitive — context
WAF inspects traffic on ingress
Nothing inspects prompt sensitivity before it leaves the building
Fastly already proved this pattern once
Before diff-as-a-service
  • FTP pushes to refresh media and configs
  • A support ticket — sometimes a Pro-Serve engagement — just to get a purge
  • Full re-upload of assets even when one line changed
  • No visibility into what actually changed between pushes
After Fastly's Diff API
  • Instant, self-serve purge — no ticket, no waiting
  • GET /service/{id}/diff/from/{v1}/to/{v2} — line-by-line config diffs on demand
  • Real-time logs streamed straight from Varnish and Apache
  • Raw console access instead of a phone queue
How it works

Five layers, same mental model as your edge stack.

Nemocore sits in front of any model router — Nemotron, a self-hosted model, or a third-party vendor — and applies edge discipline to the data before a single token is spent. Click a layer to see it up close.

Classification Gateway

Every chunk of context is tagged — public, internal, confidential, restricted — by pattern rules plus a small local classifier that never leaves the edge node. This is the WAF, pointed at meaning instead of packets.

runs at the edge

Diff / Delta Cache

Content-addressed, hash-based store — the same lineage as Fastly's Diff API, applied to prompt context instead of service configs. If a near-identical version of this context was already sent and approved, only the delta goes out.

content-addressed

Policy Router

Routes by sensitivity tier first, cost and latency second. Restricted data never sees a vendor option. Confidential data only reaches vendors under a signed DPA with zero data retention.

tier-aware

Egress TTL + Purge

Context expires on a schedule keyed to its classification. Confidential and restricted data can be purged immediately post-task — instantly, self-serve, the same way Fastly purge replaced the old ticket queue.

policy-driven

Audit Log

Every classify → route → purge event, timestamped. The answer to "did anything confidential leave the building, and where did it go" — on demand, not by reconstruction.

compliance-ready
Security at the edge

The same edge that routes your tokens defends them.

Nemocore inherits Fastly's Next-Gen WAF and Bot Management outright — every request into the gateway gets app/API-grade protection before it ever reaches a model.

90%
of Fastly WAF customers run in full blocking mode
90K+
app & API deployments protected
7 yrs
running Gartner Customers' Choice for WAAP
235%
3-yr ROI per Forrester TEI ($4.23M net benefit)
◆

Next-Gen WAF, tuned by SmartParse

Evaluates request context and execution logic instead of static regex rules, so the gateway blocks prompt-injection and payload-smuggling attempts with near-zero manual tuning — and gets smarter through Fastly's Network Learning Exchange, threat intelligence shared anonymously across tens of thousands of agents.

Covers OWASP Top 10, account takeover, and API abuse — the same coverage protecting 90,000+ production deployments today.
◆

Bot Management for inference traffic

Automated scraping and credential-stuffing patterns aimed at a model endpoint look a lot like the bot traffic Fastly already fingerprints at the edge. Nemocore applies the same detection in front of the router — before a bot ever gets to consume a single token.

Deployment is edge-native: hybrid, agent, or cloud-only, across 100+ platforms — no separate security stack to bolt on.
Model & geography routing

Load-balance prompts the way you already load-balance traffic.

Once sensitivity is settled, Nemocore's router optimizes across Nemotron variants and third-party models by cost, latency, and region — the same origin-selection logic Fastly already runs for HTTP traffic, applied to inference.

Incoming request — classified, diffed & screened by NGWAF / Bot Management
↓ policy router decision key: sensitivity tier
RESTRICTED

Local-only Nemotron instance. Never leaves the origin network. No vendor option offered.

CONFIDENTIAL

Vendor with signed DPA + zero data retention only. Nearest compliant region wins on latency.

PUBLIC / INTERNAL

Full cost/latency optimization across Nemotron and contracted vendors, any eligible geography.

Rollout path

You don't need all five layers to get value.

Nemocore is designed to be adopted incrementally, starting inside infrastructure you already run.

01 · Classification only
Tag context before it's eligible to leave the trusted boundary — even a manual checklist beats nothing.
02 · Add the diff cache
Stop re-sending the same context turn after turn. Immediate token savings.
03 · Add TTL / purge
A scheduled sweep clears cached and logged context past its expiry.
04 · Add the policy router
Formalize the sensitivity-to-destination mapping once a primary model vendor is chosen.
05 · Layer in NGWAF + Bot Management
Turn on edge screening for prompt injection and automated abuse before it reaches the router.
06 · Audit log
Wrap the stable pipeline in logging for compliance evidence.
Company

How we became Nemocore (and not Claudeflare)

Every infrastructure company has an origin story. Ours involves a lot of rejected domain names.

Our story began like so many before us.

"Why didn't you just call it Claudeflare?" our lead investor asked. "That's the easiest mental model for me — frontier model analysis and handling, plus modern edge compute." — said in the first pitch meeting, before we owned a single domain

Sure, we could have called it Claudeflare. But something about a certain someone's relentless obsession with mentioning their founders are lawyers gave us the willies. And we never really understood what a "flare" was, beyond an SOS safety tool and/or an unwanted occurrence on the body — and we figure the AI industry's logo obsession already has that whole area of content covered.

We even bought the Claudeflair domains and commissioned a genuinely snazzy logo. Then our own relentless business acumen and hotshot team of lawyers told us to get back to work.

Domains we own and will never launch
Claudeflair.ai Dyfilis.ai LoLMe.sh Traingle.ai Herplexity.ai Derplexity.ai LLMAO.ai SomethingAIful.com Nemocore.ai

Try getting "Traingle" past autocorrect. We dare you. None of them felt quite as natural as Nemocore.

And while Nemotron and NVIDIA are central technologies and co-design partners, we are by no means bound to either. We actively encourage customers to BYO models and edge providers to the SlopChopShop for even greater savings and modularity.

Bring your own everything. Nemocore's classification, diff-cache, and policy-routing layers are model- and vendor-agnostic by design — swap in whatever frontier model or edge network fits your sensitivity tier and budget.