moq-dev · kixelated · Jul 30, 2026 · Jul 30, 2026
diff --git a/.env.live b/.env.live
@@ -1,2 +1,2 @@
-PUBLIC_RELAY_URL="https://cdn.moq.dev"
+PUBLIC_RELAY_URL="https://cdn.moq.pro"
 PUBLIC_CLOUDFLARE_URL="https://relay.cloudflare.mediaoverquic.com"
diff --git a/README.md b/README.md
@@ -5,7 +5,7 @@
 This repository contains the code for [moq.dev](https://moq.dev).
 
 This is a client only.
-You'll either need to run a local server using [moq](https://github.com/moq-dev/moq) or use a public server such as `cdn.moq.dev`.
+You'll either need to run a local server using [moq](https://github.com/moq-dev/moq) or use a public server such as `cdn.moq.pro`.
 
 Join the [Discord](https://discord.moq.dev) for updates and discussion.
 

diff --git a/src/pages/blog/cars2.mdx b/src/pages/blog/cars2.mdx
@@ -192,8 +192,8 @@ It handles discovery, routing, and proxying.
 
 You can host it yourself [and/or pay me](https://moq.pro). For example:
 - **Lightning McQueen** connects to a self-hosted moq-relay at `192.168.420.69`.
-- **moq-relay** is run with `--cluster-connect https://cdn.moq.dev/cars2`.
-- **Studio clients** (or a relay!) connects to `https://cdn.moq.dev/cars2`.
+- **moq-relay** is run with `--cluster-connect https://cdn.moq.pro/cars2`.
+- **Studio clients** (or a relay!) connects to `https://cdn.moq.pro/cars2`.
 
 Just like a tinder hookup, there's a match and now you're the sub.
 Any broadcasts published by Lightning McQueen are automatically available to all relays, potentially proxied through multiple hops.
@@ -209,7 +209,7 @@ Run a self-hosted relay at each track, aggregate all of the feeds automatically,
 
 And there's no limit to the number of connections you can establish.
 [moq-lite](https://doc.moq.dev/concept/layer/moq-lite.html) routes each subscription over the shortest path.
-Go ahead, connect to `cdn.moq.dev` and `cloudflare.mediaoverquic.com` at the same time; they sit idle until someone subscribes.
+Go ahead, connect to `cdn.moq.pro` and `cloudflare.mediaoverquic.com` at the same time; they sit idle until someone subscribes.
 
 It's like swiping right on Lightning McQueen multiple times on alt accounts.
 Don't judge.

diff --git a/src/pages/blog/first-cdn.mdx b/src/pages/blog/first-cdn.mdx
@@ -96,7 +96,7 @@ If any of these are deal breakers, then you could always run your own [moq-relay
 I've been adding new features and fixing a bunch of stuff *after* Cloudflare smashed that fork button.
 For example, authentication (via JWT) and a WebSocket fallback for Safari/TCP support.
 
-There's even a [terraform module](https://github.com/moq-dev/moq/blob/main/cdn/relay.tf) that powers `cdn.moq.dev`.
+There's even a [terraform module](https://github.com/moq-dev/moq/blob/main/cdn/relay.tf) that powers `cdn.moq.pro`.
 You too can run your own "global" CDN with 3 nodes and pay ~GCP~ Linode a boatload of money for the privilege.
 It's not *quite* as good as Cloudflare's network, currently available for free...
 

diff --git a/src/pages/blog/hash-tag-community.mdx b/src/pages/blog/hash-tag-community.mdx
@@ -173,7 +173,7 @@ I hate that I have to type out "cryptography" now thanks to "crypto" bros.
 
 When a user connects to the relay, they pass a token ([JWT](https://datatracker.ietf.org/doc/html/rfc7519)) in the URL.
 Eventually, the token will be in the `Authorization` header, but it's [not yet supported](https://github.com/w3c/webtransport/issues/263) by WebTransport.
-This token is signed by an issuer (ex. `hang.live`) and verified by the relay (ex. `cdn.moq.dev`).
+This token is signed by an issuer (ex. `hang.live`) and verified by the relay (ex. `cdn.moq.pro`).
 
 There's two types of keys you can use to sign/verify the token:
 - Symmetric keys are faster/easier but also allow the relay to sign, not just verify.

diff --git a/src/pages/blog/moq-boy.mdx b/src/pages/blog/moq-boy.mdx
@@ -86,7 +86,7 @@ But I'm HYPER-C00l, so MoqBoy instead uses MoQ's ability to live discover availa
 
 There's a separate binary for ROM.
 Right now they're all running in Texas (yeehaw).
-They connect to the closest `cdn.moq.dev` node and:
+They connect to the closest `cdn.moq.pro` node and:
 
 - Worker 1 publishes `demo/boy/big2small`.
 - Worker 2 publishes `demo/boy/opossum`.

diff --git a/src/pages/blog/moqbs.mdx b/src/pages/blog/moqbs.mdx
@@ -46,7 +46,7 @@ Then we can delete the abomination that is `MoQBS`.
 
 ## How Do Use?
 You can publish to any `moq-relay` server:
-- `https://cdn.moq.dev/anon`
+- `https://cdn.moq.pro/anon`
 - `https://draft-14.cloudflare.mediaoverquic.com`
 - `https://localhost:4443/anon` (when using `just dev`)
 

diff --git a/src/pages/blog/update-00.mdx b/src/pages/blog/update-00.mdx
@@ -44,7 +44,7 @@ Every relay would connect to every other relay, which would have resulted in:\
 Oh yeah and
 Your local relay (snug behind a firewall) can proxy all broadcasts to/from a public CDN:
 ```bash
-moq-relay --cluster-connect "https://cdn.moq.dev" ...
+moq-relay --cluster-connect "https://cdn.moq.pro" ...
 ```
 
 It'll work with any other MoQ CDN... once they implement enough of the [`moq-transport`](https://datatracker.ietf.org/doc/draft-ietf-moq-transport/) spec (Cloudflare pls).
@@ -104,10 +104,10 @@ Note that `moq-mux` is available as both a library and a CLI via [`moq-cli`](htt
 ```bash
 # Publish: pipe in a MPEG-TS file
 ffmpeg -re -i input.ts -f mpegts - | \
-    moq-cli publish --url https://cdn.moq.dev/anon --broadcast my-stream ts
+    moq-cli publish --url https://cdn.moq.pro/anon --broadcast my-stream ts
 
 # Subscribe: pull MPEG-TS back out and play it
-moq-cli subscribe --url https://cdn.moq.dev/anon --broadcast my-stream --format ts | \
+moq-cli subscribe --url https://cdn.moq.pro/anon --broadcast my-stream --format ts | \
   ffplay -
 ```
 
@@ -190,7 +190,7 @@ You can use the UI on your own site via the [web components](https://doc.moq.dev
 </script>
 
 <moq-watch-ui>
-	<moq-watch url="https://cdn.moq.dev/demo" name="bbb.hang">
+	<moq-watch url="https://cdn.moq.pro/demo" name="bbb.hang">
 		<canvas style="max-width: 100%; height: auto; margin: 0 auto; border-radius: 1rem;"></canvas>
 	</moq-watch>
 </moq-watch-ui>

diff --git a/src/pages/boy.mdx b/src/pages/boy.mdx
@@ -21,5 +21,5 @@ Click a game to play. Multiple players can play at the same time; anarchy includ
 - 💤 **On-Demand**: Nothing is emulated or encoded until at least one viewer subscribes (per track). Saves you CPU and bandwidth!
 - 🧩 **Extensible**: Player controls and game status are sent as custom tracks (JSON in this case). You can do whatever you want!
 - 🌍 **Global CDN**: A generic MoQ CDN routes subscriptions over the backbone. Every client connects to the closest edge node to maximize QoS and minimize latency.
-- 🔍 **Discoverable**: The CDN announces which games are available _and_ who wants to play. There's no custom orchestration layer; all clients connect to `cdn.moq.dev` **ONLY**.
+- 🔍 **Discoverable**: The CDN announces which games are available _and_ who wants to play. There's no custom orchestration layer; all clients connect to `cdn.moq.pro` **ONLY**.
 - 🤠 **Texas**: The emulators currently run in us-central, so your latency depends on your distance from the Lone Star State. Sorry about that euros; yee-haa.