Skip to content
Apex
Aether Cloud / Networking / CDN & edge
Aether Cloud · Networking

CDN & edge.

A global content and compute edge that caches and runs logic close to your users.

⌗ Networking
Overview

A global edge network that caches content and runs lightweight compute close to users — cutting latency for assets and APIs, and running inference at the edge where it counts.

Where it sits
Category
Networking
Deployment
Managed → air-gapped
Governance
IAM · encryption · audit

A CDN caches bytes. This edge can also run the model.

A content delivery network's job is to serve cached assets fast from near the user, and Aether's does that — hundreds of points of presence, tiered caching, origin shielding and instant tag-based purge. But the edge is also compute, and the interesting thing to run there is increasingly a model. Aether's edge runs functions and lightweight inference close to the request, so personalisation, classification and moderation happen at the edge instead of round-tripping to a region.

Edge inference, not just edge logic.

Plenty of edges run JavaScript. Few can run a model. Because Aether distils models to run at the edge with the full model in the cloud for the hard calls, you can do real-time inference where latency is visible to the user — recommend, translate, redact or score on the way through, not after a trip to the origin and back.

One network, one boundary.

The cache, the edge compute and the origin are one platform with one identity and one audit trail, and managed TLS is handled throughout. For workloads with residency constraints, edge processing keeps sensitive data local and sends only what's needed onward.

Worked example

Run a moderation model at the edge, on the way through — no round trip to a region.

export default aether.edge(async (req) => {
  const body = await req.json();
  const verdict = await aether.edgeModel.score("moderation", body.text);
  if (verdict.block) return new Response("blocked", { status: 451 });
  return fetch(origin, req);     // only clean traffic reaches origin
});

The moderation decision happens at the edge, near the user, before the request reaches your origin. A CDN that only runs generic logic would have to call an external model — adding the very round trip the edge exists to avoid.

How it works

Three steps to running.

01
Put assets at the edge

Cache content across hundreds of points of presence near users.

02
Run logic there

Execute functions and lightweight inference at the edge, near the request.

03
Invalidate instantly

Tag-based purge updates the whole network in seconds.

What you get

CDN & edge, in full.

Global cache

Hundreds of points of presence with smart invalidation and tiered caching.

Edge compute

Run functions and lightweight inference at the edge, near the request.

Origin shielding

Collapse origin load and absorb spikes at the edge.

Fast purge

Instant, tag-based cache invalidation across the network.

API-first

Provision it in a few lines.

Every service is reachable from the same SDK, CLI and infrastructure-as-code — one identity, one bill, one audit trail across the whole catalog.

# Provision cdn & edge on Aether Cloud
aether networking create \
  --service cdn-edge \
  --name app \
  --region us-1 \
  --deploy managed   # or vpc | on-prem | air-gapped
Specs

At a glance.

PoPs
Hundreds, global
Edge compute
Functions + light inference
Cache
Tiered + origin shield
Purge
Instant, tag-based
TLS
Managed at the edge
Use cases

Built for real work.

01

Low-latency content delivery

02

Edge personalization and inference

03

Spike absorption

Why one platform

On one model, not stitched together.

The usual stack runs cdn & edge in one product, the model in another and the data in a third — and the seams between them are the cost. Aether Cloud runs it on the same platform that serves the model, governs your identity and deploys into your boundary, with the rest of the catalog one hop away.

One platform

No stitching a vector DB to one place, a warehouse to another and a model to a third — cdn & edge sits next to the rest of the catalog, one identity, one bill.

The model is here

The provider that runs Aether runs your cdn & edge — so the data and the model never leave the same governed boundary to talk to each other.

Built on demand

Need a capability that isn’t here yet? The model writes and deploys it into the same boundary — the catalog is a starting point, not a ceiling.

FAQ

Good to know.

How does this compare to edge platforms or edge platforms?

A global cache and edge-compute network — that can run Aether inference at the edge, not just static logic.

Can I personalize at the edge?

Yes — run functions and lightweight models per request close to the user.

How fast is purge?

Instant, tag-based invalidation across the whole network.

Deploy anywhere

Your boundary, your choice.

Managed
Your VPC
On-prem
Air-gapped / sovereign

Run CDN & edge on Aether Cloud.

A global content and compute edge that caches and runs logic close to your users. Deployable managed, in your VPC, on-prem or fully air-gapped — talk to us about the configuration your workloads and your boundary require.