diff --git a/docs/superpowers/plans/2026-07-27-tbmq-io-link-migration.md b/docs/superpowers/plans/2026-07-27-tbmq-io-link-migration.md
new file mode 100644
index 0000000000..03a5b151d3
--- /dev/null
+++ b/docs/superpowers/plans/2026-07-27-tbmq-io-link-migration.md
@@ -0,0 +1,1247 @@
+# TBMQ → tbmq.io Link Migration — Pass 1 (Entry Points) Implementation Plan
+
+> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
+
+**Goal:** Point four thingsboard.io entry points that lead to TBMQ — the Products menu, the Docs menu, the docs left-panel product selector, and the Try it now TBMQ panel — at tbmq.io, routed through a single URL module so no tbmq.io URL is ever spelled twice.
+
+**Architecture:** One new module, `src/data/external-sites.ts`, owns the tbmq.io origin and two URL builders. Every call site imports from it. Four surfaces change: the two mega-menu items (through the shared `SubMenuLink.astro`), the docs product selector's `FAMILIES` array, and the Try it now TBMQ panel's 18 links. TBMQ docs stay live and fully reachable on thingsboard.io — deletion and the cross-site edge redirects are later work, captured in a removal inventory document.
+
+**Explicitly out of scope** (deferred by the user on 2026-07-27, each awaiting its own go-ahead):
+
+| Deferred | Why it is not here |
+|---|---|
+| The pricing page TBMQ toggle | Left for a later decision. The page keeps its local TBMQ sections, sub-tabs, calculators and FAQ, and the 16 `?section=tbmq-options` deep links keep working. |
+| Homepage + `/products/` ecosystem cards | Not among the four requested surfaces. |
+| The `/docs/mqtt-broker/*` edge redirect | Would take TBMQ docs offline in production the moment it deploys. It also drags 27 chaining `SINGLE_REDIRECTS` and 4 `CATCH_ALL_REDIRECTS` groups with it — all documented in Task 7's inventory. |
+| Blog posts, TBMQ docs content, `_includes` | Content edits; covered by the redirect when it lands. |
+
+Do not implement any deferred row, even if it looks like a natural extension of a task you are on. Flag it and move on.
+
+**Tech Stack:** Astro 6 + Starlight, TypeScript, SCSS, pnpm.
+
+**Spec:** `docs/superpowers/specs/2026-07-27-tbmq-io-link-migration-design.md`
+
+## Global Constraints
+
+- **No hardcoded tbmq.io URLs outside `src/data/external-sites.ts`.** Every other file imports `TBMQ_URLS`, `tbmqUrl` or `tbmqDocsUrl`. A literal `https://tbmq.io` anywhere else is a plan violation. `https://demo.tbmq.io/signup` is the one pre-existing exception and it moves *into* the module as `TBMQ_URLS.liveDemo`.
+- **Path aliases only.** Use `@data/*`, `@components/*`, `@models/*`, `@util/*`, `@root/*` per `CLAUDE.md`. Never relative paths, never the legacy `~/*` for new code. (Existing `~/*` imports in a file you touch stay as they are — do not churn them.)
+- **Tabs for indentation** in `.ts` / `.astro` files. Spaces in `.md`.
+- **External links carry both attributes:** `target="_blank" rel="noopener noreferrer"`. Never `target="_blank"` alone.
+- **Don't add narrating comments.** Comment only non-obvious *why* (a constraint, a gotcha), matching each file's existing comment density.
+- **Format after editing:** run `pnpm exec prettier -w <files you changed>`. If a file was already non-format-clean in regions you didn't touch, leave those regions alone.
+- **No TBMQ content deletion.** This plan deletes no `.mdx` doc, no asset, no pricing/installations data file. Everything removable is recorded in the inventory instead.
+- **Never run `pnpm build` / `pnpm build:fast` without asking the user first** (project build policy in `CLAUDE.md`).
+
+## Testing note — read before Task 1
+
+**This repo has no unit-test runner.** There is no `test` script, no `tests/` directory, no vitest/jest dependency. Do not invent one, and do not add a test framework — that would be a scope change nobody asked for.
+
+Verification per task is therefore:
+
+1. `pnpm check` — Astro + TypeScript type checking (catches wrong prop types, missing interface fields, bad imports)
+2. `pnpm lint:eslint` — lint, unused imports, unused vars
+3. **Grep assertions on source** — prove the old literal is gone and the helper call is present
+4. One end-to-end task at the end asserts against **built HTML** and runs the link checker
+
+Steps below give you the exact commands and the exact expected output. A step that says "Expected: no output" means the grep must find nothing — `grep` exits 1, which is success for that step.
+
+---
+
+### Task 1: The URL module
+
+**Files:**
+- Create: `src/data/external-sites.ts`
+
+**Interfaces:**
+- Consumes: nothing.
+- Produces — every later task depends on these exact names and signatures:
+  - `TBMQ_ORIGIN: string` — e.g. `'https://tbmq.io'`, never a trailing slash
+  - `tbmqUrl(path?: string): string` — absolute URL for a tbmq.io path
+  - `tbmqDocsUrl(slug?: string): string` — absolute URL under tbmq.io's TBMQ docs root
+  - `TBMQ_URLS` — readonly object with keys `product`, `docs`, `liveDemo`, all `string`
+
+- [ ] **Step 1: Write the module**
+
+Create `src/data/external-sites.ts`:
+
+```ts
+/**
+ * Sibling-site origins and URL builders.
+ *
+ * TBMQ moved to its own site (tbmq.io). Every thingsboard.io link that used to
+ * point at a local TBMQ page resolves through the helpers here, so the origin
+ * and the path shape live in exactly one place — when tbmq.io restructures,
+ * this file is the only edit.
+ *
+ * `TBMQ_SITE_URL` mirrors the `IOT_HUB_API_URL` pattern in `src/models/iot-hub.ts`:
+ * build-time `import.meta.env` with a literal fallback, no `PUBLIC_` prefix,
+ * because every URL produced here is baked into HTML at build time.
+ */
+
+const normalizeOrigin = (origin: string): string => origin.replace(/\/+$/, '');
+
+export const TBMQ_ORIGIN = normalizeOrigin(import.meta.env.TBMQ_SITE_URL ?? 'https://tbmq.io');
+
+/**
+ * tbmq.io serves the TBMQ docs under the same tree thingsboard.io used, so a
+ * slug maps across 1:1. Their `/docs/` 301s here, which is why `TBMQ_URLS.docs`
+ * can stay on the shorter, restructure-proof entry point.
+ */
+const TBMQ_DOCS_ROOT = '/docs/mqtt-broker/';
+
+/** Absolute tbmq.io URL for `path`. Leading and trailing slashes are normalized. */
+export function tbmqUrl(path = '/'): string {
+	const trimmed = path.replace(/^\/+/, '');
+	const withSlash = trimmed === '' || trimmed.endsWith('/') ? trimmed : `${trimmed}/`;
+	return `${TBMQ_ORIGIN}/${withSlash}`;
+}
+
+/**
+ * Absolute tbmq.io docs URL for a slug relative to the TBMQ docs root.
+ *   tbmqDocsUrl('installation/')    → https://tbmq.io/docs/mqtt-broker/installation/
+ *   tbmqDocsUrl('pe/installation/') → https://tbmq.io/docs/mqtt-broker/pe/installation/
+ *
+ * Query strings survive: a slug ending in `?installationType=helm` is not given
+ * a trailing slash.
+ */
+export function tbmqDocsUrl(slug = ''): string {
+	const trimmed = slug.replace(/^\/+/, '');
+	if (trimmed === '') return tbmqUrl(TBMQ_DOCS_ROOT);
+	const [pathPart, query] = trimmed.split('?');
+	const path = pathPart!.endsWith('/') ? pathPart : `${pathPart}/`;
+	return `${TBMQ_ORIGIN}${TBMQ_DOCS_ROOT}${path}${query ? `?${query}` : ''}`;
+}
+
+/**
+ * Named tbmq.io entry points. Prefer these over spelling a path at a call site.
+ * Add a key when a surface needs it — `/pricing/` and `/installations/` are
+ * deliberately absent until the pricing migration is approved.
+ */
+export const TBMQ_URLS = {
+	product: tbmqUrl('/product/'),
+	docs: tbmqUrl('/docs/'),
+	liveDemo: 'https://demo.tbmq.io/signup',
+} as const;
+```
+
+- [ ] **Step 2: Type-check and lint**
+
+```bash
+pnpm check && pnpm lint:eslint
+```
+
+Expected: both PASS. `pnpm check` reports 0 errors for `src/data/external-sites.ts`.
+
+If `import.meta.env.TBMQ_SITE_URL` produces a TS error about an unknown env key, that is the signal to check whether the repo has an `env.d.ts` declaring `ImportMetaEnv`. `src/models/iot-hub.ts` reads `import.meta.env.IOT_HUB_API_URL` with no declaration and passes, so this should pass too — do not add a declaration file unless `pnpm check` actually demands one.
+
+- [ ] **Step 3: Verify the produced values**
+
+The module can't be imported by bare `node` (`import.meta.env` is Vite-injected). Assert on the source instead — the shapes are simple enough that the type checker plus these greps are the real coverage:
+
+```bash
+grep -n "TBMQ_ORIGIN\|TBMQ_DOCS_ROOT = \|product:\|docs:\|liveDemo:" src/data/external-sites.ts
+```
+
+Expected: `TBMQ_ORIGIN` defined once from `import.meta.env.TBMQ_SITE_URL`, `TBMQ_DOCS_ROOT = '/docs/mqtt-broker/'`, and all three `TBMQ_URLS` keys present.
+
+Task 9 asserts the actual resolved strings against built HTML.
+
+- [ ] **Step 4: Format and commit**
+
+```bash
+pnpm exec prettier -w src/data/external-sites.ts
+git add src/data/external-sites.ts
+git commit -m "feat(tbmq): add central tbmq.io URL module"
+```
+
+---
+
+### Task 2: Mega-menu external-link support
+
+**Files:**
+- Modify: `src/data/navigation.ts` — `SubMenuItem` interface (~L7–13)
+- Modify: `src/components/Landing/SubMenuLink.astro`
+
+**Interfaces:**
+- Consumes: nothing from Task 1.
+- Produces: `SubMenuItem.external?: boolean`, honored by `SubMenuLink.astro`. Task 3 sets it.
+
+This is separated from Task 3 because it is a reusable capability with its own review surface: a reviewer could accept the mechanism and reject the specific links, or vice versa.
+
+- [ ] **Step 1: Add the field to the interface**
+
+In `src/data/navigation.ts`, the interface currently reads:
+
+```ts
+export interface SubMenuItem {
+	href: string;
+	icon?: string;
+	heading: string;
+	description?: string;
+	linkClass?: string;
+}
+```
+
+Add `external`:
+
+```ts
+export interface SubMenuItem {
+	href: string;
+	icon?: string;
+	heading: string;
+	description?: string;
+	linkClass?: string;
+	/** Opens in a new tab. Set for links that leave thingsboard.io. */
+	external?: boolean;
+}
+```
+
+- [ ] **Step 2: Honor it in the shared link component**
+
+`src/components/Landing/SubMenuLink.astro` currently renders:
+
+```astro
+<a class={item.linkClass} href={item.href}>
+```
+
+Change that one line to:
+
+```astro
+<a
+	class={item.linkClass}
+	href={item.href}
+	target={item.external ? '_blank' : undefined}
+	rel={item.external ? 'noopener noreferrer' : undefined}
+>
+```
+
+Leave the rest of the file untouched — the `NavIcon`, `.sub-text`, heading and description markup all stay exactly as they are.
+
+- [ ] **Step 3: Type-check and lint**
+
+```bash
+pnpm check && pnpm lint:eslint
+```
+
+Expected: both PASS. No new errors.
+
+- [ ] **Step 4: Verify nothing regressed for non-external items**
+
+```bash
+grep -c "external" src/components/Landing/SubMenuLink.astro
+```
+
+Expected: `2` (the `target` and `rel` conditionals). Every existing submenu item leaves `external` unset, so both attributes render as `undefined` and Astro omits them — internal links are byte-identical to before.
+
+- [ ] **Step 5: Format and commit**
+
+```bash
+pnpm exec prettier -w src/data/navigation.ts src/components/Landing/SubMenuLink.astro
+git add src/data/navigation.ts src/components/Landing/SubMenuLink.astro
+git commit -m "feat(nav): support external submenu links"
+```
+
+---
+
+### Task 3: Products and Docs mega-menu TBMQ items (spec items 1 and 2)
+
+**Files:**
+- Modify: `src/data/navigation.ts` — products submenu TBMQ item (~L100–106), docs submenu TBMQ item (~L405–410)
+
+**Interfaces:**
+- Consumes: `TBMQ_URLS` from Task 1; `SubMenuItem.external` from Task 2.
+- Produces: nothing new.
+
+- [ ] **Step 1: Add the import**
+
+At the top of `src/data/navigation.ts`, add:
+
+```ts
+import { TBMQ_URLS } from '@data/external-sites';
+```
+
+Place it with any other imports in the file. If the file currently has no imports, put it as the first line, followed by a blank line before the first `export interface`.
+
+- [ ] **Step 2: Repoint the Products submenu item**
+
+Find this entry in `productsSubmenu` (it is the item with `linkClass: 'mqtt-broker-lnk'` and `heading: 'TBMQ'`):
+
+```ts
+				{
+					href: '/products/mqtt-broker/',
+					icon: '/src/assets/images/landings/nav/tbmq-icon.svg',
+					heading: 'TBMQ',
+					description: 'Scalable MQTT broker',
+					linkClass: 'mqtt-broker-lnk',
+				},
+```
+
+Replace with:
+
+```ts
+				{
+					href: TBMQ_URLS.product,
+					icon: '/src/assets/images/landings/nav/tbmq-icon.svg',
+					heading: 'TBMQ',
+					description: 'Scalable MQTT broker',
+					linkClass: 'mqtt-broker-lnk',
+					external: true,
+				},
+```
+
+- [ ] **Step 3: Repoint the Docs submenu item**
+
+Find this entry in `docsSubmenu` (heading `TBMQ`, no `icon` key):
+
+```ts
+				{
+					href: '/docs/mqtt-broker/',
+					heading: 'TBMQ',
+					description: 'Scalable MQTT broker',
+					linkClass: 'mqtt-broker-lnk',
+				},
+```
+
+Replace with:
+
+```ts
+				{
+					href: TBMQ_URLS.docs,
+					heading: 'TBMQ',
+					description: 'Scalable MQTT broker',
+					linkClass: 'mqtt-broker-lnk',
+					external: true,
+				},
+```
+
+- [ ] **Step 4: Verify both literals are gone**
+
+```bash
+grep -n "mqtt-broker" src/data/navigation.ts
+```
+
+Expected: only two lines, both `linkClass: 'mqtt-broker-lnk',`. No `href: '/products/mqtt-broker/'`, no `href: '/docs/mqtt-broker/'`.
+
+- [ ] **Step 5: Type-check and lint**
+
+```bash
+pnpm check && pnpm lint:eslint
+```
+
+Expected: both PASS.
+
+- [ ] **Step 6: Format and commit**
+
+```bash
+pnpm exec prettier -w src/data/navigation.ts
+git add src/data/navigation.ts
+git commit -m "feat(nav): point TBMQ menu items at tbmq.io"
+```
+
+---
+
+### Task 4: Docs product selector (spec item 4)
+
+**Files:**
+- Modify: `src/components/VersionSwitcher.astro` — `Family` interface (~L31–43), TBMQ family entry (~L88–101), product popover `<a>` (~L250–283)
+
+**Interfaces:**
+- Consumes: `TBMQ_URLS` from Task 1.
+- Produces: `Family.externalUrl?: string`.
+
+**Critical constraint — do not remove the TBMQ `editions` array.** `currentFamily` is derived as `FAMILIES.find((f) => f.editions.some((e) => e.product === currentProduct))`. TBMQ docs are still present, so a visitor can be *on* a TBMQ docs page; emptying `editions` makes `currentFamily` `undefined` and the non-null assertion on the following line throws at build time for all 174 TBMQ pages. Only the popover link is overridden.
+
+- [ ] **Step 1: Add the import**
+
+In the frontmatter of `src/components/VersionSwitcher.astro`, alongside the existing imports:
+
+```ts
+import { TBMQ_URLS } from '@data/external-sites';
+```
+
+- [ ] **Step 2: Add `externalUrl` to the `Family` interface**
+
+The interface currently ends with:
+
+```ts
+	/** Edition to land on when this family is picked from the product dropdown.
+	 * Defaults to `editions[editions.length - 1]` (Professional/Cloud first). */
+	preferredEdition?: Products;
+}
+```
+
+Add before the closing brace:
+
+```ts
+	/** When set, picking this family from the dropdown leaves thingsboard.io.
+	 * `editions` still drives which pages belong to the family, so local docs
+	 * for it keep resolving while they exist. */
+	externalUrl?: string;
+}
+```
+
+- [ ] **Step 3: Set it on the MQTT Broker family**
+
+The entry currently reads:
+
+```ts
+	{
+		id: Products.TBMQ,
+		group: 'ecosystem',
+		name: 'MQTT Broker',
+		tagline: 'Reliable messaging for massive fleets',
+		iconId: 'tbmq',
+		editions: [
+			{ product: Products.TBMQ, label: 'Community' },
+			{ product: Products.TBMQ_PE, label: 'Professional' },
+		],
+		preferredEdition: Products.TBMQ_PE,
+	},
+```
+
+Add one line — change nothing else:
+
+```ts
+	{
+		id: Products.TBMQ,
+		group: 'ecosystem',
+		name: 'MQTT Broker',
+		tagline: 'Reliable messaging for massive fleets',
+		iconId: 'tbmq',
+		editions: [
+			{ product: Products.TBMQ, label: 'Community' },
+			{ product: Products.TBMQ_PE, label: 'Professional' },
+		],
+		preferredEdition: Products.TBMQ_PE,
+		externalUrl: TBMQ_URLS.docs,
+	},
+```
+
+- [ ] **Step 4: Use it in the product popover**
+
+The popover maps families to `<a>` elements. It currently opens:
+
+```astro
+					{FAMILIES.filter((f) => f.group === section.group).map((f) => (
+						<a
+							role="option"
+							class:list={['ps-item', { 'is-active': f.id === currentFamily.id }]}
+							href={href(preferredOf(f))}
+							aria-selected={f.id === currentFamily.id}
+						>
+```
+
+Change the `href` and add the two external attributes:
+
+```astro
+					{FAMILIES.filter((f) => f.group === section.group).map((f) => (
+						<a
+							role="option"
+							class:list={['ps-item', { 'is-active': f.id === currentFamily.id }]}
+							href={f.externalUrl ?? href(preferredOf(f))}
+							target={f.externalUrl ? '_blank' : undefined}
+							rel={f.externalUrl ? 'noopener noreferrer' : undefined}
+							aria-selected={f.id === currentFamily.id}
+						>
+```
+
+- [ ] **Step 5: Add the outbound affordance** — **NOT IMPLEMENTED (deferred 2026-07-27)**
+
+> The user asked to leave the MQTT Broker row looking like every other row for
+> now: same markup, no `↗` glyph, no `.ps-external` rule. The link still opens in
+> a new tab — only the visual affordance is missing. Keep this step written out;
+> it is the spec for adding the styling later if we decide the outbound jump
+> needs to be signposted. Everything below in this step is unbuilt.
+
+Inside the same `<a>`, the trailing check mark renders for the active family:
+
+```astro
+							{f.id === currentFamily.id && (
+								<svg class="ps-check" width="20" height="20" viewBox="0 0 20 20" aria-hidden="true">
+									<path
+										d="M4.5 10.5L8 14L15.5 6.5"
+										stroke="currentColor"
+										stroke-width="1.67"
+										stroke-linecap="round"
+										stroke-linejoin="round"
+										fill="none"
+									/>
+								</svg>
+							)}
+```
+
+Immediately **before** that block, add an outbound arrow for external families:
+
+```astro
+							{f.externalUrl && (
+								<svg class="ps-external" width="16" height="16" viewBox="0 0 16 16" aria-hidden="true">
+									<path
+										d="M6 3.5H12.5V10M12.5 3.5L4 12"
+										stroke="currentColor"
+										stroke-width="1.33"
+										stroke-linecap="round"
+										stroke-linejoin="round"
+										fill="none"
+									/>
+								</svg>
+							)}
+```
+
+Then add the style rule to the component's `<style>` block, next to the existing `.ps-check` rule. Find `.ps-check` and add after it:
+
+```scss
+	.ps-external {
+		flex-shrink: 0;
+		margin-left: auto;
+		color: var(--color-text-secondary);
+		opacity: 0.6;
+	}
+```
+
+If the existing `.ps-check` rule already sets `margin-left: auto`, drop that property from `.ps-external` so the two don't fight — check before writing.
+
+- [ ] **Step 6: Type-check and lint**
+
+```bash
+pnpm check && pnpm lint:eslint
+```
+
+Expected: both PASS. A `Property 'externalUrl' does not exist` error means Step 2 was skipped or landed in the wrong interface.
+
+- [ ] **Step 7: Verify the guard rails**
+
+```bash
+grep -n "editions: \[" src/components/VersionSwitcher.astro | wc -l
+```
+
+Expected: `8` — one per family, unchanged. TBMQ's editions must still be there.
+
+```bash
+grep -n "externalUrl" src/components/VersionSwitcher.astro
+```
+
+Expected: 6 hits — the interface field, the TBMQ assignment, the `href` fallback, the `target` conditional, the `rel` conditional, and the `{f.externalUrl && (` affordance guard. Confirm the TBMQ family is the only one assigning it.
+
+- [ ] **Step 8: Format and commit**
+
+```bash
+pnpm exec prettier -w src/components/VersionSwitcher.astro
+git add src/components/VersionSwitcher.astro
+git commit -m "feat(docs): point MQTT Broker product selector at tbmq.io"
+```
+
+---
+
+### Task 5: Try it now TBMQ panel (spec item 3)
+
+**Files:**
+- Modify: `src/data/installations.ts` — the `mqtt-broker` product block (~L611–760)
+
+**Interfaces:**
+- Consumes: `TBMQ_URLS`, `tbmqDocsUrl` from Task 1.
+- Produces: nothing new.
+
+Per the spec the panel **stays on thingsboard.io**; only its links leave. Do not delete the block, do not touch the other five product blocks, do not touch `heroImages` or `productTabs`.
+
+> **Narrowed 2026-07-27 — only the three buttons move.** The user scoped this task
+> down to Steps 1 and 3. The description's two links, the six feature links and the
+> eight deploy-card links **stay local** (`/products/mqtt-broker/`,
+> `/docs/mqtt-broker/…`) until TBMQ docs actually come down. Steps 2, 4 and 5 below
+> are the spec for that later pass — they are written out but unbuilt, and Step 6's
+> grep expectations describe the full sweep, not the current state. As built:
+> `tbmqDocsUrl(` appears twice and `TBMQ_URLS.liveDemo` once in `installations.ts`,
+> and 16 local `/docs/mqtt-broker/…` and `/products/mqtt-broker/` links remain
+> (2 in the description, 6 features, 8 deploy cards).
+
+- [ ] **Step 1: Add the import**
+
+At the top of `src/data/installations.ts`:
+
+```ts
+import { TBMQ_URLS, tbmqDocsUrl } from '@data/external-sites';
+```
+
+- [ ] **Step 2: Repoint the two links in the description string**
+
+The `description` field currently contains `href="/products/mqtt-broker/"` and `href="/docs/mqtt-broker/"`. Convert the string to a template literal and interpolate. The whole field becomes:
+
+```ts
+		description:
+			`<b>TBMQ</b> is a highly scalable and durable <a href="${TBMQ_URLS.product}" target="_blank" rel="noopener noreferrer">MQTT message broker</a> built for real-time data processing across IoT ecosystems of any scale. It efficiently handles millions of concurrent client connections and processes millions of messages per second while maintaining low latency and reliable delivery. Designed for horizontal scalability, TBMQ seamlessly expands across cluster nodes to support massive deployments with millions of connected devices. <a href="${TBMQ_URLS.docs}" target="_blank" rel="noopener noreferrer">Read more<span class="sr-only"> about TBMQ MQTT Broker</span></a>.`,
+```
+
+Note the backticks. The copy is unchanged — only the two `href` values and the quote style.
+
+- [ ] **Step 3: Repoint the three buttons**
+
+```ts
+		buttons: [
+			{
+				id: 'TryItNow_TBMQ_Demo',
+				label: 'Live Demo',
+				href: TBMQ_URLS.liveDemo,
+				target: '_blank',
+			},
+			{
+				id: 'TryItNow_TBMQ_Install_CE',
+				label: 'Download CE',
+				href: tbmqDocsUrl('installation/'),
+				target: '_blank',
+				secondary: true,
+			},
+			{
+				id: 'TryItNow_TBMQ_Install_PE',
+				label: 'Start PE Trial',
+				href: tbmqDocsUrl('pe/installation/'),
+				target: '_blank',
+				secondary: true,
+			},
+		],
+```
+
+The Live Demo URL is unchanged in value — it moves from a literal to `TBMQ_URLS.liveDemo` so the module owns it.
+
+- [ ] **Step 4: Repoint the six feature links**
+
+Replace each `href` in the two `features` columns. Keep every `title` and `description` string byte-identical:
+
+| Title | New href |
+|---|---|
+| Unlimited Horizontal Scaling | `tbmqDocsUrl('reference/100m-connections-performance-test/')` |
+| Million-Message Throughput | `tbmqDocsUrl('reference/3m-throughput-single-node-performance-test/')` |
+| Masterless High Availability | `tbmqDocsUrl('architecture/')` |
+| Universal MQTT Support | `tbmqDocsUrl('getting-started/')` |
+| Zero Data Loss Guarantee | `tbmqDocsUrl('architecture/')` |
+| K8s & Cloud Agnostic | `tbmqDocsUrl('installation/')` |
+
+- [ ] **Step 5: Repoint the eight deploy cards**
+
+Replace each `href` in `deployGroups`. Keep every `logo`, `logoAlt` and `title` byte-identical:
+
+| Title | New href |
+|---|---|
+| Docker (Linux or Mac OS) | `tbmqDocsUrl('installation/docker/')` |
+| Docker (Windows) | `tbmqDocsUrl('installation/docker-windows/')` |
+| Cluster with Docker Compose | `tbmqDocsUrl('installation/cluster/docker-compose-setup/')` |
+| Cluster setup with Minikube | `tbmqDocsUrl('installation/cluster/minikube-cluster-setup/')` |
+| Cluster setup on EKS | `tbmqDocsUrl('installation/cluster/aws-cluster-setup/')` |
+| Cluster setup on AKS | `tbmqDocsUrl('installation/cluster/azure-cluster-setup/')` |
+| Cluster setup on GCP | `tbmqDocsUrl('installation/cluster/gcp-cluster-setup/')` |
+| Cluster setup using Helm | `tbmqDocsUrl('installation/?installationType=helm')` |
+
+The Helm entry keeps its query string — `tbmqDocsUrl` splits on `?` and does not append a slash after it. That behavior is why the helper handles queries at all; if it regresses, the built URL becomes `installation/?installationType=helm/`.
+
+- [ ] **Step 6: Verify every local TBMQ link is gone**
+
+```bash
+grep -n "'/docs/mqtt-broker\|\"/docs/mqtt-broker\|'/products/mqtt-broker\|\"/products/mqtt-broker" src/data/installations.ts
+```
+
+Expected: **no output.**
+
+```bash
+grep -c "tbmqDocsUrl(" src/data/installations.ts
+```
+
+Expected: `16` (2 buttons + 6 features + 8 deploy cards).
+
+```bash
+grep -c "TBMQ_URLS\." src/data/installations.ts
+```
+
+Expected: `3` — `.product` and `.docs` in the description, `.liveDemo` in the buttons. The import line has no dot after `TBMQ_URLS`, so it does not match.
+
+- [ ] **Step 7: Type-check and lint**
+
+```bash
+pnpm check && pnpm lint:eslint
+```
+
+Expected: both PASS.
+
+- [ ] **Step 8: Format and commit**
+
+```bash
+pnpm exec prettier -w src/data/installations.ts
+git add src/data/installations.ts
+git commit -m "feat(installations): point Try it now TBMQ links at tbmq.io"
+```
+
+---
+
+### Task 6: Repo-wide hardcoded-URL audit
+
+**Files:** none modified unless a violation is found.
+
+**Interfaces:**
+- Consumes: everything from Tasks 1–5.
+- Produces: a clean invariant that Task 9 re-checks against built output.
+
+This is the Global Constraints check, run once while the changes are fresh.
+
+- [ ] **Step 1: Assert no tbmq.io literal escaped the module**
+
+```bash
+grep -rn "tbmq\.io" src/ --include="*.ts" --include="*.astro" --include="*.tsx" | grep -v "^src/data/external-sites.ts" | grep -v "^src/content/"
+```
+
+Expected: **two hits, both pre-existing and both legitimate** — `src/components/LiveDemoCard.astro` uses `demo.tbmq.io` as display copy and as a reachability probe, which is a hostname shown to the reader rather than a link target. Leave it.
+
+Any other hit is a Global Constraints violation: replace it with a helper call from `src/data/external-sites.ts`.
+
+- [ ] **Step 2: Confirm the deliberately-untouched surfaces are still untouched**
+
+```bash
+git diff --stat main...HEAD -- src/content/ | tail -3
+```
+
+Expected: **no output** — this phase edits no content file. TBMQ docs, `_includes` and blog posts are all later work.
+
+```bash
+git diff --name-only main...HEAD | sort
+```
+
+Expected exactly — five source files and the two planning documents:
+
+```
+docs/superpowers/plans/2026-07-27-tbmq-io-link-migration.md
+docs/superpowers/specs/2026-07-27-tbmq-io-link-migration-design.md
+docs/tbmq-migration/removal-inventory.md
+src/components/Landing/SubMenuLink.astro
+src/components/VersionSwitcher.astro
+src/data/external-sites.ts
+src/data/installations.ts
+src/data/navigation.ts
+```
+
+If `main` is not the right base, use the branch point: `git merge-base HEAD main`.
+
+- [ ] **Step 3: Confirm no deferred surface was touched**
+
+```bash
+git diff --name-only main...HEAD | grep -E "pricing|homeEcosystem|products/index|redirects" || echo "clean"
+```
+
+Expected: `clean`. A hit means a deferred row from the header table was implemented — revert that file. The pricing page, the two ecosystem cards and `src/data/redirects.ts` are all awaiting separate go-aheads.
+
+```bash
+git diff main...HEAD -- src/data/redirects.ts public/_redirects public/redirects.json | wc -l
+```
+
+Expected: `0`. No redirect work belongs in this phase.
+
+- [ ] **Step 4: No commit**
+
+Nothing changed. If Step 1 or 2 found a violation, fix it, then commit with `fix(tbmq): route <file> through the URL module` and re-run both steps.
+
+---
+
+### Task 7: Removal inventory document (spec item 5)
+
+**Files:**
+- Create: `docs/tbmq-migration/removal-inventory.md`
+
+**Interfaces:**
+- Consumes: nothing.
+- Produces: the phase-2 checklist.
+
+Write it by hand from the counts below. Every count was measured on this branch — re-run each command and use the number you get, so the document is true at commit time rather than copied.
+
+- [ ] **Step 1: Re-measure the counts**
+
+```bash
+find src/content/docs/docs/mqtt-broker -name "*.mdx" -not -path "*/pe/*" | wc -l   # expect 84
+find src/content/docs/docs/mqtt-broker/pe -name "*.mdx" | wc -l                    # expect 90
+find src/content/_includes/docs/mqtt-broker -name "*.mdx" | wc -l                  # expect 88
+ls src/assets/images/landings/mqtt-broker/ | wc -l                                 # expect 37
+du -sh src/assets/images/landings/mqtt-broker/                                     # expect ~2.0M
+ls src/content/blog/ | grep -ci "tbmq"                                             # expect 8
+grep -rl "docs/mqtt-broker" src/content/ | wc -l                                   # expect 219
+```
+
+- [ ] **Step 2: Write the document**
+
+Create `docs/tbmq-migration/removal-inventory.md` with these sections. Use real paths and the line numbers you verify with `grep -n` at write time — do not copy a line number without checking it.
+
+````markdown
+# TBMQ removal inventory
+
+TBMQ moved to tbmq.io. The first pass (see
+`docs/superpowers/specs/2026-07-27-tbmq-io-link-migration-design.md`) repointed four
+entry points: the Products menu, the Docs menu, the docs left-panel product
+selector, and the Try it now TBMQ panel. Everything below is still live on
+thingsboard.io and still awaiting a decision.
+
+Counts measured 2026-07-27 on branch `tbmq-migration`.
+
+## Still live, awaiting a go-ahead
+
+Each of these is independently approvable — none blocks the others:
+
+| | What | Where in this document |
+|---|---|---|
+| A | The `/docs/mqtt-broker/*` cutover redirect | § Redirects |
+| B | Pricing page TBMQ toggle | § Pricing |
+| C | Homepage + `/products/` ecosystem cards | § Marketing |
+| D | Delete the TBMQ docs, marketing pages, blog posts and assets | § Docs content, § Marketing, § Blog |
+
+**A and D are ordered:** the redirect must deploy *before* the deletion, so no
+request ever lands on a page that is already gone. **B and C are independent** of
+both and can ship at any time.
+
+## Order of operations for the full sweep (A + D)
+
+1. Add the redirects (§ Redirects) — including the chain prune, which is not
+   optional; skip it and `pnpm lint:redirects` fails.
+2. Delete content (§ Docs content, § Marketing, § Blog).
+3. Remove the plumbing (§ Sidebar, § Product plumbing) — this is what makes
+   `pnpm check` fail if a reference was missed.
+4. Delete the data files (§ Pricing, § Try it now).
+5. `pnpm generate:redirects`, then `pnpm check && pnpm lint:eslint && pnpm lint:slugcheck && pnpm lint:redirects && pnpm lint:linkcheck`.
+
+## Docs content
+
+- `src/content/docs/docs/mqtt-broker/**` — 84 CE stubs
+- `src/content/docs/docs/mqtt-broker/pe/**` — 90 PE stubs
+- `src/content/_includes/docs/mqtt-broker/**` — 88 shared include files
+
+219 files under `src/content/` reference `docs/mqtt-broker`; the splat redirects
+cover every link, so none of them needs a content edit before deletion.
+
+## Sidebar — `astro.sidebar.ts`
+
+- `tbmqSidebar` (L3803) and `tbmqPeSidebar` (L3855)
+- helpers `tbmqGuideItems` (L3568), `tbmqInstallItems` (L3683), `tbmqReferenceItems` (L3735)
+- `tbmqSidebarTabLinks` (L4339), `tbmqPeSidebarTabLinks` (L4346)
+- registrations: L4390, L4391 (tab-link map) and L4414, L4415 (sidebar spread)
+
+## Product plumbing
+
+- `src/models/site.models.ts` — `Products.TBMQ`, `Products.TBMQ_PE` and their `productDocsPrefix` entries
+- `src/util/path-utils.ts` — `productVersions` entries plus the `mqtt-broker/` prefix branches (5 sites)
+- `src/routeData.ts` — the TBMQ / TBMQ_PE path branches
+- `src/util/ogContext.ts` — `'mqtt-broker/pe/'` and `'mqtt-broker/'` in `MARKETING_ALLOWLIST`
+- `src/components/DocLink.astro` — the `TBMQ` / `TBMQ_PE` entries in the `tbBase` map
+- `src/components/VersionSwitcher.astro` — the `Products.TBMQ` family (drop the whole entry; `externalUrl` alone is no longer enough once local editions are gone)
+- `scripts/lint-linkcheck.ts` — the `/docs/mqtt-broker/` → `/docs/mqtt-broker/pe/` `consolidationPatterns` entry
+
+## Marketing
+
+- `src/pages/products/mqtt-broker/index.astro`, `privacy-policy.astro`, `terms-of-use.astro`
+- `src/pages/open-graph/_shared/marketing-meta.ts` — 3 entries (`/products/mqtt-broker/`, `…/privacy-policy/`, `…/terms-of-use/`)
+- `src/data/tbmqNews.ts`
+- `src/assets/images/landings/mqtt-broker/` — 37 files, ~2.0 MB
+
+## Blog
+
+All 8 TBMQ posts are already published on tbmq.io, so they are deleted here and
+redirected there:
+
+- `1-million-reasons-to-choose-tbmq-as-high-performance-mqtt-broker.mdx`
+- `introducing-tbmq-professional-edition-the-mqtt-broker-for-enterprise-needs.mdx`
+- `new-thingsboard-tbmq-pricing-modular-add-ons-top-ups-and-total-cost-clarity.mdx`
+- `tbmq-1-3-0-release-websocket-client-advanced-mqtt-5-features-and-more.mdx`
+- `tbmq-2-0-migration-to-redis-mqtt-5-0-support-and-more.mdx`
+- `tbmq-2-1-new-chapter-in-mqtt-messaging-with-embedded-integrations.mdx`
+- `tbmq-2-2-strengthening-mqtt-security-with-jwt-and-client-blocking.mdx`
+- `tbmq-2-3-external-authentication-bulk-provisioning-and-enterprise-audit-trails.mdx`
+
+## Pricing — item B, fully live, no decision made
+
+Nothing here has been touched. `/pricing/` still renders its TBMQ tab, its three
+sub-tabs (`tbmq-ce`, `tbmq-pe`, `tbmq-private-cloud`), all three calculators and
+the TBMQ FAQ set, and all 16 `?section=tbmq-options` deep links still resolve
+locally.
+
+Files in play when the decision comes:
+
+- `src/pages/pricing/index.astro` — the `data-product-content="tbmq"` block, `tbmqSubTabs`, and the `'tbmq-options'` entry in `sectionMap` inside the pre-paint `is:inline` resolver
+- `src/components/Pricing/ProductTabs.astro` — the `tbmq` tab entry
+- `src/data/pricing/tbmq-ce.ts`, `tbmq-self-managed.ts`, `tbmq-private-cloud.ts`
+- `src/data/pricing/faq/tbmq-ce.ts`, `tbmq-self-managed-payg.ts`, `tbmq-self-managed-perp.ts`, `tbmq-private-cloud.ts` (and their registration in `src/data/pricing/faq/index.ts`)
+- `src/components/Pricing/TbmqPaygCalculator.astro`, `TbmqPerpetualCalculator.astro`, `TbmqPrivateCloudCalculator.astro`
+- `src/scripts/pricing/calc-tbmq-payg.ts`, `calc-tbmq-pc.ts`, `calc-tbmq-perp.ts`
+- `src/assets/pricing/tbmq-icon.svg`
+- 18 local TBMQ links inside `src/data/pricing/tbmq-ce.ts` and the four `faq/tbmq-*.ts` files
+
+**Two things to know before deciding.**
+
+First, if item A (the docs redirect) ships before this, the pricing question
+partly answers itself: 9 of the 16 `?section=tbmq-options` deep links live in
+TBMQ docs `_includes`, whose pages would 301 away — so those links become
+unreachable and need no work.
+
+Second, `?section=tbmq-options` cannot be redirected at the edge. Cloudflare
+Pages `_redirects` does not match query strings. Whenever the local TBMQ pricing
+content goes, the remaining deep links need an in-page bounce instead: read the
+param in the existing pre-paint `is:inline` resolver in `pricing/index.astro` and
+`location.replace()` to tbmq.io, with the URL injected via
+`define:vars={{ tbmqPricingUrl: … }}` — the pattern already used by `Tabs.astro`,
+`DemoRequestForm.astro` and `IotHubRuntimeConfig.astro`. Pre-paint placement is
+what keeps the ThingsBoard tab from flashing first.
+
+## Marketing ecosystem cards — item C, fully live
+
+Two cards still point at the local `/products/mqtt-broker/` page:
+
+- `src/data/homeEcosystem.ts` — the homepage ecosystem card
+- `src/pages/products/index.astro` — the products-ecosystem card
+
+Both are one-line changes to `TBMQ_URLS.product`. Neither card component supports
+`target`/`rel`, so these would open in the same tab — acceptable for a body card,
+and not worth threading the plumbing through two more components.
+
+## Try it now
+
+- the `mqtt-broker` product block in `src/data/installations.ts`, and its entry in `productTabs` at the bottom of that file
+- the TBMQ hero images it references under `src/assets/images/landings/mqtt-broker/`
+
+## Redirects — item A, not yet added
+
+tbmq.io mirrors the docs tree 1:1 (`tbmq.io/docs/mqtt-broker/**`), so the whole
+cutover is prefix substitution. Nothing below exists in the repo yet.
+
+### The two splats
+
+Add to `DYNAMIC_REDIRECTS` in `src/data/redirects.ts` (46 of the 100-rule
+Cloudflare dynamic budget in use today, so this lands at 48):
+
+```
+/docs/mqtt-broker/*    → https://tbmq.io/docs/mqtt-broker/:splat 301
+/docs/pe/mqtt-broker/* → https://tbmq.io/docs/mqtt-broker/pe/:splat 301
+```
+
+They **must** go in `DYNAMIC_REDIRECTS`, not `NON_DOCS_REDIRECTS`:
+`astro.redirects.ts` feeds `NON_DOCS_REDIRECTS` to Astro's `redirects:` config,
+where a splat over `/docs/mqtt-broker/*` collides with the real content routes.
+Keeping them out of the Astro config also means `pnpm dev`, `pnpm preview` and
+`pnpm lint:linkcheck` still see the real TBMQ pages — the link checker stays
+green and the docs remain browsable locally.
+
+### The chain prune — not optional
+
+`src/data/redirects.ts` already holds **27 `SINGLE_REDIRECTS` whose targets sit
+under `/docs/mqtt-broker/`** (`/docs/mqtt-broker/api/ → /docs/mqtt-broker/rest-api/`,
+`…/faq/ → …/why-tbmq/`, and 25 more), plus **4 `CATCH_ALL_REDIRECTS` groups**:
+`mqtt-broker/install`, `mqtt-broker/pe/install`, `pe/mqtt-broker/install`,
+`pe/mqtt-broker`.
+
+Add the splats without touching them and every one becomes a redirect chain:
+`pnpm lint:redirects` fails, and real visitors pay two round-trips.
+
+Delete all 31. This is safe because **tbmq.io carries the identical legacy
+redirect table** — verified: `/docs/mqtt-broker/api/ → /docs/mqtt-broker/rest-api/`
+is present in their `public/_redirects` too. So the splat forwards the legacy
+shape across and tbmq.io resolves it on their side.
+
+Regenerate the counts before trusting these numbers:
+
+```bash
+node --experimental-transform-types -e "
+import('./src/data/redirects.ts').then(m => {
+  const t = s => (s ?? '').includes('mqtt-broker');
+  console.log('singles targeting /docs/mqtt-broker/:',
+    m.SINGLE_REDIRECTS.filter(e => e.target.startsWith('/docs/mqtt-broker/')).length);
+  console.log('catch-all groups touching mqtt-broker:',
+    m.CATCH_ALL_REDIRECTS.filter(g => t(g.oldPrefix) || t(g.newPrefix)).length);
+});
+"
+```
+
+Deleting the singles also drops them from `public/redirects.json`, which *is*
+spread into `astro.redirects.ts` — so those legacy URLs stop resolving in
+`pnpm dev` / `pnpm preview`. They are inbound-only Jekyll-era URLs and nothing in
+the repo links to them, but confirm with `pnpm lint:linkcheck` rather than
+assuming.
+
+Also prune the five `/docs/*/search/` entries in `devFallbackRedirects` in
+`astro.redirects.ts` that mention `mqtt-broker`.
+
+### Marketing and blog
+
+Add to `NON_DOCS_REDIRECTS`:
+
+```
+/products/mqtt-broker/ → https://tbmq.io/product/ 301
+/blog/<each of the 8 slugs above>/ → https://tbmq.io/blog/<slug>/ 301
+```
+
+### Sequencing
+
+Cloudflare applies redirect rules regardless of whether a file exists at the
+path, so the splats take effect the moment they deploy — TBMQ docs go dark on
+thingsboard.io immediately, which is why they land *before* the content deletion,
+not after.
+
+One loose end to decide at that point: the TBMQ pages are still built and still
+in the sitemap, so crawlers get pointed at URLs that 301 cross-domain until the
+deletion lands. Either accept it for the gap, or give those pages a cross-site
+`<link rel="canonical">` — the sitemap integration only includes pages that are
+self-canonical, so a cross-site canonical drops them automatically.
+````
+
+- [ ] **Step 3: Verify no placeholders**
+
+```bash
+grep -n "TBD\|TODO\|FIXME\|XXX" docs/tbmq-migration/removal-inventory.md
+```
+
+Expected: **no output.**
+
+- [ ] **Step 4: Spot-check three line references**
+
+Pick any three `astro.sidebar.ts` line numbers you wrote and confirm each:
+
+```bash
+sed -n '3803p;3855p;4339p' astro.sidebar.ts
+```
+
+Expected: the `export const tbmqSidebar`, `export const tbmqPeSidebar` and `export const tbmqSidebarTabLinks` declarations. If a number is off, fix the document — a stale line reference is worse than none.
+
+- [ ] **Step 5: Commit**
+
+```bash
+git add docs/tbmq-migration/removal-inventory.md
+git commit -m "docs(tbmq): add phase-2 removal inventory"
+```
+
+---
+
+### Task 8: Static verification sweep
+
+**Files:** none modified.
+
+**Interfaces:**
+- Consumes: Tasks 1–7.
+- Produces: green CI-equivalent checks.
+
+- [ ] **Step 1: Run the full CI set**
+
+```bash
+pnpm check && pnpm lint:eslint && pnpm lint:slugcheck
+```
+
+Expected: all three PASS. These are exactly what GitHub Actions runs, so a failure here fails the PR.
+
+- [ ] **Step 2: If anything fails, fix it before continuing**
+
+Do not proceed to Task 9 with a red check. A build takes minutes; a type error found now costs seconds.
+
+- [ ] **Step 3: No commit unless a fix was needed**
+
+If you fixed something, commit it with a `fix(...)` message scoped to the file.
+
+---
+
+### Task 9: Built-output verification
+
+**Files:** none modified.
+
+**Interfaces:**
+- Consumes: Tasks 1–8.
+- Produces: evidence that the resolved URLs are correct in real HTML.
+
+This is where Task 1's URL builders are actually tested — against rendered output rather than source.
+
+- [ ] **Step 1: Ask the user before building**
+
+`CLAUDE.md` requires it. Ask: "Run `pnpm build:fast` to verify, or skip?" Wait for the answer. If they skip, note in the final report that built-output verification did not run, and stop here.
+
+- [ ] **Step 2: Build**
+
+```bash
+pnpm build:fast
+```
+
+Expected: completes with no errors.
+
+- [ ] **Step 3: Assert the mega-menu links resolved**
+
+```bash
+grep -o 'href="https://tbmq.io/product/"[^>]*' dist/index.html | head -2
+grep -o 'href="https://tbmq.io/docs/"[^>]*' dist/index.html | head -2
+```
+
+Expected: both found, each carrying `target="_blank"` and `rel="noopener noreferrer"`. The mega-menu renders on every page, so `dist/index.html` is a valid sample.
+
+- [ ] **Step 4: Assert the docs product selector resolved**
+
+```bash
+grep -o 'href="https://tbmq.io/docs/"[^>]*' dist/docs/index.html | head -2
+```
+
+Expected: found with `target="_blank"` and `rel="noopener noreferrer"` — this is the Ecosystem → MQTT Broker row in the product popover.
+
+- [ ] **Step 5: Assert the Try it now links resolved, including the query-string edge case**
+
+```bash
+grep -c 'https://tbmq.io/docs/mqtt-broker/' dist/installations/index.html
+grep -o 'https://tbmq.io/docs/mqtt-broker/installation/?installationType=helm' dist/installations/index.html
+```
+
+Expected: first ≥ 16. Second must match **exactly** — no trailing slash after `helm`. A hit of `…?installationType=helm/` means `tbmqDocsUrl` mishandled the query string; fix the helper in `src/data/external-sites.ts`, not the call site.
+
+- [ ] **Step 6: Assert the deferred surfaces are byte-identical**
+
+The two surfaces left for a later decision must come out of this build unchanged:
+
+```bash
+grep -c 'data-product-content="tbmq"' dist/pricing/index.html
+grep -o 'href="/products/mqtt-broker/"' dist/index.html dist/products/index.html | wc -l
+grep -c 'tbmq\.io' dist/pricing/index.html
+```
+
+Expected: `1` (the local TBMQ pricing block still renders), `2` (both ecosystem cards still point locally), `0` (no tbmq.io URL leaked into the pricing page). Any other result means a deferred row from the header table was implemented.
+
+- [ ] **Step 7: Assert the TBMQ docs are still reachable**
+
+```bash
+test -f dist/docs/mqtt-broker/index.html && echo "TBMQ docs built"
+grep -c "mqtt-broker" dist/_redirects
+```
+
+Expected: `TBMQ docs built`, and the `dist/_redirects` count **unchanged from `main`** — compare with `git show main:public/_redirects | grep -c mqtt-broker`. No cutover redirect belongs in this phase.
+
+- [ ] **Step 8: Run the link checker**
+
+```bash
+pnpm lint:linkcheck:nobuild
+```
+
+Expected: PASS. `pnpm build:fast` in Step 2 already produced `dist/`, so the `:nobuild` variant is right. tbmq.io URLs are skipped as external hosts (`scripts/lint-linkcheck.ts` only treats `PROD_ORIGIN` and `additionalLocalHosts` as local), so they cannot fail here — what this catches is an internal link accidentally broken along the way.
+
+- [ ] **Step 9: Manual smoke check**
+
+Report to the user which surfaces to click through, since only they can eyeball rendering:
+
+1. Products menu → TBMQ → `tbmq.io/product/` in a new tab
+2. Docs menu → TBMQ → `tbmq.io/docs/` in a new tab
+3. Any docs page → left-panel product selector → Ecosystem → MQTT Broker → `tbmq.io/docs/`, with the ↗ affordance visible in the popover row
+4. `/installations/?product=mqtt-broker` → panel still renders locally; every CTA, feature link and deploy card opens tbmq.io
+5. Any TBMQ docs page (e.g. `/docs/mqtt-broker/getting-started/`) → still loads normally; the edition pills still switch Community ↔ Professional locally
+6. `/pricing/` → unchanged: TBMQ tab still switches to local sections, all three sub-tabs and calculators work
+
+- [ ] **Step 10: No commit**
+
+Verification only. Any fix gets its own scoped commit and a re-run of the affected assertions.
+
+---
+
+## Self-Review
+
+**Requested-scope coverage** (the four surfaces the user asked for on 2026-07-27):
+
+| Requested surface | Task |
+|---|---|
+| Products menu → TBMQ | 2, 3 |
+| Docs menu → TBMQ | 2, 3 |
+| Docs left-panel product selector → MQTT Broker | 4 |
+| Try it now TBMQ panel, 18 links | 5 |
+| Supporting: central URL module | 1 |
+| Supporting: no-hardcoded-URL audit + deferred-surface guard | 6 |
+| Supporting: inventory of everything still live | 7 |
+| Supporting: verification | 8, 9 |
+
+**Deferred-scope coverage** — each row of the header table is documented in Task 7's inventory, not implemented: pricing (§ Pricing, item B), ecosystem cards (§ Marketing ecosystem cards, item C), the docs cutover redirect and its 31-entry chain prune (§ Redirects, item A), content deletion (§ Docs content, § Blog, item D). Tasks 6 and 9 both assert that none of them was touched.
+No gaps.
+
+**Placeholder scan:** No TBD/TODO. Every code step carries the actual code. Every verification step carries the actual command and expected output. Task 7's document body is written out in full rather than described.
+
+**Type consistency:** `tbmqUrl` / `tbmqDocsUrl` / `TBMQ_URLS` / `TBMQ_ORIGIN` are defined in Task 1 and used with those exact names in Tasks 3, 4 and 5. `TBMQ_URLS` has exactly three keys — `product` (Task 3), `docs` (Tasks 3, 4), `liveDemo` (Task 5) — and every one is consumed, so no unused key ships. `SubMenuItem.external` is defined in Task 2 and set in Task 3. `Family.externalUrl` is defined and consumed within Task 4.
+
+**Two risks worth flagging to the reviewer:**
+
+1. **Task 4 must not empty the TBMQ `editions` array.** `currentFamily` is derived by matching the URL's product against `editions`, and TBMQ docs are still live — emptying it makes `currentFamily` undefined and the following non-null assertion throws at build time for all 174 TBMQ pages. Task 4's Step 7 grep is the guard.
+2. **Scope creep is the main failure mode here.** Four of the original twelve tasks were cut, and the cut work is adjacent to the surviving work: an implementer in `installations.ts` may notice the pricing FAQ links, and one in `VersionSwitcher.astro` may reason that the redirect "should" come too. Tasks 6 and 9 exist to catch that, but the header table is the instruction — flag, don't implement.
+
+---
+
+## Appendix — testing the cutover redirects locally (no tbmq.io instance needed)
+
+*Added 2026-07-30, after the phase-2 cutover landed in `src/data/redirects.ts`.*
+
+The five TBMQ cutover splats live only in `public/_redirects`, which only the
+Cloudflare edge executes — `pnpm dev` never reads that file, so on localhost the
+splat-covered URLs (e.g. `/docs/mqtt-broker/install/`) 404 instead of 301-ing.
+Exact-path singles are unaffected (they flow through `redirects.json` into the
+Astro config and redirect in dev).
+
+To exercise the splats locally, drop this **temporary** middleware in as
+`src/middleware.ts` and restart the dev server (a new middleware file is not
+picked up by HMR — restart is required):
+
+```ts
+import { defineMiddleware } from 'astro:middleware';
+import { DYNAMIC_REDIRECTS } from '@data/redirects.ts';
+
+// TEMPORARY — dev-only emulation of the Cloudflare edge for cross-origin splat
+// rules (the TBMQ cutover group). Astro never reads public/_redirects, so this
+// applies the same first-match 301s on localhost. Delete this file after
+// testing: while it is active, every /docs/mqtt-broker/* page redirects away
+// to tbmq.io in dev and `pnpm lint:linkcheck` will fail.
+
+const crossOriginRules = DYNAMIC_REDIRECTS.flatMap((group) => group.entries).filter((entry) =>
+	entry.target.startsWith('http'),
+);
+
+function toRegex(source: string): RegExp {
+	let body = source.replace(/[.+^${}()|[\]\\]/g, '\\$&');
+	body = body.replace(/\*/g, '(.*)');
+	body = body.replace(/:[A-Za-z_][A-Za-z0-9_]*/g, '[^/]+');
+	return new RegExp(`^${body}$`);
+}
+
+const compiled = crossOriginRules.map((rule) => ({
+	regex: toRegex(rule.source),
+	target: rule.target,
+	status: (rule.status ?? 301) as 301,
+}));
+
+export const onRequest = defineMiddleware((context, next) => {
+	if (!import.meta.env.DEV) return next();
+	const { pathname } = context.url;
+	for (const rule of compiled) {
+		const match = rule.regex.exec(pathname);
+		if (match) {
+			return context.redirect(rule.target.replace(':splat', match[1] ?? ''), rule.status);
+		}
+	}
+	return next();
+});
+```
+
+It reads the cross-origin rules straight out of `DYNAMIC_REDIRECTS` (no copy to
+drift), compiles the splat patterns with the same regex semantics as
+`scripts/check-redirect-chains.ts`, and applies them first-match — including
+Cloudflare's "redirect wins over an existing page" behavior.
+
+Verification (all against `http://localhost:4321`):
+
+```bash
+# Splat with empty tail → docs root of the renamed prefix
+curl -s -o /dev/null -w "%{http_code} %{redirect_url}\n" http://localhost:4321/docs/mqtt-broker/install/
+# Expected: 301 https://tbmq.io/docs/installation/
+
+# Jekyll install-rename must win over the generic pe splat (first-match order)
+curl -s -o /dev/null -w "%{http_code} %{redirect_url}\n" http://localhost:4321/docs/pe/mqtt-broker/install/docker/
+# Expected: 301 https://tbmq.io/docs/pe/installation/docker/
+
+# Redirect beats a still-existing local page, like the Cloudflare edge
+curl -s -o /dev/null -w "%{http_code} %{redirect_url}\n" http://localhost:4321/docs/mqtt-broker/getting-started/
+# Expected: 301 https://tbmq.io/docs/getting-started/
+
+# Non-TBMQ pages unaffected
+curl -s -o /dev/null -w "%{http_code}\n" http://localhost:4321/docs/getting-started/
+# Expected: 200
+```
+
+Caveats while the file exists:
+
+- The browser follows the 301 into a DNS error until tbmq.io is live — assert on
+  the `Location` header (curl or the devtools Network tab), not on the final page.
+- `pnpm lint:linkcheck` fails (every TBMQ docs link redirects away). Don't run it.
+- **Never commit `src/middleware.ts`** — it is a test harness, not a feature.
+
+Cleanup: delete `src/middleware.ts` and restart the dev server. Re-run the first
+curl above — it must 404 again (splats are edge-only), and
+`/docs/mqtt-broker/getting-started/` must 200.
diff --git a/docs/superpowers/specs/2026-07-27-tbmq-io-link-migration-design.md b/docs/superpowers/specs/2026-07-27-tbmq-io-link-migration-design.md
new file mode 100644
index 0000000000..91a592b9c2
--- /dev/null
+++ b/docs/superpowers/specs/2026-07-27-tbmq-io-link-migration-design.md
@@ -0,0 +1,274 @@
+# TBMQ → tbmq.io link migration — pass 1 (entry points)
+
+**Date:** 2026-07-27
+**Branch:** `tbmq-migration`
+**Status:** approved
+
+## Problem
+
+TBMQ is moving off thingsboard.io onto its own site, `tbmq.io` (local clone at
+`../tbmq.io`). Every thingsboard.io surface that points at a TBMQ product page,
+TBMQ docs page or TBMQ pricing must send visitors to tbmq.io instead.
+
+The TBMQ docs and marketing pages currently hosted on thingsboard.io will be
+deleted in a later phase. Before that deletion, we need a written index of
+everything that has to go, so the removal is a mechanical sweep rather than a
+rediscovery exercise.
+
+## Constraints and findings
+
+**tbmq.io mirrors the docs tree 1:1.** ~~`tbmq.io/docs/mqtt-broker/**` has the
+same shape as thingsboard.io's. tbmq.io also 301s its own `/docs/` →
+`/docs/mqtt-broker/` and `/products/mqtt-broker/` → `/`.~~ Every deep doc link
+maps by prefix substitution — no per-page mapping table is needed, now or at
+deletion time.
+
+> **Corrected 2026-07-28.** tbmq.io carries **no `mqtt-broker/` segment**: it is a
+> TBMQ-only site, so `/docs/mqtt-broker/<slug>` here is `/docs/<slug>` there, and
+> the product landing is the site root `/`, not `/product/`. Prefix substitution
+> still holds — the prefix is just shorter. Everything below that spells
+> `tbmq.io/docs/mqtt-broker/…` or `tbmq.io/product/` is superseded; the live shape
+> is whatever `src/data/external-sites.ts` builds, and the phase-2 redirect targets
+> in `docs/tbmq-migration/removal-inventory.md` have been updated to match.
+
+**No hardcoded URLs.** The repo's established pattern for a value that must not
+be spelled twice is a single exported constant consumed everywhere:
+`PROD_ORIGIN` in `src/consts.ts`, `src/data/versions.ts` for version strings,
+`src/data/redirects.ts` as the redirect single source of truth. Absolute
+external redirect targets already exist (`'/support-ukraine/':
+'https://u24.gov.ua/'`), so nothing new is needed at the redirect layer.
+
+**Entry points funnel through few files.** The Products and Docs mega-menu
+items both render through `SubMenuLink.astro`; the docs product selector is one
+entry in the `FAMILIES` array in `VersionSwitcher.astro`; the pricing toggle is
+`ProductTabs.astro` plus an inline script in `pricing/index.astro`.
+
+**The link checker ignores other hosts.** `scripts/lint-linkcheck.ts` treats
+non-local hosts as external and does not fetch them, so absolute `tbmq.io` URLs
+keep `pnpm lint:linkcheck` green.
+
+## Scope
+
+**Revised 2026-07-27**, after the user narrowed the first pass to four surfaces
+and deferred the rest. This pass ships:
+
+1. Products mega-menu → TBMQ
+2. Docs mega-menu → TBMQ
+3. Docs left-panel product selector → MQTT Broker
+4. Try it now TBMQ panel (18 links)
+
+TBMQ docs stay live and fully reachable on thingsboard.io. Deep links between doc
+pages keep resolving locally.
+
+**Deferred, each awaiting its own go-ahead:**
+
+| Deferred | Notes |
+|---|---|
+| Pricing page TBMQ toggle | Left for a later decision. The page keeps its local TBMQ sections, sub-tabs, calculators and FAQ, and all 16 `?section=tbmq-options` deep links keep working. Design retained in § F. |
+| Homepage + `/products/` ecosystem cards | Not among the four requested surfaces. Design retained in § F. |
+| `/docs/mqtt-broker/*` cutover redirect | Design in § D. |
+| Deleting TBMQ docs, marketing pages, blog posts, assets | Inventory in § E. |
+
+Rationale for holding the redirect: it would make the still-present TBMQ docs
+unreachable in production the moment it deploys, because Cloudflare Pages applies
+redirect rules regardless of whether an asset exists at the path. It also drags 27
+chaining `SINGLE_REDIRECTS` and 4 `CATCH_ALL_REDIRECTS` groups with it (§ D).
+
+## Design
+
+### A. Central URL module
+
+New file `src/data/external-sites.ts` — the only place a tbmq.io URL is spelled.
+
+```ts
+export const TBMQ_ORIGIN = normalizeOrigin(import.meta.env.TBMQ_SITE_URL ?? 'https://tbmq.io');
+
+export function tbmqUrl(path = '/'): string;      // tbmqUrl('/product/')
+export function tbmqDocsUrl(slug = ''): string;   // tbmqDocsUrl('pe/installation/')
+
+export const TBMQ_URLS = {
+  product:  tbmqUrl('/product/'),
+  docs:     tbmqUrl('/docs/'),
+  liveDemo: 'https://demo.tbmq.io/signup',
+} as const;
+```
+
+`tbmqDocsUrl('installation/')` resolves to
+`https://tbmq.io/docs/mqtt-broker/installation/`. Call sites express intent
+(`tbmqDocsUrl('pe/installation/')`), never a URL string.
+
+The `TBMQ_SITE_URL` override follows the `IOT_HUB_API_URL` precedent in
+`src/models/iot-hub.ts` — build-time `import.meta.env` with a literal fallback, no
+`PUBLIC_` prefix, because every URL this module produces is baked into HTML at
+build time. A future client-side consumer (the pricing bounce in § F) receives its
+value through Astro `define:vars` rather than needing a public env var.
+
+Both helpers normalise slashes so callers may pass a slug with or without
+leading/trailing `/`. `TBMQ_ORIGIN` never carries a trailing slash.
+
+The bare docs entry uses `/docs/` rather than `/docs/mqtt-broker/`. tbmq.io
+301s it on their side, and `/docs/` is the URL that survives a future
+restructure of their docs tree. Switching to the no-hop target is a one-line
+change in this file.
+
+### B. Entry-point changes
+
+| Item | File | Change |
+|---|---|---|
+| 1 | `src/data/navigation.ts` (~L101) | Products submenu TBMQ item: `href: TBMQ_URLS.product`, `external: true` |
+| 2 | `src/data/navigation.ts` (~L406) | Docs submenu TBMQ item: `href: TBMQ_URLS.docs`, `external: true` |
+| 1, 2 | `src/data/navigation.ts` `SubMenuItem` | add optional `external?: boolean` |
+| 1, 2 | `src/components/Landing/SubMenuLink.astro` | emit `target="_blank" rel="noopener noreferrer"` when `item.external` |
+| 3 | `src/data/installations.ts` (TBMQ block, ~L611–760) | 18 URLs through the helpers: 2 in the HTML description, 2 of 3 buttons (Live Demo already external), 6 feature links, 8 deploy cards. The TBMQ panel itself stays on thingsboard.io |
+| 4 | `src/components/VersionSwitcher.astro` | add `externalUrl?: string` to the `Family` interface; the MQTT Broker family gets `externalUrl: TBMQ_URLS.docs`; the product popover row uses it with `target`/`rel` and an outbound affordance |
+
+**VersionSwitcher constraint:** the TBMQ family's `editions` array must stay
+intact. `currentFamily` is derived by finding the family whose editions contain
+the product parsed from the URL; with TBMQ docs still present, emptying that array
+would leave `currentFamily` undefined and break every TBMQ docs page. Only the
+popover link is overridden.
+
+**`TBMQ_URLS` carries only what is consumed** — `product`, `docs`, `liveDemo`.
+`pricing` and `installations` are added when the surfaces that need them are
+approved.
+
+### C. Content links are not edited
+
+**Blog posts and docs content are deliberately excluded.** Zero non-TBMQ docs
+pages link to `/docs/mqtt-broker/` — verified. All 212 in-content link sources sit
+inside the TBMQ trees themselves (168 doc stubs, 44 `_includes`), plus 7 blog
+posts, and all 8 TBMQ blog posts are already duplicated on tbmq.io. So every one
+of them is content scheduled for deletion; editing their links is wasted work.
+
+Worse, markdown link destinations cannot call a helper, so repointing the blog
+posts would mean 34 hardcoded `https://tbmq.io/...` strings in content — precisely
+what § A exists to prevent. The § D splats cover them for free.
+
+### D. The docs cutover redirect (deferred)
+
+Links *inside* the TBMQ docs tree (219 files reference `/docs/mqtt-broker`) are
+not edited. They are covered wholesale by three edge rules:
+
+```
+/docs/mqtt-broker/*    → https://tbmq.io/docs/mqtt-broker/:splat 301
+/docs/pe/mqtt-broker/* → https://tbmq.io/docs/mqtt-broker/pe/:splat 301
+/products/mqtt-broker/ → https://tbmq.io/product/ 301
+```
+
+The two `/docs/` splats belong in `DYNAMIC_REDIRECTS` in `src/data/redirects.ts`
+(46 of the 100-rule Cloudflare dynamic budget currently used, so this lands at
+48); `/products/mqtt-broker/` is static and goes in `NON_DOCS_REDIRECTS`. The
+splats must **not** go in `NON_DOCS_REDIRECTS`, which `astro.redirects.ts` feeds
+to Astro's `redirects:` config — a splat there collides with the real content
+routes. Keeping them out of the Astro config also leaves `pnpm dev`,
+`pnpm preview` and `pnpm lint:linkcheck` seeing the real TBMQ pages.
+
+**The chain prune is part of this, not optional.** `src/data/redirects.ts` already
+holds 27 `SINGLE_REDIRECTS` whose targets sit under `/docs/mqtt-broker/`, plus 4
+`CATCH_ALL_REDIRECTS` groups (`mqtt-broker/install`, `mqtt-broker/pe/install`,
+`pe/mqtt-broker/install`, `pe/mqtt-broker`). Add the splats without touching them
+and every one becomes a redirect chain: `pnpm lint:redirects` fails and visitors
+pay two round-trips. All 31 get deleted — safe because tbmq.io carries the
+identical legacy redirect table (verified: `/docs/mqtt-broker/api/ →
+/docs/mqtt-broker/rest-api/` is in their `public/_redirects` too), so the splat
+forwards the legacy shape across and tbmq.io resolves it.
+
+Deleting the singles also drops them from `public/redirects.json`, which *is*
+spread into `astro.redirects.ts`, so those Jekyll-era URLs stop resolving in dev
+and preview. Nothing in the repo links to them; confirm with `pnpm lint:linkcheck`
+rather than assuming.
+
+The 8 TBMQ blog posts get one static rule each, in `NON_DOCS_REDIRECTS`:
+
+```
+/blog/<slug>/ → https://tbmq.io/blog/<slug>/ 301
+```
+
+for `1-million-reasons-to-choose-tbmq-as-high-performance-mqtt-broker`,
+`introducing-tbmq-professional-edition-the-mqtt-broker-for-enterprise-needs`,
+`new-thingsboard-tbmq-pricing-modular-add-ons-top-ups-and-total-cost-clarity`,
+`tbmq-1-3-0-release-websocket-client-advanced-mqtt-5-features-and-more`,
+`tbmq-2-0-migration-to-redis-mqtt-5-0-support-and-more`,
+`tbmq-2-1-new-chapter-in-mqtt-messaging-with-embedded-integrations`,
+`tbmq-2-2-strengthening-mqtt-security-with-jwt-and-client-blocking`,
+`tbmq-2-3-external-authentication-bulk-provisioning-and-enterprise-audit-trails`.
+
+### E. Removal inventory
+
+New file `docs/tbmq-migration/removal-inventory.md`, hand-written, grouped by
+area with counts and line references:
+
+- **Docs content** — 84 CE + 90 PE stubs under `src/content/docs/docs/mqtt-broker/**`; 88 files under `src/content/_includes/docs/mqtt-broker/**`
+- **Sidebar** — `astro.sidebar.ts`: `tbmqSidebar` (L3803), `tbmqPeSidebar` (L3855), helpers `tbmqGuideItems` / `tbmqInstallItems` / `tbmqReferenceItems` (L3568 / L3683 / L3735), tab links (L4339 / L4346), registrations (L4390 / L4391 / L4414 / L4415)
+- **Product plumbing** — `Products.TBMQ` / `TBMQ_PE` in `src/models/site.models.ts`; `src/util/path-utils.ts` (5 sites); `src/routeData.ts`; `src/util/ogContext.ts`; the `tbBase` map in `src/components/DocLink.astro`; the `VersionSwitcher` family; the `/docs/mqtt-broker/` entry in the link checker's `consolidationPatterns`
+- **Marketing** — `src/pages/products/mqtt-broker/{index,privacy-policy,terms-of-use}.astro`; 3 entries in `src/pages/open-graph/_shared/marketing-meta.ts`; `src/data/tbmqNews.ts`; 37 assets (2.0 MB) in `src/assets/images/landings/mqtt-broker/`
+- **Pricing** — 3 data files, 4 FAQ files, 3 calculator components, 3 calculator scripts, the TBMQ sections and `tbmqSubTabs` in `src/pages/pricing/index.astro`, and the `tbmq` tab in `ProductTabs.astro` — all still live
+- **Try it now** — the `mqtt-broker` product block in `src/data/installations.ts`
+- **Blog** — 8 TBMQ posts under `src/content/blog/`, all already live on tbmq.io (slugs listed in § D)
+- **Redirects** — the 31 chaining entries to prune, the 5 `mqtt-broker` entries in `devFallbackRedirects` in `astro.redirects.ts`, plus every rule from § D verbatim
+
+### F. Deferred designs, retained
+
+These were designed in full before being deferred. The inventory carries them so
+the reasoning is not re-derived when the go-ahead comes.
+
+**Pricing toggle.** `ProductTabs.astro` tab entries gain an optional `href`; a tab
+with one renders an `<a>` (no `product-tab` class, no `data-product` — both are
+local-switch hooks) to `tbmq.io/pricing/`. `pricing/index.astro` drops the
+`data-product-content="tbmq"` block, `tbmqSubTabs`, the three calculator mounts,
+the now-unused imports and the `'tbmq-options'` entry in `sectionMap`.
+
+The removal must be from the render, not `display:none` — left in, the block keeps
+roughly 18 crawlable links to local TBMQ docs in the DOM.
+
+`?section=tbmq-options` (optionally `&product=tbmq-*`) is linked from 16 places: 9
+TBMQ docs `_includes`, 3 blog posts, 4 spots on the TBMQ product landing page.
+Cloudflare Pages `_redirects` cannot match query strings, so the bounce goes in the
+existing pre-paint `is:inline` resolver in `pricing/index.astro`:
+`location.replace()` when the param matches, with the URL injected via
+`define:vars={{ tbmqPricingUrl: … }}` — the pattern already used by `Tabs.astro`,
+`DemoRequestForm.astro` and `IotHubRuntimeConfig.astro`. Pre-paint placement is
+what keeps the ThingsBoard tab from flashing first.
+
+If § D ships first, 9 of those 16 links become unreachable on their own — their
+source pages 301 away — so this shrinks to 7.
+
+**Ecosystem cards.** `src/data/homeEcosystem.ts` (~L25) and
+`src/pages/products/index.astro` (~L87) → `TBMQ_URLS.product`, one line each.
+Neither card component supports `target`/`rel`, so they would open in the same tab
+— acceptable for a body card, and not worth threading that plumbing through two
+more components.
+
+## Error handling
+
+External links carry `rel="noopener noreferrer"` alongside `target="_blank"`,
+matching the convention already used throughout `installations.ts` and
+`Banner.astro`.
+
+If `TBMQ_SITE_URL` is set to a value with a trailing slash, `normalizeOrigin`
+strips it; the helpers never emit `//` between origin and path.
+
+Nothing in this pass can 404: every tbmq.io target it uses was verified present in
+the `../tbmq.io` build output (`dist/product/`, `dist/docs/`).
+
+## Verification
+
+- `pnpm check` — Astro/TypeScript
+- `pnpm lint:eslint`
+- `pnpm lint:slugcheck`
+- `pnpm lint:linkcheck` — confirms no internal link broke; tbmq.io URLs are
+  skipped as external
+- Manual: Products menu, Docs menu, docs left-panel product selector and
+  `/installations/?product=mqtt-broker` each open the correct tbmq.io page in a new
+  tab; TBMQ docs pages and `/pricing/` behave exactly as before
+
+Ask before running any build, per the project build policy in `CLAUDE.md`.
+
+## Out of scope
+
+- Deleting TBMQ docs, marketing pages, pricing data or assets
+- The cross-site edge redirects and their 31-entry chain prune (§ D)
+- The pricing page and the two ecosystem cards (§ F)
+- Rewriting links *within* the TBMQ docs tree or in blog posts (§ C)
+- The `/mqtt/*` MQTT glossary pages — they exist only on tbmq.io, not here
+- `demo.tbmq.io` links, which are already external and correct
diff --git a/docs/tbmq-migration/removal-inventory.md b/docs/tbmq-migration/removal-inventory.md
new file mode 100644
index 0000000000..6a237d6d70
--- /dev/null
+++ b/docs/tbmq-migration/removal-inventory.md
@@ -0,0 +1,246 @@
+# TBMQ removal inventory
+
+TBMQ moved to tbmq.io. The first pass (see
+`docs/superpowers/specs/2026-07-27-tbmq-io-link-migration-design.md`) repointed four
+entry points: the Products menu, the Docs menu, the docs left-panel product
+selector, and the Try it now TBMQ panel.
+
+The second pass **landed the edge cutover** — every `/docs/mqtt-broker/*` and
+`/products/mqtt-broker/` request now 301s to tbmq.io, so inbound Google results and
+links from other sites resolve without a per-link source edit. Deployment order is
+tbmq.io first, then thingsboard.io, so nothing lands on a missing page.
+
+Counts measured 2026-07-27 on branch `tbmq-migration`.
+
+## Status
+
+| | What | State | Where in this document |
+|---|---|---|---|
+| A | The `/docs/mqtt-broker/*` cutover redirect | **done** | § Redirects |
+| B | Pricing page TBMQ toggle | awaiting go-ahead | § Pricing |
+| C | Homepage + `/products/` ecosystem cards | awaiting go-ahead | § Marketing ecosystem cards |
+| D | Delete the TBMQ docs, marketing pages, blog posts and assets | awaiting go-ahead | § Docs content, § Marketing, § Blog |
+
+With A in place, **D is unblocked** — the redirects already cover every URL the
+deletion would remove. **B and C are independent** of both and can ship at any time.
+
+## Order of operations for the remaining sweep (D)
+
+1. ~~Add the redirects~~ — done, see § Redirects.
+2. Delete content (§ Docs content, § Marketing, § Blog).
+3. Remove the plumbing (§ Sidebar, § Product plumbing) — this is what makes
+   `pnpm check` fail if a reference was missed.
+4. Delete the data files (§ Pricing, § Try it now).
+5. `pnpm generate:redirects`, then `pnpm check && pnpm lint:eslint && pnpm lint:slugcheck && pnpm lint:redirects && pnpm lint:linkcheck`.
+
+**Live gap until D lands:** the TBMQ pages are still built and still in the sitemap,
+so crawlers are pointed at URLs that now 301 cross-domain. Either accept it for the
+gap, or give those pages a cross-site `<link rel="canonical">` — the sitemap
+integration only includes self-canonical pages, so a cross-site canonical drops them
+automatically.
+
+## Docs content
+
+- `src/content/docs/docs/mqtt-broker/**` — 84 CE stubs
+- `src/content/docs/docs/mqtt-broker/pe/**` — 90 PE stubs
+- `src/content/_includes/docs/mqtt-broker/**` — 88 shared include files
+
+219 files under `src/content/` reference `docs/mqtt-broker`; the splat redirects
+cover every link, so none of them needs a content edit before deletion.
+
+## Sidebar — `astro.sidebar.ts`
+
+- `tbmqSidebar` (L3803) and `tbmqPeSidebar` (L3855)
+- helpers `tbmqGuideItems` (L3568), `tbmqInstallItems` (L3683), `tbmqReferenceItems` (L3735)
+- `tbmqSidebarTabLinks` (L4339), `tbmqPeSidebarTabLinks` (L4346)
+- registrations: L4390, L4391 (tab-link map) and L4414, L4415 (sidebar spread)
+
+## Product plumbing
+
+- `src/models/site.models.ts` — `Products.TBMQ` (L14), `Products.TBMQ_PE` (L15) and their `productDocsPrefix` entries (L32–33)
+- `src/util/path-utils.ts` — `productVersions` entries (L42, L47) plus the `mqtt-broker/` prefix branches (L115–116, L144–145, L202–203)
+- `src/routeData.ts` — the TBMQ / TBMQ_PE path branches (L202–203)
+- `src/util/ogContext.ts` — `'mqtt-broker/pe/'` and `'mqtt-broker/'` in `MARKETING_ALLOWLIST` (L23)
+- `src/components/DocLink.astro` — the `TBMQ` / `TBMQ_PE` entries in the `tbBase` map (L21–22)
+- `src/content/_includes/docs/user-guide/integrations/mqtt.mdx` — two `<DocLink product={Products.TBMQ|TBMQ_PE}>` links (`installation/live-demo/`, `security/mqtts`). Unlike plain-href content links (covered by the splats, no edit needed), DocLink resolves the product at build time — dropping the enum entries breaks the build, so re-point these two at `tbmqDocsUrl(…)` in the same change
+- `src/components/VersionSwitcher.astro` — the `Products.TBMQ` family (drop the whole entry; `externalUrl` alone is no longer enough once local editions are gone)
+- `scripts/lint-linkcheck.ts` — the `/docs/mqtt-broker/` → `/docs/mqtt-broker/pe/` `consolidationPatterns` entry (L111)
+
+## Marketing
+
+- `src/pages/products/mqtt-broker/index.astro`, `privacy-policy.astro`, `terms-of-use.astro`
+- `src/pages/open-graph/_shared/marketing-meta.ts` — 3 entries (L34–36: `/products/mqtt-broker/`, `…/privacy-policy/`, `…/terms-of-use/`)
+- `src/data/tbmqNews.ts`
+- `src/assets/images/landings/mqtt-broker/` — 37 files, ~2.0 MB
+
+## Blog
+
+All 8 TBMQ posts are already published on tbmq.io, so they are deleted here and
+redirected there:
+
+- `1-million-reasons-to-choose-tbmq-as-high-performance-mqtt-broker.mdx`
+- `introducing-tbmq-professional-edition-the-mqtt-broker-for-enterprise-needs.mdx`
+- `new-thingsboard-tbmq-pricing-modular-add-ons-top-ups-and-total-cost-clarity.mdx`
+- `tbmq-1-3-0-release-websocket-client-advanced-mqtt-5-features-and-more.mdx`
+- `tbmq-2-0-migration-to-redis-mqtt-5-0-support-and-more.mdx`
+- `tbmq-2-1-new-chapter-in-mqtt-messaging-with-embedded-integrations.mdx`
+- `tbmq-2-2-strengthening-mqtt-security-with-jwt-and-client-blocking.mdx`
+- `tbmq-2-3-external-authentication-bulk-provisioning-and-enterprise-audit-trails.mdx`
+
+## Pricing — item B, fully live, no decision made
+
+Nothing here has been touched. `/pricing/` still renders its TBMQ tab, its three
+sub-tabs (`tbmq-ce`, `tbmq-pe`, `tbmq-private-cloud`), all three calculators and
+the TBMQ FAQ set, and every `?section=tbmq-options` deep link still resolves
+locally.
+
+Files in play when the decision comes:
+
+- `src/pages/pricing/index.astro` — the `data-product-content="tbmq"` block (L336), `tbmqSubTabs` (L157), the three data imports (L32–34), the `'tbmq-options'` entry in `sectionMap` inside the pre-paint `is:inline` resolver (L432), and the `updateUrl()` branch that writes the param back (L1306–1307)
+- `src/components/Pricing/ProductTabs.astro` — the `tbmq` tab entry (L7) and the `tbmq-icon.svg` import (L3)
+- `src/data/pricing/tbmq-ce.ts`, `tbmq-self-managed.ts`, `tbmq-private-cloud.ts`
+- `src/data/pricing/faq/tbmq-ce.ts`, `tbmq-self-managed-payg.ts`, `tbmq-self-managed-perp.ts`, `tbmq-private-cloud.ts` (and their registration in `src/data/pricing/faq/index.ts`, L7–10 and L23–26)
+- `src/components/Pricing/TbmqPaygCalculator.astro`, `TbmqPerpetualCalculator.astro`, `TbmqPrivateCloudCalculator.astro`
+- `src/scripts/pricing/calc-tbmq-payg.ts`, `calc-tbmq-pc.ts`, `calc-tbmq-perp.ts`
+- `src/assets/pricing/tbmq-icon.svg`
+- 16 local `/docs/mqtt-broker/…` links inside the pricing data files — `tbmq-ce.ts` (1), `faq/tbmq-ce.ts` (7), `faq/tbmq-self-managed-payg.ts` (3), `faq/tbmq-self-managed-perp.ts` (4), `faq/tbmq-private-cloud.ts` (1)
+
+**Two things to know before deciding.**
+
+First, **every inbound `?section=tbmq-options` link in this repo lives in TBMQ-owned
+content that items A and D would remove anyway.** All 20 occurrences sit in 14
+files: 10 in TBMQ docs `_includes` (which would 301 away under item A), 6 across 3
+TBMQ blog posts, and 4 in `src/pages/products/mqtt-broker/index.astro` (both
+deleted and redirected under item D). Nothing on a surviving page links to the
+TBMQ pricing tab. So once A and D land, the in-repo half of this question answers
+itself and no link edits are needed.
+
+Second, that leaves only *external* inbound traffic — bookmarks, search results,
+links from tbmq.io — and `?section=tbmq-options` **cannot be redirected at the
+edge**: Cloudflare Pages `_redirects` does not match query strings. Whenever the
+local TBMQ pricing content goes, those remaining hits need an in-page bounce
+instead: read the param in the existing pre-paint `is:inline` resolver in
+`pricing/index.astro` (L416) and `location.replace()` to tbmq.io, with the URL
+injected via `define:vars={{ tbmqPricingUrl: … }}` — the pattern already used by
+`Tabs.astro`, `DemoRequestForm.astro` and `IotHubRuntimeConfig.astro`. Pre-paint
+placement is what keeps the ThingsBoard tab from flashing first.
+
+## Marketing ecosystem cards — item C, fully live
+
+Two cards still point at the local `/products/mqtt-broker/` page:
+
+- `src/data/homeEcosystem.ts` (L25) — the homepage ecosystem card
+- `src/pages/products/index.astro` (L87) — the products-ecosystem card
+
+Both are one-line changes to `TBMQ_URLS.product`. Neither card component supports
+`target`/`rel`, so these would open in the same tab — acceptable for a body card,
+and not worth threading the plumbing through two more components.
+
+## Try it now
+
+Only the panel's **three CTA buttons** were repointed at tbmq.io in the first pass.
+**16 links in this block are still local** and still resolve on thingsboard.io: the
+two in the `description` string (`/products/mqtt-broker/`, `/docs/mqtt-broker/`),
+the six feature links, and the eight deploy-card links. They were deliberately left
+alone until TBMQ docs actually come down — repointing them is part of item A/D, not
+a separate decision.
+
+- the `mqtt-broker` product block in `src/data/installations.ts` (L609–756) and the
+  `mqttBroker()` image-path helper it uses (L56)
+- `productTabs` (L759) needs no entry removed — it is derived from `products` — but
+  its label ternary ends in `: 'TBMQ'` (L772) as the catch-all branch, so that
+  fallback has to be re-pointed at whichever product should own it
+- the TBMQ hero images it references under `src/assets/images/landings/mqtt-broker/`
+
+## Redirects — item A, landed
+
+tbmq.io mirrors the docs tree slug-for-slug, but **without the `mqtt-broker/`
+product segment** — that site is TBMQ-only, so `/docs/mqtt-broker/<slug>` here is
+`/docs/<slug>` there. The cutover is therefore pure prefix substitution.
+
+All of the below is in `src/data/redirects.ts` and regenerated into
+`public/_redirects` + `public/redirects.json`. The origin and docs root are not
+spelled here — `redirects.ts` imports `TBMQ_DOCS_BASE`, `TBMQ_URLS` and
+`tbmqDocsUrl` from `src/data/external-sites.ts`, so a tbmq.io restructure is still
+a one-file edit.
+
+### The cutover splats
+
+Five entries in the `TBMQ_CUTOVER` group of `DYNAMIC_REDIRECTS`. Cloudflare takes
+the **first match**, so the `install/` → `installation/` Jekyll renames precede the
+generic splats:
+
+```
+/docs/mqtt-broker/pe/install/*  → https://tbmq.io/docs/pe/installation/:splat 301
+/docs/pe/mqtt-broker/install/*  → https://tbmq.io/docs/pe/installation/:splat 301
+/docs/mqtt-broker/install/*     → https://tbmq.io/docs/installation/:splat 301
+/docs/pe/mqtt-broker/*          → https://tbmq.io/docs/pe/:splat 301
+/docs/mqtt-broker/*             → https://tbmq.io/docs/:splat 301
+```
+
+The generic `/docs/mqtt-broker/*` rule covers PE too: `/docs/mqtt-broker/pe/x`
+loses the segment and lands on `/docs/pe/x`, which is already correct. The separate
+`/docs/pe/mqtt-broker/*` rule exists only for the legacy Jekyll ordering.
+
+Dynamic-rule budget: **47 of Cloudflare's 100** (was 46; the five new rules replaced
+four emitted by the deleted catch-all groups).
+
+They **must** stay in `DYNAMIC_REDIRECTS`, not `NON_DOCS_REDIRECTS`:
+`astro.redirects.ts` feeds `NON_DOCS_REDIRECTS` to Astro's `redirects:` config,
+where a splat over `/docs/mqtt-broker/*` collides with the real content routes.
+Keeping them out of the Astro config also means `pnpm dev`, `pnpm preview` and
+`pnpm lint:linkcheck` still see the real TBMQ pages — the link checker stays
+green and the docs remain browsable locally.
+
+### The chain prune — done by rewriting, not deleting
+
+`redirects.ts` held **27 `SINGLE_REDIRECTS` targeting `/docs/mqtt-broker/`** plus
+**4 `CATCH_ALL_REDIRECTS` groups** (`mqtt-broker/install`, `mqtt-broker/pe/install`,
+`pe/mqtt-broker/install`, `pe/mqtt-broker`). Left alone, every one would have become
+a chain once the splats landed — `pnpm lint:redirects` fails and visitors pay two
+round-trips.
+
+Rather than deleting them and relying on tbmq.io to re-resolve the legacy shape on
+their side, **the 27 singles were rewritten to their final tbmq.io URL** via
+`tbmqDocsUrl(...)`:
+
+```
+/docs/mqtt-broker/api/  → https://tbmq.io/docs/rest-api/  (was → /docs/mqtt-broker/rest-api/)
+/docs/mqtt-broker/faq/  → https://tbmq.io/docs/why-tbmq/
+```
+
+That resolves in **one hop to the right page** and depends on nothing in tbmq.io's
+own redirect table — which is what the earlier draft of this document assumed, and
+could not verify.
+
+The 4 catch-all groups were **deleted** and replaced by the three `install/` splats
+above, because `CatchAllRedirect` can only express a local `newPrefix` — it cannot
+target another origin.
+
+`pnpm lint:redirects` reports no chains across 1040 SINGLE + 52 NON_DOCS targets.
+
+### Marketing
+
+In `NON_DOCS_REDIRECTS`:
+
+```
+/products/mqtt-broker/ → https://tbmq.io/ 301
+```
+
+`/products/mqtt-broker/privacy-policy/` and `…/terms-of-use/` are **deliberately not
+covered** — no splat here, so they keep serving locally until tbmq.io's equivalents
+are confirmed.
+
+### Still to add — blog
+
+The 8 TBMQ blog posts (§ Blog) are **not redirected yet**. The rule shape is
+`/blog/<slug>/ → https://tbmq.io/blog/<slug>/ 301`, but unlike the docs tree this is
+not a mechanical prefix rule — each target slug has to be confirmed to exist on
+tbmq.io first, or we trade 8 local pages for 8 cross-domain 404s.
+
+### Dev-mode leftovers
+
+`devFallbackRedirects` in `astro.redirects.ts` still has one mqtt-broker entry —
+`'/docs/pe/mqtt-broker/search/': '/docs/mqtt-broker/pe/search/'` (L24). It is dev-only
+(never emitted to `_redirects`) and still useful while the local docs exist; remove
+it with item D.
diff --git a/public/_redirects b/public/_redirects
index 21192c24a3..173d49a85d 100644
--- a/public/_redirects
+++ b/public/_redirects
@@ -12,12 +12,6 @@
 /docs/paas/eu/solution-templates/fleet-tracking/ /iot-hub/solution-templates/fleet-tracking/ 301
 /docs/iot-gateway/install/rpi/ /docs/iot-gateway/installation/deb-installation/ 301
 /docs/iot-gateway/install/windows/ /docs/iot-gateway/installation/docker-windows/ 301
-/docs/mqtt-broker/install/cluster/helm-cluster-setup-options/ /docs/mqtt-broker/installation/ 301
-/docs/mqtt-broker/install/installation-options/ /docs/mqtt-broker/installation/ 301
-/docs/mqtt-broker/install/cluster/helm-cluster-upgrading-options/ /docs/mqtt-broker/installation/upgrade-instructions/ 301
-/docs/mqtt-broker/install/cluster/resources/upgrade-options/docker-compose-upgrade-tbmq-with-from-version/ /docs/mqtt-broker/installation/upgrade-instructions/ 301
-/docs/mqtt-broker/install/cluster/resources/upgrade-options/docker-compose-upgrade-tbmq-without-from-version/ /docs/mqtt-broker/installation/upgrade-instructions/ 301
-/docs/mqtt-broker/install/cluster/resources/upgrade-options/k8s-upgrade-tbmq-with-from-version/ /docs/mqtt-broker/installation/upgrade-instructions/ 301
 /docs/trendz/install/trndz-upgrade-instructions-kubernetes/ /docs/trendz/installation/upgrade-instructions/ 301
 /docs/trendz/install/trndz-upgrade-instructions/ /docs/trendz/installation/upgrade-instructions/ 301
 /docs/trendz/install/installation-options/ /docs/trendz/installation/ 301
@@ -66,17 +60,6 @@
 /docs/pe/edge/rule-engine/queues/ /docs/edge/pe/user-guide/queues/ 301
 /docs/pe/edge/features/cloud-events/ /docs/edge/pe/user-guide/telemetry-synchronization/ 301
 /docs/pe/edge/features/edge-status/ /docs/edge/pe/user-guide/edge-status-events/ 301
-/docs/pe/mqtt-broker/install/cluster/helm-cluster-setup-options/ /docs/mqtt-broker/pe/installation/ 301
-/docs/pe/mqtt-broker/install/installation-options/ /docs/mqtt-broker/pe/installation/ 301
-/docs/pe/mqtt-broker/install/cluster/helm-cluster-upgrading-options/ /docs/mqtt-broker/pe/installation/upgrade-instructions/ 301
-/docs/pe/mqtt-broker/install/cluster/resources/upgrade-options/docker-compose-upgrade-tbmq-with-from-version/ /docs/mqtt-broker/pe/installation/upgrade-instructions/ 301
-/docs/pe/mqtt-broker/install/cluster/resources/upgrade-options/docker-compose-upgrade-tbmq-without-from-version/ /docs/mqtt-broker/pe/installation/upgrade-instructions/ 301
-/docs/pe/mqtt-broker/install/cluster/resources/upgrade-options/k8s-upgrade-tbmq-with-from-version/ /docs/mqtt-broker/pe/installation/upgrade-instructions/ 301
-/docs/pe/mqtt-broker/api/ /docs/mqtt-broker/pe/rest-api/ 301
-/docs/pe/mqtt-broker/faq/ /docs/mqtt-broker/pe/why-tbmq/ 301
-/docs/pe/mqtt-broker/getting-started-guides/what-is-thingsboard-mqtt-broker/ /docs/mqtt-broker/pe/why-tbmq/ 301
-/docs/pe/mqtt-broker/troubleshooting/ /docs/mqtt-broker/pe/help/ 301
-/docs/pe/mqtt-broker/user-guide/ui/mail-server/ /docs/mqtt-broker/pe/user-guide/ui/settings/ 301
 /docs/user-guide/install/upgrade-instructions/old-upgrade-instructions/ /docs/installation/upgrade-instructions/ 301
 /docs/pe/user-guide/install/upgrade-instructions/old-upgrade-instructions/ /docs/pe/installation/upgrade-instructions/ 301
 /docs/pe/user-guide/install/upgrade-instructions/upgrade-from-ce/ /docs/pe/installation/upgrade-from-ce/ 301
@@ -903,14 +886,6 @@
 /docs/paas/eu/samples/analytics/ollama/ /docs/paas/eu/user-guide/local-ai-ollama/ 301
 /docs/samples/analytics/ollama/nginx/ /docs/user-guide/local-ai-ollama/ 301
 /docs/samples/analytics/spark-integration-with-thingsboard/ /docs/user-guide/ai-models/ 301
-/docs/mqtt-broker/api/ /docs/mqtt-broker/rest-api/ 301
-/docs/mqtt-broker/faq/ /docs/mqtt-broker/why-tbmq/ 301
-/docs/mqtt-broker/getting-started-guides/what-is-thingsboard-mqtt-broker/ /docs/mqtt-broker/why-tbmq/ 301
-/docs/mqtt-broker/image-gallery/ /docs/mqtt-broker/pe/image-gallery/ 301
-/docs/mqtt-broker/subscription/ /docs/mqtt-broker/pe/subscription/ 301
-/docs/mqtt-broker/troubleshooting/ /docs/mqtt-broker/help/ 301
-/docs/mqtt-broker/user-guide/ui/mail-server/ /docs/mqtt-broker/user-guide/ui/settings/ 301
-/docs/mqtt-broker/white-labeling/ /docs/mqtt-broker/pe/white-labeling/ 301
 /docs/services/ /services/ 301
 /docs/services/consulting/ /services/development-services/ 301
 /docs/services/customers-full-reviews/ /services/development-services/ 301
@@ -1034,7 +1009,6 @@
 /docs/user-guide/install/ /docs/installation/ 301
 /docs/user-guide/install/openbsd/ /docs/installation/ 301
 /docs/user-guide/install-and-use/install/ /docs/installation/ 301
-/docs/mqtt-broker/security/ /docs/mqtt-broker/security/overview/ 301
 /docs/reference/apis/ /docs/apis-and-sdks/ 301
 /docs/reference/device-connectivity-api/ /docs/apis-and-sdks/ 301
 /docs/reference/edge/ /docs/edge/ 301
@@ -1048,6 +1022,7 @@
 # Non-docs redirects (from NON_DOCS_REDIRECTS)
 /community/ / 301
 /services/support/ /services/ 301
+/products/mqtt-broker/ https://tbmq.io/ 301
 /products/trendz/trndz-request-demo/ /products/trendz/request-demo/ 301
 /images/trendz/trndz-request-demo/ /products/trendz/request-demo/ 301
 /products/paas/billing-info/ /docs/paas/user-guide/billing-info/ 301
@@ -1118,6 +1093,8 @@
 /docs/user-guide/install/pe/edge/upgrade-instructions/:platform/:version/ /docs/edge/pe/installation/upgrade-instructions/:platform/ 301
 /docs/gw/* /docs/iot-gateway/:splat 301
 /docs/license/* /docs/license-server/:splat 301
+/docs/pe/mqtt-broker/* https://tbmq.io/docs/pe/mqtt-broker/:splat 301
+/docs/mqtt-broker/* https://tbmq.io/docs/mqtt-broker/:splat 301
 /docs/user-guide/releases-table/* /docs/releases/releases-table/:splat 301
 /docs/pe/user-guide/releases-table/* /docs/pe/releases/releases-table/:splat 301
 /device-library/ce/* /iot-hub/devices/:splat 301
@@ -1141,14 +1118,10 @@
 /docs/paas/solution-templates/* /docs/paas/recipes/solution-templates/:splat 301
 /docs/paas/eu/solution-templates/* /docs/paas/eu/recipes/solution-templates/:splat 301
 /docs/iot-gateway/install/* /docs/iot-gateway/installation/:splat 301
-/docs/mqtt-broker/install/* /docs/mqtt-broker/installation/:splat 301
-/docs/mqtt-broker/pe/install/* /docs/mqtt-broker/pe/installation/:splat 301
 /docs/trendz/install/* /docs/trendz/installation/:splat 301
 /docs/trendz/guide/* /docs/trendz/user-guide/:splat 301
 /docs/pe/edge/* /docs/edge/pe/:splat 301
 /docs/pe/mobile/* /docs/mobile/pe/:splat 301
-/docs/pe/mqtt-broker/install/* /docs/mqtt-broker/pe/installation/:splat 301
-/docs/pe/mqtt-broker/* /docs/mqtt-broker/pe/:splat 301
 /docs/user-guide/install/upgrade-instructions/* /docs/installation/upgrade-instructions/:splat 301
 /docs/user-guide/install/pe/upgrade-instructions/* /docs/pe/installation/upgrade-instructions/:splat 301
 /docs/pe/user-guide/install/upgrade-instructions/* /docs/pe/installation/upgrade-instructions/:splat 301
diff --git a/public/redirects.json b/public/redirects.json
index 8c08db43bf..90762c81e1 100644
--- a/public/redirects.json
+++ b/public/redirects.json
@@ -1104,32 +1104,6 @@
   "/docs/paas/eu/samples/analytics/ollama/": "/docs/paas/eu/user-guide/local-ai-ollama/",
   "/docs/samples/analytics/ollama/nginx/": "/docs/user-guide/local-ai-ollama/",
   "/docs/samples/analytics/spark-integration-with-thingsboard/": "/docs/user-guide/ai-models/",
-  "/docs/mqtt-broker/api/": "/docs/mqtt-broker/rest-api/",
-  "/docs/mqtt-broker/faq/": "/docs/mqtt-broker/why-tbmq/",
-  "/docs/mqtt-broker/getting-started-guides/what-is-thingsboard-mqtt-broker/": "/docs/mqtt-broker/why-tbmq/",
-  "/docs/mqtt-broker/image-gallery/": "/docs/mqtt-broker/pe/image-gallery/",
-  "/docs/mqtt-broker/install/cluster/helm-cluster-setup-options/": "/docs/mqtt-broker/installation/",
-  "/docs/mqtt-broker/install/installation-options/": "/docs/mqtt-broker/installation/",
-  "/docs/mqtt-broker/install/cluster/helm-cluster-upgrading-options/": "/docs/mqtt-broker/installation/upgrade-instructions/",
-  "/docs/mqtt-broker/install/cluster/resources/upgrade-options/docker-compose-upgrade-tbmq-with-from-version/": "/docs/mqtt-broker/installation/upgrade-instructions/",
-  "/docs/mqtt-broker/install/cluster/resources/upgrade-options/docker-compose-upgrade-tbmq-without-from-version/": "/docs/mqtt-broker/installation/upgrade-instructions/",
-  "/docs/mqtt-broker/install/cluster/resources/upgrade-options/k8s-upgrade-tbmq-with-from-version/": "/docs/mqtt-broker/installation/upgrade-instructions/",
-  "/docs/mqtt-broker/subscription/": "/docs/mqtt-broker/pe/subscription/",
-  "/docs/mqtt-broker/troubleshooting/": "/docs/mqtt-broker/help/",
-  "/docs/mqtt-broker/user-guide/ui/mail-server/": "/docs/mqtt-broker/user-guide/ui/settings/",
-  "/docs/mqtt-broker/white-labeling/": "/docs/mqtt-broker/pe/white-labeling/",
-  "/docs/pe/mqtt-broker/api/": "/docs/mqtt-broker/pe/rest-api/",
-  "/docs/pe/mqtt-broker/faq/": "/docs/mqtt-broker/pe/why-tbmq/",
-  "/docs/pe/mqtt-broker/getting-started-guides/what-is-thingsboard-mqtt-broker/": "/docs/mqtt-broker/pe/why-tbmq/",
-  "/docs/pe/mqtt-broker/image-gallery/": "/docs/mqtt-broker/pe/image-gallery/",
-  "/docs/pe/mqtt-broker/install/cluster/helm-cluster-setup-options/": "/docs/mqtt-broker/pe/installation/",
-  "/docs/pe/mqtt-broker/install/installation-options/": "/docs/mqtt-broker/pe/installation/",
-  "/docs/pe/mqtt-broker/install/cluster/helm-cluster-upgrading-options/": "/docs/mqtt-broker/pe/installation/upgrade-instructions/",
-  "/docs/pe/mqtt-broker/install/cluster/resources/upgrade-options/docker-compose-upgrade-tbmq-with-from-version/": "/docs/mqtt-broker/pe/installation/upgrade-instructions/",
-  "/docs/pe/mqtt-broker/install/cluster/resources/upgrade-options/docker-compose-upgrade-tbmq-without-from-version/": "/docs/mqtt-broker/pe/installation/upgrade-instructions/",
-  "/docs/pe/mqtt-broker/install/cluster/resources/upgrade-options/k8s-upgrade-tbmq-with-from-version/": "/docs/mqtt-broker/pe/installation/upgrade-instructions/",
-  "/docs/pe/mqtt-broker/troubleshooting/": "/docs/mqtt-broker/pe/help/",
-  "/docs/pe/mqtt-broker/user-guide/ui/mail-server/": "/docs/mqtt-broker/pe/user-guide/ui/settings/",
   "/docs/services/": "/services/",
   "/docs/services/consulting/": "/services/development-services/",
   "/docs/services/customers-full-reviews/": "/services/development-services/",
@@ -1256,7 +1230,6 @@
   "/docs/user-guide/install/": "/docs/installation/",
   "/docs/user-guide/install/openbsd/": "/docs/installation/",
   "/docs/user-guide/install-and-use/install/": "/docs/installation/",
-  "/docs/mqtt-broker/security/": "/docs/mqtt-broker/security/overview/",
   "/docs/reference/apis/": "/docs/apis-and-sdks/",
   "/docs/reference/device-connectivity-api/": "/docs/apis-and-sdks/",
   "/docs/reference/edge/": "/docs/edge/",
@@ -1660,41 +1633,6 @@
   "/docs/iot-gateway/install/rpm-installation/": "/docs/iot-gateway/installation/rpm-installation/",
   "/docs/iot-gateway/install/source-installation/": "/docs/iot-gateway/installation/source-installation/",
   "/docs/iot-gateway/install/upgrade-instructions/": "/docs/iot-gateway/installation/upgrade-instructions/",
-  "/docs/mqtt-broker/install/building-from-source/": "/docs/mqtt-broker/installation/building-from-source/",
-  "/docs/mqtt-broker/install/cluster/aws-cluster-setup/": "/docs/mqtt-broker/installation/cluster/aws-cluster-setup/",
-  "/docs/mqtt-broker/install/cluster/azure-cluster-setup/": "/docs/mqtt-broker/installation/cluster/azure-cluster-setup/",
-  "/docs/mqtt-broker/install/cluster/docker-compose-setup/": "/docs/mqtt-broker/installation/cluster/docker-compose-setup/",
-  "/docs/mqtt-broker/install/cluster/gcp-cluster-setup/": "/docs/mqtt-broker/installation/cluster/gcp-cluster-setup/",
-  "/docs/mqtt-broker/install/cluster/helm-cluster-setup-aws/": "/docs/mqtt-broker/installation/cluster/helm-cluster-setup-aws/",
-  "/docs/mqtt-broker/install/cluster/helm-cluster-setup-azure/": "/docs/mqtt-broker/installation/cluster/helm-cluster-setup-azure/",
-  "/docs/mqtt-broker/install/cluster/helm-cluster-setup-gcp/": "/docs/mqtt-broker/installation/cluster/helm-cluster-setup-gcp/",
-  "/docs/mqtt-broker/install/cluster/helm-cluster-setup-minikube/": "/docs/mqtt-broker/installation/cluster/helm-cluster-setup-minikube/",
-  "/docs/mqtt-broker/install/cluster/minikube-cluster-setup/": "/docs/mqtt-broker/installation/cluster/minikube-cluster-setup/",
-  "/docs/mqtt-broker/install/config/": "/docs/mqtt-broker/installation/config/",
-  "/docs/mqtt-broker/install/docker-windows/": "/docs/mqtt-broker/installation/docker-windows/",
-  "/docs/mqtt-broker/install/docker/": "/docs/mqtt-broker/installation/docker/",
-  "/docs/mqtt-broker/install/how-to-change-config/": "/docs/mqtt-broker/installation/how-to-change-config/",
-  "/docs/mqtt-broker/install/ie-config/": "/docs/mqtt-broker/installation/ie-config/",
-  "/docs/mqtt-broker/install/": "/docs/mqtt-broker/installation/",
-  "/docs/mqtt-broker/install/live-demo/": "/docs/mqtt-broker/installation/live-demo/",
-  "/docs/mqtt-broker/install/upgrade-instructions/": "/docs/mqtt-broker/installation/upgrade-instructions/",
-  "/docs/mqtt-broker/pe/install/cluster/aws-cluster-setup/": "/docs/mqtt-broker/pe/installation/cluster/aws-cluster-setup/",
-  "/docs/mqtt-broker/pe/install/cluster/azure-cluster-setup/": "/docs/mqtt-broker/pe/installation/cluster/azure-cluster-setup/",
-  "/docs/mqtt-broker/pe/install/cluster/docker-compose-setup/": "/docs/mqtt-broker/pe/installation/cluster/docker-compose-setup/",
-  "/docs/mqtt-broker/pe/install/cluster/gcp-cluster-setup/": "/docs/mqtt-broker/pe/installation/cluster/gcp-cluster-setup/",
-  "/docs/mqtt-broker/pe/install/cluster/helm-cluster-setup-aws/": "/docs/mqtt-broker/pe/installation/cluster/helm-cluster-setup-aws/",
-  "/docs/mqtt-broker/pe/install/cluster/helm-cluster-setup-azure/": "/docs/mqtt-broker/pe/installation/cluster/helm-cluster-setup-azure/",
-  "/docs/mqtt-broker/pe/install/cluster/helm-cluster-setup-gcp/": "/docs/mqtt-broker/pe/installation/cluster/helm-cluster-setup-gcp/",
-  "/docs/mqtt-broker/pe/install/cluster/helm-cluster-setup-minikube/": "/docs/mqtt-broker/pe/installation/cluster/helm-cluster-setup-minikube/",
-  "/docs/mqtt-broker/pe/install/cluster/minikube-cluster-setup/": "/docs/mqtt-broker/pe/installation/cluster/minikube-cluster-setup/",
-  "/docs/mqtt-broker/pe/install/config/": "/docs/mqtt-broker/pe/installation/config/",
-  "/docs/mqtt-broker/pe/install/docker-windows/": "/docs/mqtt-broker/pe/installation/docker-windows/",
-  "/docs/mqtt-broker/pe/install/docker/": "/docs/mqtt-broker/pe/installation/docker/",
-  "/docs/mqtt-broker/pe/install/how-to-change-config/": "/docs/mqtt-broker/pe/installation/how-to-change-config/",
-  "/docs/mqtt-broker/pe/install/ie-config/": "/docs/mqtt-broker/pe/installation/ie-config/",
-  "/docs/mqtt-broker/pe/install/": "/docs/mqtt-broker/pe/installation/",
-  "/docs/mqtt-broker/pe/install/live-demo/": "/docs/mqtt-broker/pe/installation/live-demo/",
-  "/docs/mqtt-broker/pe/install/upgrade-instructions/": "/docs/mqtt-broker/pe/installation/upgrade-instructions/",
   "/docs/trendz/install/cloud/": "/docs/trendz/installation/cloud/",
   "/docs/trendz/install/docker-compose-setup/": "/docs/trendz/installation/docker-compose-setup/",
   "/docs/trendz/install/docker-windows/": "/docs/trendz/installation/docker-windows/",
@@ -1991,111 +1929,5 @@
   "/docs/pe/mobile/releases/": "/docs/mobile/pe/releases/",
   "/docs/pe/mobile/search/": "/docs/mobile/pe/search/",
   "/docs/pe/mobile/self-registration/": "/docs/mobile/pe/self-registration/",
-  "/docs/pe/mobile/white-labeling/": "/docs/mobile/pe/white-labeling/",
-  "/docs/pe/mqtt-broker/install/cluster/aws-cluster-setup/": "/docs/mqtt-broker/pe/installation/cluster/aws-cluster-setup/",
-  "/docs/pe/mqtt-broker/install/cluster/azure-cluster-setup/": "/docs/mqtt-broker/pe/installation/cluster/azure-cluster-setup/",
-  "/docs/pe/mqtt-broker/install/cluster/docker-compose-setup/": "/docs/mqtt-broker/pe/installation/cluster/docker-compose-setup/",
-  "/docs/pe/mqtt-broker/install/cluster/gcp-cluster-setup/": "/docs/mqtt-broker/pe/installation/cluster/gcp-cluster-setup/",
-  "/docs/pe/mqtt-broker/install/cluster/helm-cluster-setup-aws/": "/docs/mqtt-broker/pe/installation/cluster/helm-cluster-setup-aws/",
-  "/docs/pe/mqtt-broker/install/cluster/helm-cluster-setup-azure/": "/docs/mqtt-broker/pe/installation/cluster/helm-cluster-setup-azure/",
-  "/docs/pe/mqtt-broker/install/cluster/helm-cluster-setup-gcp/": "/docs/mqtt-broker/pe/installation/cluster/helm-cluster-setup-gcp/",
-  "/docs/pe/mqtt-broker/install/cluster/helm-cluster-setup-minikube/": "/docs/mqtt-broker/pe/installation/cluster/helm-cluster-setup-minikube/",
-  "/docs/pe/mqtt-broker/install/cluster/minikube-cluster-setup/": "/docs/mqtt-broker/pe/installation/cluster/minikube-cluster-setup/",
-  "/docs/pe/mqtt-broker/install/config/": "/docs/mqtt-broker/pe/installation/config/",
-  "/docs/pe/mqtt-broker/install/docker-windows/": "/docs/mqtt-broker/pe/installation/docker-windows/",
-  "/docs/pe/mqtt-broker/install/docker/": "/docs/mqtt-broker/pe/installation/docker/",
-  "/docs/pe/mqtt-broker/install/how-to-change-config/": "/docs/mqtt-broker/pe/installation/how-to-change-config/",
-  "/docs/pe/mqtt-broker/install/ie-config/": "/docs/mqtt-broker/pe/installation/ie-config/",
-  "/docs/pe/mqtt-broker/install/": "/docs/mqtt-broker/pe/installation/",
-  "/docs/pe/mqtt-broker/install/live-demo/": "/docs/mqtt-broker/pe/installation/live-demo/",
-  "/docs/pe/mqtt-broker/install/upgrade-instructions/": "/docs/mqtt-broker/pe/installation/upgrade-instructions/",
-  "/docs/pe/mqtt-broker/application-shared-subscription/": "/docs/mqtt-broker/pe/application-shared-subscription/",
-  "/docs/pe/mqtt-broker/architecture-details/persistent-app-client/": "/docs/mqtt-broker/pe/architecture-details/persistent-app-client/",
-  "/docs/pe/mqtt-broker/architecture-details/persistent-device-client/": "/docs/mqtt-broker/pe/architecture-details/persistent-device-client/",
-  "/docs/pe/mqtt-broker/architecture/": "/docs/mqtt-broker/pe/architecture/",
-  "/docs/pe/mqtt-broker/changelog/": "/docs/mqtt-broker/pe/changelog/",
-  "/docs/pe/mqtt-broker/concepts/client-types/": "/docs/mqtt-broker/pe/concepts/client-types/",
-  "/docs/pe/mqtt-broker/concepts/clustering/": "/docs/mqtt-broker/pe/concepts/clustering/",
-  "/docs/pe/mqtt-broker/concepts/qos/": "/docs/mqtt-broker/pe/concepts/qos/",
-  "/docs/pe/mqtt-broker/concepts/security/": "/docs/mqtt-broker/pe/concepts/security/",
-  "/docs/pe/mqtt-broker/concepts/sessions/": "/docs/mqtt-broker/pe/concepts/sessions/",
-  "/docs/pe/mqtt-broker/concepts/topics/": "/docs/mqtt-broker/pe/concepts/topics/",
-  "/docs/pe/mqtt-broker/getting-started/": "/docs/mqtt-broker/pe/getting-started/",
-  "/docs/pe/mqtt-broker/help/": "/docs/mqtt-broker/pe/help/",
-  "/docs/pe/mqtt-broker/": "/docs/mqtt-broker/pe/",
-  "/docs/pe/mqtt-broker/installation/cluster/aws-cluster-setup/": "/docs/mqtt-broker/pe/installation/cluster/aws-cluster-setup/",
-  "/docs/pe/mqtt-broker/installation/cluster/azure-cluster-setup/": "/docs/mqtt-broker/pe/installation/cluster/azure-cluster-setup/",
-  "/docs/pe/mqtt-broker/installation/cluster/docker-compose-setup/": "/docs/mqtt-broker/pe/installation/cluster/docker-compose-setup/",
-  "/docs/pe/mqtt-broker/installation/cluster/gcp-cluster-setup/": "/docs/mqtt-broker/pe/installation/cluster/gcp-cluster-setup/",
-  "/docs/pe/mqtt-broker/installation/cluster/helm-cluster-setup-aws/": "/docs/mqtt-broker/pe/installation/cluster/helm-cluster-setup-aws/",
-  "/docs/pe/mqtt-broker/installation/cluster/helm-cluster-setup-azure/": "/docs/mqtt-broker/pe/installation/cluster/helm-cluster-setup-azure/",
-  "/docs/pe/mqtt-broker/installation/cluster/helm-cluster-setup-gcp/": "/docs/mqtt-broker/pe/installation/cluster/helm-cluster-setup-gcp/",
-  "/docs/pe/mqtt-broker/installation/cluster/helm-cluster-setup-minikube/": "/docs/mqtt-broker/pe/installation/cluster/helm-cluster-setup-minikube/",
-  "/docs/pe/mqtt-broker/installation/cluster/minikube-cluster-setup/": "/docs/mqtt-broker/pe/installation/cluster/minikube-cluster-setup/",
-  "/docs/pe/mqtt-broker/installation/config/": "/docs/mqtt-broker/pe/installation/config/",
-  "/docs/pe/mqtt-broker/installation/docker-windows/": "/docs/mqtt-broker/pe/installation/docker-windows/",
-  "/docs/pe/mqtt-broker/installation/docker/": "/docs/mqtt-broker/pe/installation/docker/",
-  "/docs/pe/mqtt-broker/installation/how-to-change-config/": "/docs/mqtt-broker/pe/installation/how-to-change-config/",
-  "/docs/pe/mqtt-broker/installation/ie-config/": "/docs/mqtt-broker/pe/installation/ie-config/",
-  "/docs/pe/mqtt-broker/installation/": "/docs/mqtt-broker/pe/installation/",
-  "/docs/pe/mqtt-broker/installation/live-demo/": "/docs/mqtt-broker/pe/installation/live-demo/",
-  "/docs/pe/mqtt-broker/installation/upgrade-instructions/": "/docs/mqtt-broker/pe/installation/upgrade-instructions/",
-  "/docs/pe/mqtt-broker/integrations/http/": "/docs/mqtt-broker/pe/integrations/http/",
-  "/docs/pe/mqtt-broker/integrations/kafka/": "/docs/mqtt-broker/pe/integrations/kafka/",
-  "/docs/pe/mqtt-broker/integrations/mqtt/": "/docs/mqtt-broker/pe/integrations/mqtt/",
-  "/docs/pe/mqtt-broker/integrations/": "/docs/mqtt-broker/pe/integrations/",
-  "/docs/pe/mqtt-broker/mqtt-client-credentials-management/": "/docs/mqtt-broker/pe/mqtt-client-credentials-management/",
-  "/docs/pe/mqtt-broker/other/blocked-client/": "/docs/mqtt-broker/pe/other/blocked-client/",
-  "/docs/pe/mqtt-broker/other/bulk-provisioning/": "/docs/mqtt-broker/pe/other/bulk-provisioning/",
-  "/docs/pe/mqtt-broker/other/health/": "/docs/mqtt-broker/pe/other/health/",
-  "/docs/pe/mqtt-broker/other/msg-delivery-strategy/": "/docs/mqtt-broker/pe/other/msg-delivery-strategy/",
-  "/docs/pe/mqtt-broker/other/proxy-protocol/": "/docs/mqtt-broker/pe/other/proxy-protocol/",
-  "/docs/pe/mqtt-broker/reference/100m-connections-performance-test/": "/docs/mqtt-broker/pe/reference/100m-connections-performance-test/",
-  "/docs/pe/mqtt-broker/reference/1m-throughput-p2p-performance-test/": "/docs/mqtt-broker/pe/reference/1m-throughput-p2p-performance-test/",
-  "/docs/pe/mqtt-broker/reference/3m-throughput-single-node-performance-test/": "/docs/mqtt-broker/pe/reference/3m-throughput-single-node-performance-test/",
-  "/docs/pe/mqtt-broker/reference/": "/docs/mqtt-broker/pe/reference/",
-  "/docs/pe/mqtt-broker/releases/": "/docs/mqtt-broker/pe/releases/",
-  "/docs/pe/mqtt-broker/rest-api/": "/docs/mqtt-broker/pe/rest-api/",
-  "/docs/pe/mqtt-broker/roadmap/": "/docs/mqtt-broker/pe/roadmap/",
-  "/docs/pe/mqtt-broker/search/": "/docs/mqtt-broker/pe/search/",
-  "/docs/pe/mqtt-broker/security/audit-log/": "/docs/mqtt-broker/pe/security/audit-log/",
-  "/docs/pe/mqtt-broker/security/authentication/basic/": "/docs/mqtt-broker/pe/security/authentication/basic/",
-  "/docs/pe/mqtt-broker/security/authentication/http/": "/docs/mqtt-broker/pe/security/authentication/http/",
-  "/docs/pe/mqtt-broker/security/authentication/jwt/": "/docs/mqtt-broker/pe/security/authentication/jwt/",
-  "/docs/pe/mqtt-broker/security/authentication/scram/": "/docs/mqtt-broker/pe/security/authentication/scram/",
-  "/docs/pe/mqtt-broker/security/authentication/x509/": "/docs/mqtt-broker/pe/security/authentication/x509/",
-  "/docs/pe/mqtt-broker/security/domains/": "/docs/mqtt-broker/pe/security/domains/",
-  "/docs/pe/mqtt-broker/security/https/": "/docs/mqtt-broker/pe/security/https/",
-  "/docs/pe/mqtt-broker/security/listeners/": "/docs/mqtt-broker/pe/security/listeners/",
-  "/docs/pe/mqtt-broker/security/mqtts/": "/docs/mqtt-broker/pe/security/mqtts/",
-  "/docs/pe/mqtt-broker/security/oauth-2-support/": "/docs/mqtt-broker/pe/security/oauth-2-support/",
-  "/docs/pe/mqtt-broker/security/overview/": "/docs/mqtt-broker/pe/security/overview/",
-  "/docs/pe/mqtt-broker/security/rbac/": "/docs/mqtt-broker/pe/security/rbac/",
-  "/docs/pe/mqtt-broker/subscription/": "/docs/mqtt-broker/pe/subscription/",
-  "/docs/pe/mqtt-broker/user-guide/backpressure/": "/docs/mqtt-broker/pe/user-guide/backpressure/",
-  "/docs/pe/mqtt-broker/user-guide/clean-persistent-sessions/": "/docs/mqtt-broker/pe/user-guide/clean-persistent-sessions/",
-  "/docs/pe/mqtt-broker/user-guide/integrations/how-to-connect-thingsboard-to-tbmq/": "/docs/mqtt-broker/pe/user-guide/integrations/how-to-connect-thingsboard-to-tbmq/",
-  "/docs/pe/mqtt-broker/user-guide/keep-alive/": "/docs/mqtt-broker/pe/user-guide/keep-alive/",
-  "/docs/pe/mqtt-broker/user-guide/last-will/": "/docs/mqtt-broker/pe/user-guide/last-will/",
-  "/docs/pe/mqtt-broker/user-guide/mqtt-broker/": "/docs/mqtt-broker/pe/user-guide/mqtt-broker/",
-  "/docs/pe/mqtt-broker/user-guide/mqtt-client-type/": "/docs/mqtt-broker/pe/user-guide/mqtt-client-type/",
-  "/docs/pe/mqtt-broker/user-guide/mqtt-over-ws/": "/docs/mqtt-broker/pe/user-guide/mqtt-over-ws/",
-  "/docs/pe/mqtt-broker/user-guide/mqtt-protocol/": "/docs/mqtt-broker/pe/user-guide/mqtt-protocol/",
-  "/docs/pe/mqtt-broker/user-guide/qos/": "/docs/mqtt-broker/pe/user-guide/qos/",
-  "/docs/pe/mqtt-broker/user-guide/retained-messages/": "/docs/mqtt-broker/pe/user-guide/retained-messages/",
-  "/docs/pe/mqtt-broker/user-guide/shared-subscriptions/": "/docs/mqtt-broker/pe/user-guide/shared-subscriptions/",
-  "/docs/pe/mqtt-broker/user-guide/topics/": "/docs/mqtt-broker/pe/user-guide/topics/",
-  "/docs/pe/mqtt-broker/user-guide/ui/monitoring/": "/docs/mqtt-broker/pe/user-guide/ui/monitoring/",
-  "/docs/pe/mqtt-broker/user-guide/ui/mqtt-client-credentials/": "/docs/mqtt-broker/pe/user-guide/ui/mqtt-client-credentials/",
-  "/docs/pe/mqtt-broker/user-guide/ui/sessions/": "/docs/mqtt-broker/pe/user-guide/ui/sessions/",
-  "/docs/pe/mqtt-broker/user-guide/ui/settings/": "/docs/mqtt-broker/pe/user-guide/ui/settings/",
-  "/docs/pe/mqtt-broker/user-guide/ui/shared-subscriptions/": "/docs/mqtt-broker/pe/user-guide/ui/shared-subscriptions/",
-  "/docs/pe/mqtt-broker/user-guide/ui/subscriptions/": "/docs/mqtt-broker/pe/user-guide/ui/subscriptions/",
-  "/docs/pe/mqtt-broker/user-guide/ui/unauthorized-clients/": "/docs/mqtt-broker/pe/user-guide/ui/unauthorized-clients/",
-  "/docs/pe/mqtt-broker/user-guide/ui/users/": "/docs/mqtt-broker/pe/user-guide/ui/users/",
-  "/docs/pe/mqtt-broker/user-guide/ui/websocket-client/": "/docs/mqtt-broker/pe/user-guide/ui/websocket-client/",
-  "/docs/pe/mqtt-broker/user-guide/": "/docs/mqtt-broker/pe/user-guide/",
-  "/docs/pe/mqtt-broker/user-management/": "/docs/mqtt-broker/pe/user-management/",
-  "/docs/pe/mqtt-broker/white-labeling/": "/docs/mqtt-broker/pe/white-labeling/",
-  "/docs/pe/mqtt-broker/why-tbmq/": "/docs/mqtt-broker/pe/why-tbmq/"
+  "/docs/pe/mobile/white-labeling/": "/docs/mobile/pe/white-labeling/"
 }
diff --git a/src/components/Landing/SubMenuLink.astro b/src/components/Landing/SubMenuLink.astro
index ec40515496..6ca5a562c9 100644
--- a/src/components/Landing/SubMenuLink.astro
+++ b/src/components/Landing/SubMenuLink.astro
@@ -11,7 +11,12 @@ interface Props {
 const { item, iconSize = 24 } = Astro.props;
 ---
 
-<a class={item.linkClass} href={item.href}>
+<a
+	class={item.linkClass}
+	href={item.href}
+	target={item.external ? '_blank' : undefined}
+	rel={item.external ? 'noopener noreferrer' : undefined}
+>
 	{item.icon && <NavIcon src={item.icon} size={iconSize} alt={`${item.heading} icon`} />}
 	<div class="sub-text">
 		<span class="item-heading">{item.heading}</span>
diff --git a/src/components/VersionSwitcher.astro b/src/components/VersionSwitcher.astro
index a7afc6b4fd..e264086f68 100644
--- a/src/components/VersionSwitcher.astro
+++ b/src/components/VersionSwitcher.astro
@@ -1,5 +1,6 @@
 ---
 import { Products } from '@models/site.models.ts';
+import { TBMQ_URLS } from '@data/external-sites';
 import { allPages } from '~/content';
 import { getVersionFromURL, switchVersionWithFallback } from '~/util/path-utils';
 import { RELEASE_FAMILIES, familySlug } from '~/models/releases-table';
@@ -41,6 +42,10 @@ interface Family {
 	/** Edition to land on when this family is picked from the product dropdown.
 	 * Defaults to `editions[editions.length - 1]` (Professional/Cloud first). */
 	preferredEdition?: Products;
+	/** When set, picking this family from the dropdown leaves thingsboard.io.
+	 * `editions` still drives which pages belong to the family, so local docs
+	 * for it keep resolving while they exist. */
+	externalUrl?: string;
 }
 
 const FAMILIES: Family[] = [
@@ -102,6 +107,7 @@ const FAMILIES: Family[] = [
 			{ product: Products.TBMQ_PE, label: 'Professional' },
 		],
 		preferredEdition: Products.TBMQ_PE,
+		externalUrl: TBMQ_URLS.docs,
 	},
 	{
 		id: Products.MOBILE,
@@ -253,7 +259,9 @@ const activeRegion = currentFamily.regions?.options.find((r) => r.product === cu
 						<a
 							role="option"
 							class:list={['ps-item', { 'is-active': f.id === currentFamily.id }]}
-							href={href(preferredOf(f))}
+							href={f.externalUrl ?? href(preferredOf(f))}
+							target={f.externalUrl ? '_blank' : undefined}
+							rel={f.externalUrl ? 'noopener noreferrer' : undefined}
 							aria-selected={f.id === currentFamily.id}
 						>
 							<span class:list={['ps-icon-box', { 'ps-icon-box--active': f.id === currentFamily.id }]}>
diff --git a/src/content/_includes/docs/user-guide/integrations/mqtt.mdx b/src/content/_includes/docs/user-guide/integrations/mqtt.mdx
index ebbc99ca14..38cf42ad01 100644
--- a/src/content/_includes/docs/user-guide/integrations/mqtt.mdx
+++ b/src/content/_includes/docs/user-guide/integrations/mqtt.mdx
@@ -986,51 +986,39 @@ The encoder receives `msg`, `metadata`, and `msgType`, and must return:
 For RPC commands, `msg.method` and `msg.params` are available. `msg.params` is always a string — use `parseFloat(msg.params)` or `JSON.parse(msg.params)` when a numeric or structured value is needed. See the <DocLink product={props.product} path="user-guide/integrations/downlink-data-converter" target="_blank">Downlink data converter</DocLink> reference for the full encoder API.
 
 <Steps>
-  1. Go to **Integrations center &#8702; Integrations** and open the MQTT Integration.
+  1. Go to **Integrations center &#8702; Integrations** and open the **MQTT integration**.
   2. Click the **pencil** icon to enter edit mode.
   3. In the **Downlink data converter** field, click **Create new**.
-  4. Enter a name (e.g. `MQTT Downlink Converter`) and paste the encoder script.
-  5. Click **Add**, then click **Apply changes**.
+  4. In the **Add data converter** dialog:
+      - Enter a name for the converter, for example, `MQTT Downlink Converter`.
+      - Use the default encoder script or replace it with your own implementation.
+      - Click **Add**.
+  5. Click **Apply changes** to save the integration.
 </Steps>
 
 **The encoder function used in this tutorial:**
 
-<Tabs>
-<TabItem label="TBEL (Recommended)">
-```js maxLines=15 collapsible
+```js
 /** Encoder **/
 // Publish the ThingsBoard message as JSON to the device command topic.
 // metadata.topic is read by the integration when Downlink topic pattern is ${topic}.
 
 var result = {
+  // Specify the downlink payload format: JSON, TEXT, or BINARY.
   contentType: "JSON",
-  data: JSON.stringify(msg),
-  metadata: {
-    topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
-  }
-};
-
-return result;
-```
-</TabItem>
-<TabItem label="JavaScript">
-```js maxLines=15 collapsible
-/** Encoder **/
-// Publish the ThingsBoard message as JSON to the device command topic.
-// metadata.topic is read by the integration when Downlink topic pattern is ${topic}.
 
-var result = {
-  contentType: "JSON",
+  // Serialize the incoming message and use it as the MQTT payload.
   data: JSON.stringify(msg),
+
+  // Build the MQTT topic from the device type and device name.
+  // The integration uses this value when the Downlink topic pattern is ${topic}.
   metadata: {
-    topic: metadata['deviceType']+'/'+metadata['deviceName']+'/upload'
+    topic: metadata['deviceType'] + '/' + metadata['deviceName'] + '/upload'
   }
 };
 
 return result;
 ```
-</TabItem>
-</Tabs>
 
 ### Configure the Root Rule Chain
 
diff --git a/src/data/external-sites.ts b/src/data/external-sites.ts
new file mode 100644
index 0000000000..fdcfa3a543
--- /dev/null
+++ b/src/data/external-sites.ts
@@ -0,0 +1,70 @@
+/**
+ * Sibling-site origins and URL builders.
+ *
+ * TBMQ moved to its own site (tbmq.io). Every thingsboard.io link that used to
+ * point at a local TBMQ page resolves through the helpers here, so the origin
+ * and the path shape live in exactly one place — when tbmq.io restructures,
+ * this file is the only edit.
+ *
+ * `TBMQ_SITE_URL` mirrors the `IOT_HUB_API_URL` pattern in `src/models/iot-hub.ts`:
+ * build-time `import.meta.env` with a literal fallback, no `PUBLIC_` prefix,
+ * because every URL produced here is baked into HTML at build time.
+ */
+
+const normalizeOrigin = (origin: string): string => origin.replace(/\/+$/, '');
+
+// `import.meta.env` only exists under Vite. The redirects generator
+// (`pnpm generate:redirects`) and Astro's config loader pull this file in under
+// plain Node, where the guard short-circuits to the literal fallback.
+const envSiteUrl = import.meta.env ? import.meta.env.TBMQ_SITE_URL : undefined;
+
+export const TBMQ_ORIGIN = normalizeOrigin(envSiteUrl ?? 'https://tbmq.io');
+
+/**
+ * tbmq.io is a TBMQ-only site, so its docs tree carries no `mqtt-broker/`
+ * segment: thingsboard.io's `/docs/mqtt-broker/<slug>` is `/docs/<slug>` there,
+ * a 1:1 mapping by prefix substitution.
+ */
+const TBMQ_DOCS_ROOT = '/docs/';
+
+/**
+ * Absolute docs root with trailing slash (`https://tbmq.io/docs/`). For redirect
+ * splat templates (`` `${TBMQ_DOCS_BASE}pe/:splat` ``), where `tbmqDocsUrl` can't
+ * be used — it would append a trailing slash after `:splat`.
+ */
+export const TBMQ_DOCS_BASE = `${TBMQ_ORIGIN}${TBMQ_DOCS_ROOT}`;
+
+/** Absolute tbmq.io URL for `path`. Leading and trailing slashes are normalized. */
+export function tbmqUrl(path = '/'): string {
+	const trimmed = path.replace(/^\/+/, '');
+	const withSlash = trimmed === '' || trimmed.endsWith('/') ? trimmed : `${trimmed}/`;
+	return `${TBMQ_ORIGIN}/${withSlash}`;
+}
+
+/**
+ * Absolute tbmq.io docs URL for a slug relative to the TBMQ docs root.
+ *   tbmqDocsUrl('installation/')    → https://tbmq.io/docs/installation/
+ *   tbmqDocsUrl('pe/installation/') → https://tbmq.io/docs/pe/installation/
+ *
+ * Query strings survive: a slug ending in `?installationType=helm` is not given
+ * a trailing slash.
+ */
+export function tbmqDocsUrl(slug = ''): string {
+	const trimmed = slug.replace(/^\/+/, '');
+	if (trimmed === '') return tbmqUrl(TBMQ_DOCS_ROOT);
+	const [pathPart, query] = trimmed.split('?');
+	const path = pathPart!.endsWith('/') ? pathPart : `${pathPart}/`;
+	return `${TBMQ_ORIGIN}${TBMQ_DOCS_ROOT}${path}${query ? `?${query}` : ''}`;
+}
+
+/**
+ * Named tbmq.io entry points. Prefer these over spelling a path at a call site.
+ * Add a key when a surface needs it — `/pricing/` and `/installations/` are
+ * deliberately absent until the pricing migration is approved.
+ */
+export const TBMQ_URLS = {
+	// The site root is the product landing — tbmq.io has no separate /product/ page.
+	product: tbmqUrl('/'),
+	docs: tbmqUrl('/docs/'),
+	liveDemo: 'https://demo.tbmq.io/signup',
+} as const;
diff --git a/src/data/homeEcosystem.ts b/src/data/homeEcosystem.ts
index 532ad52399..a8dcce232b 100644
--- a/src/data/homeEcosystem.ts
+++ b/src/data/homeEcosystem.ts
@@ -1,3 +1,5 @@
+import { TBMQ_URLS } from '@data/external-sites';
+
 export interface EcosystemItem {
 	name: string;
 	description: string;
@@ -22,7 +24,7 @@ export const homeEcosystem: EcosystemItem[] = [
 		name: 'MQTT Broker',
 		description: 'Connect MQTT clients',
 		icon: '/src/assets/images/landings/ce/tbmq-icon.svg',
-		href: '/products/mqtt-broker/',
+		href: TBMQ_URLS.product,
 	},
 	{
 		name: 'Trendz Analytics',
diff --git a/src/data/installations.ts b/src/data/installations.ts
index 760db36213..0ff70df521 100644
--- a/src/data/installations.ts
+++ b/src/data/installations.ts
@@ -1,3 +1,5 @@
+import { TBMQ_URLS, tbmqDocsUrl } from '@data/external-sites';
+
 export interface HeroButton {
 	id: string;
 	label: string;
@@ -611,26 +613,25 @@ export const products: ProductData[] = [
 	{
 		id: 'mqtt-broker',
 		title: 'MQTT Broker',
-		description:
-			'<b>TBMQ</b> is a highly scalable and durable <a href="/products/mqtt-broker/" target="_blank" rel="noopener noreferrer">MQTT message broker</a> built for real-time data processing across IoT ecosystems of any scale. It efficiently handles millions of concurrent client connections and processes millions of messages per second while maintaining low latency and reliable delivery. Designed for horizontal scalability, TBMQ seamlessly expands across cluster nodes to support massive deployments with millions of connected devices. <a href="/docs/mqtt-broker/" target="_blank" rel="noopener noreferrer">Read more<span class="sr-only"> about TBMQ MQTT Broker</span></a>.',
+		description: `<b>TBMQ</b> is a highly scalable and durable <a href="${TBMQ_URLS.product}" target="_blank" rel="noopener noreferrer">MQTT message broker</a> built for real-time data processing across IoT ecosystems of any scale. It efficiently handles millions of concurrent client connections and processes millions of messages per second while maintaining low latency and reliable delivery. Designed for horizontal scalability, TBMQ seamlessly expands across cluster nodes to support massive deployments with millions of connected devices. <a href="${TBMQ_URLS.docs}" target="_blank" rel="noopener noreferrer">Read more<span class="sr-only"> about TBMQ MQTT Broker</span></a>.`,
 		buttons: [
 			{
 				id: 'TryItNow_TBMQ_Demo',
 				label: 'Live Demo',
-				href: 'https://demo.tbmq.io/signup',
+				href: TBMQ_URLS.liveDemo,
 				target: '_blank',
 			},
 			{
 				id: 'TryItNow_TBMQ_Install_CE',
 				label: 'Download CE',
-				href: '/docs/mqtt-broker/installation/',
+				href: tbmqDocsUrl('installation/'),
 				target: '_blank',
 				secondary: true,
 			},
 			{
 				id: 'TryItNow_TBMQ_Install_PE',
 				label: 'Start PE Trial',
-				href: '/docs/mqtt-broker/pe/installation/',
+				href: tbmqDocsUrl('pe/installation/'),
 				target: '_blank',
 				secondary: true,
 			},
@@ -651,20 +652,20 @@ export const products: ProductData[] = [
 			[
 				{
 					title: 'Unlimited Horizontal Scaling',
-					href: '/docs/mqtt-broker/reference/100m-connections-performance-test/',
+					href: tbmqDocsUrl('reference/100m-connections-performance-test/'),
 					target: '_blank',
 					description: 'Scale horizontally to manage more than 100M MQTT connections on a single cluster',
 				},
 				{
 					title: 'Million-Message Throughput',
-					href: '/docs/mqtt-broker/reference/3m-throughput-single-node-performance-test/',
+					href: tbmqDocsUrl('reference/3m-throughput-single-node-performance-test/'),
 					target: '_blank',
 					description:
 						'Process millions of messages per second with 1 TBMQ server and single-digit latency',
 				},
 				{
 					title: 'Masterless High Availability',
-					href: '/docs/mqtt-broker/architecture/',
+					href: tbmqDocsUrl('architecture/'),
 					target: '_blank',
 					description: 'Prevent single point of failure with masterless nodes in the cluster',
 				},
@@ -672,20 +673,20 @@ export const products: ProductData[] = [
 			[
 				{
 					title: 'Universal MQTT Support',
-					href: '/docs/mqtt-broker/getting-started/',
+					href: tbmqDocsUrl('getting-started/'),
 					target: '_blank',
 					description: 'MQTT 3.x and 5.0 compatible for a seamless and secure connection experience',
 				},
 				{
 					title: 'Zero Data Loss Guarantee',
-					href: '/docs/mqtt-broker/architecture/',
+					href: tbmqDocsUrl('architecture/'),
 					target: '_blank',
 					description:
 						'Guarantee the persistence and replication of your data to ensure it\'s never lost',
 				},
 				{
 					title: 'K8s & Cloud Agnostic',
-					href: '/docs/mqtt-broker/installation/',
+					href: tbmqDocsUrl('installation/'),
 					target: '_blank',
 					description: 'Deploy in cloud or on-premises using K8s scripts with ease',
 				},
@@ -699,28 +700,28 @@ export const products: ProductData[] = [
 						logo: install('docker-linux-mac.svg'),
 						logoAlt: 'Docker (Linux or Mac OS)',
 						title: 'Docker (Linux or Mac OS)',
-						href: '/docs/mqtt-broker/installation/docker/',
+						href: tbmqDocsUrl('installation/docker/'),
 						target: '_blank',
 					},
 					{
 						logo: install('docker-windows.svg'),
 						logoAlt: 'Docker (Windows)',
 						title: 'Docker (Windows)',
-						href: '/docs/mqtt-broker/installation/docker-windows/',
+						href: tbmqDocsUrl('installation/docker-windows/'),
 						target: '_blank',
 					},
 					{
 						logo: install('docker-compose.svg'),
 						logoAlt: 'Cluster setup with Docker Compose',
 						title: 'Cluster with Docker Compose',
-						href: '/docs/mqtt-broker/installation/cluster/docker-compose-setup/',
+						href: tbmqDocsUrl('installation/cluster/docker-compose-setup/'),
 						target: '_blank',
 					},
 					{
 						logo: install('minikube.svg'),
 						logoAlt: 'Cluster setup with Minikube',
 						title: 'Cluster setup with Minikube',
-						href: '/docs/mqtt-broker/installation/cluster/minikube-cluster-setup/',
+						href: tbmqDocsUrl('installation/cluster/minikube-cluster-setup/'),
 						target: '_blank',
 					},
 				],
@@ -732,28 +733,28 @@ export const products: ProductData[] = [
 						logo: install('eks.svg'),
 						logoAlt: 'Cluster setup on EKS',
 						title: 'Cluster setup on EKS',
-						href: '/docs/mqtt-broker/installation/cluster/aws-cluster-setup/',
+						href: tbmqDocsUrl('installation/cluster/aws-cluster-setup/'),
 						target: '_blank',
 					},
 					{
 						logo: install('azure.svg'),
 						logoAlt: 'Cluster setup on AKS',
 						title: 'Cluster setup on AKS',
-						href: '/docs/mqtt-broker/installation/cluster/azure-cluster-setup/',
+						href: tbmqDocsUrl('installation/cluster/azure-cluster-setup/'),
 						target: '_blank',
 					},
 					{
 						logo: install('gcp.svg'),
 						logoAlt: 'Cluster setup on GCP',
 						title: 'Cluster setup on GCP',
-						href: '/docs/mqtt-broker/installation/cluster/gcp-cluster-setup/',
+						href: tbmqDocsUrl('installation/cluster/gcp-cluster-setup/'),
 						target: '_blank',
 					},
 					{
 						logo: install('helm.svg'),
 						logoAlt: 'Cluster setup using Helm',
 						title: 'Cluster setup using Helm',
-						href: '/docs/mqtt-broker/installation/?installationType=helm',
+						href: tbmqDocsUrl('installation/?installationType=helm'),
 						target: '_blank',
 					},
 				],
diff --git a/src/data/navigation.ts b/src/data/navigation.ts
index ee7767ac2f..a2864dc67a 100644
--- a/src/data/navigation.ts
+++ b/src/data/navigation.ts
@@ -1,3 +1,5 @@
+import { TBMQ_URLS } from '@data/external-sites';
+
 export interface NavItem {
 	label: string;
 	href?: string;
@@ -11,6 +13,8 @@ export interface SubMenuItem {
 	heading: string;
 	description?: string;
 	linkClass?: string;
+	/** Opens in a new tab. Set for links that leave thingsboard.io. */
+	external?: boolean;
 }
 
 export interface SubMenuGroup {
@@ -98,11 +102,12 @@ export const productsSubmenu: SubMenu = {
 					linkClass: 'mobile-pe-lnk',
 				},
 				{
-					href: '/products/mqtt-broker/',
+					href: TBMQ_URLS.product,
 					icon: '/src/assets/images/landings/nav/tbmq-icon.svg',
 					heading: 'TBMQ',
 					description: 'Scalable MQTT broker',
 					linkClass: 'mqtt-broker-lnk',
+					external: true,
 				},
 				{
 					href: '/products/trendz/',
@@ -403,10 +408,11 @@ export const docsSubmenu: SubMenu = {
 					linkClass: 'mobile-pe-lnk',
 				},
 				{
-					href: '/docs/mqtt-broker/',
+					href: TBMQ_URLS.docs,
 					heading: 'TBMQ',
 					description: 'Scalable MQTT broker',
 					linkClass: 'mqtt-broker-lnk',
+					external: true,
 				},
 				{
 					href: '/docs/trendz/',
diff --git a/src/data/pricing/faq/tbmq-ce.ts b/src/data/pricing/faq/tbmq-ce.ts
index d96dea9e31..eba46daadb 100644
--- a/src/data/pricing/faq/tbmq-ce.ts
+++ b/src/data/pricing/faq/tbmq-ce.ts
@@ -38,7 +38,7 @@ export const tbmqCeFaq: FaqCategory[] = [
 			{
 				id: 'tbmq-ce-migration-pe',
 				question: 'Is it possible to migrate from the Community Edition to the self-managed TBMQ Professional Edition?',
-				answer: '<p>Yes, you can upgrade from TBMQ Community Edition to Professional Edition without losing any data and/or configurations. The upgrade process preserves your existing setup, ensuring a seamless transition. However, please note that any custom modifications made directly to the source code of the Community Edition will be removed during the upgrade process. For more information about the migration procedure, please <a target="_blank" href="/contact-us/" rel="noopener noreferrer">contact us</a>.</p>',
+				answer: '<p>Yes, you can upgrade from TBMQ Community Edition to Professional Edition without losing any data and/or configurations. The upgrade process preserves your existing setup, ensuring a seamless transition. However, please note that any custom modifications made directly to the source code of the Community Edition will be removed during the upgrade process. For more information about the migration procedure, please <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">contact us</a>.</p>',
 			},
 			{
 				id: 'tbmq-ce-clustering',
@@ -136,7 +136,7 @@ export const tbmqCeFaq: FaqCategory[] = [
 			{
 				id: 'tbmq-ce-paid-support',
 				question: 'Can I purchase additional support for the Community Edition?',
-				answer: '<p>Depending on the type of support you are looking for, the TBMQ team may be able to offer certain types of additional support packages. To discuss your unique case and requirements, please <a target="_blank" href="/contact-us/" rel="noopener noreferrer">contact us</a>.</p>',
+				answer: '<p>Depending on the type of support you are looking for, the TBMQ team may be able to offer certain types of additional support packages. To discuss your unique case and requirements, please <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">contact us</a>.</p>',
 			},
 			{
 				id: 'tbmq-ce-help',
@@ -151,7 +151,7 @@ export const tbmqCeFaq: FaqCategory[] = [
 			{
 				id: 'tbmq-ce-dev-services',
 				question: 'Can I pay for additional features to be developed?',
-				answer: '<p>The TBMQ team can propose application configuration services. To discuss your unique case and requirements, please <a target="_blank" href="/contact-us/" rel="noopener noreferrer">contact us</a>.</p>',
+				answer: '<p>The TBMQ team can propose application configuration services. To discuss your unique case and requirements, please <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">contact us</a>.</p>',
 			},
 			{
 				id: 'tbmq-ce-updates',
@@ -161,7 +161,7 @@ export const tbmqCeFaq: FaqCategory[] = [
 			{
 				id: 'tbmq-ce-dev-assist',
 				question: 'Can I get TBMQ developers to help with my Community Edition deployment?',
-				answer: '<p>Yes, you can request such assistance as an additional paid service. Please, <a target="_blank" href="/contact-us/" rel="noopener noreferrer">contact us</a> to discuss how we can help.</p>',
+				answer: '<p>Yes, you can request such assistance as an additional paid service. Please, <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">contact us</a> to discuss how we can help.</p>',
 			},
 			{
 				id: 'tbmq-ce-bug-report',
@@ -192,7 +192,7 @@ export const tbmqCeFaq: FaqCategory[] = [
 			{
 				id: 'tbmq-ce-migration-strategy',
 				question: 'How do I migrate from Community Edition to Enterprise?',
-				answer: '<p>Migration depends on factors such as the version, source code changes, and more. Please <a target="_blank" href="/contact-us/" rel="noopener noreferrer">contact us</a> for personalized suggestions and a clear strategy on how to perform the migration.</p>',
+				answer: '<p>Migration depends on factors such as the version, source code changes, and more. Please <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">contact us</a> for personalized suggestions and a clear strategy on how to perform the migration.</p>',
 			},
 			{
 				id: 'tbmq-ce-pe-trial',
diff --git a/src/data/pricing/faq/tbmq-self-managed-payg.ts b/src/data/pricing/faq/tbmq-self-managed-payg.ts
index ea8973c656..9f5133c0f7 100644
--- a/src/data/pricing/faq/tbmq-self-managed-payg.ts
+++ b/src/data/pricing/faq/tbmq-self-managed-payg.ts
@@ -97,12 +97,12 @@ export const tbmqSelfManagedPaygFaq: FaqCategory[] = [
 			{
 				id: 'tbmq-payg-wire',
 				question: 'I cannot pay by card, may we use wire instead?',
-				answer: `<p>Sure. In this case, you must reach out to our sales team via <a target="_blank" href="/contact-us/" rel="noopener noreferrer">contact us</a>. If you have ongoing communication with the account manager or success manager on our end, please refer your request to that person.</p>`,
+				answer: `<p>Sure. In this case, you must reach out to our sales team via <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">contact us</a>. If you have ongoing communication with the account manager or success manager on our end, please refer your request to that person.</p>`,
 			},
 			{
 				id: 'tbmq-payg-annual',
 				question: 'Do you offer an annual payment option?',
-				answer: `<p>We currently offer only a monthly subscription with automatic payments via Stripe. For annual payments, please <a target="_blank" href="/contact-us/" rel="noopener noreferrer">contact</a> our team to arrange a wire transfer invoice.</p>`,
+				answer: `<p>We currently offer only a monthly subscription with automatic payments via Stripe. For annual payments, please <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">contact</a> our team to arrange a wire transfer invoice.</p>`,
 			},
 			{
 				id: 'tbmq-payg-failed-payment',
@@ -127,7 +127,7 @@ export const tbmqSelfManagedPaygFaq: FaqCategory[] = [
 			{
 				id: 'tbmq-payg-discounts',
 				question: 'Do you offer discounts for multiple licenses?',
-				answer: `<p>Contact our <a target="_blank" href="/contact-us/" rel="noopener noreferrer">sales team</a> for bulk pricing options.</p>`,
+				answer: `<p>Contact our <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">sales team</a> for bulk pricing options.</p>`,
 			},
 			{
 				id: 'tbmq-payg-renew-fail',
@@ -230,7 +230,7 @@ export const tbmqSelfManagedPaygFaq: FaqCategory[] = [
 			{
 				id: 'tbmq-payg-offline',
 				question: 'Can I run offline?',
-				answer: `<p>By default, the platform requires active Internet access or at least access to license portal from your host machine. If Offline access is a must, please <a target="_blank" href="/contact-us/" rel="noopener noreferrer">contact us</a> to discuss options.</p>`,
+				answer: `<p>By default, the platform requires active Internet access or at least access to license portal from your host machine. If Offline access is a must, please <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">contact us</a> to discuss options.</p>`,
 			},
 			{
 				id: 'tbmq-payg-cloud-agnostic',
@@ -319,12 +319,12 @@ export const tbmqSelfManagedPaygFaq: FaqCategory[] = [
 			{
 				id: 'tbmq-payg-support-247',
 				question: 'Do you offer 24/7 support?',
-				answer: `<p>Yes, we can provide 24/7 support as part of our managed services with an additional signed SLA. Please <a target="_blank" href="/contact-us/" rel="noopener noreferrer">contact us</a> for more details.</p>`,
+				answer: `<p>Yes, we can provide 24/7 support as part of our managed services with an additional signed SLA. Please <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">contact us</a> for more details.</p>`,
 			},
 			{
 				id: 'tbmq-payg-install-help',
 				question: 'How can I get help with installation and setup?',
-				answer: `<p>If your subscription includes response time support and you have access to the Support Portal, the TBMQ support team can assist with system deployment as part of the subscription. However, this applies only if you follow recommended installation methods and architecture. Custom installation scripts or non-recommended deployment scenarios are not covered under included support. If your subscription plan does not include support, then we recommend using our documentation, tutorials, and optional professional services. To discuss options, please <a target="_blank" href="/contact-us/" rel="noopener noreferrer">contact us</a>.</p>`,
+				answer: `<p>If your subscription includes response time support and you have access to the Support Portal, the TBMQ support team can assist with system deployment as part of the subscription. However, this applies only if you follow recommended installation methods and architecture. Custom installation scripts or non-recommended deployment scenarios are not covered under included support. If your subscription plan does not include support, then we recommend using our documentation, tutorials, and optional professional services. To discuss options, please <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">contact us</a>.</p>`,
 			},
 			{
 				id: 'tbmq-payg-contact-support',
diff --git a/src/data/pricing/faq/tbmq-self-managed-perp.ts b/src/data/pricing/faq/tbmq-self-managed-perp.ts
index 98217c7740..766fc2f731 100644
--- a/src/data/pricing/faq/tbmq-self-managed-perp.ts
+++ b/src/data/pricing/faq/tbmq-self-managed-perp.ts
@@ -38,7 +38,7 @@ export const tbmqSelfManagedPerpFaq: FaqCategory[] = [
 			{
 				id: 'tbmq-perp-servers',
 				question: 'How many servers can I have with the Perpetual license?',
-				answer: `<p>The Perpetual License initially includes a base of one licensed Production Instance. If your deployment needs to scale horizontally for increased performance, fault tolerance, or High Availability (HA), you can purchase additional Production or Development Instances at any time. This scaling enables you to permanently expand your licensed instance count, allowing for seamless horizontal scaling across your infrastructure while ensuring continuous compliance with your license terms. For purchasing details or specialized capacity needs, please <a target="_blank" href="/contact-us/" rel="noopener noreferrer">contact our sales team</a>.</p>`,
+				answer: `<p>The Perpetual License initially includes a base of one licensed Production Instance. If your deployment needs to scale horizontally for increased performance, fault tolerance, or High Availability (HA), you can purchase additional Production or Development Instances at any time. This scaling enables you to permanently expand your licensed instance count, allowing for seamless horizontal scaling across your infrastructure while ensuring continuous compliance with your license terms. For purchasing details or specialized capacity needs, please <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">contact our sales team</a>.</p>`,
 			},
 			{
 				id: 'tbmq-perp-min-cost',
@@ -75,7 +75,7 @@ export const tbmqSelfManagedPerpFaq: FaqCategory[] = [
 			{
 				id: 'tbmq-perp-renewal-fee',
 				question: 'What is the renewal fee per year?',
-				answer: `<p>The annual renewal fee for the Perpetual License depends on the total value of your license. <a target="_blank" href="/contact-us/" rel="noopener noreferrer">Contact us</a> for more details.</p>`,
+				answer: `<p>The annual renewal fee for the Perpetual License depends on the total value of your license. <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">Contact us</a> for more details.</p>`,
 			},
 			{
 				id: 'tbmq-perp-no-renew',
@@ -91,7 +91,7 @@ export const tbmqSelfManagedPerpFaq: FaqCategory[] = [
 			{
 				id: 'tbmq-perp-missed-renewal',
 				question: 'If I miss 1 year and then decide to prolong, how much should I pay?',
-				answer: `<p>If you miss the renewal for one year and then decide to renew, you will need to pay the yearly renewal fee for the missed period, in addition to the fee for the new period. If you miss 6 months after the initial expiration date, you can still renew by paying the annual fee, and the renewal will be calculated based on the original expiration date of your license, not from the moment you choose to renew. If you require further clarifications on this, please <a target="_blank" href="/contact-us/" rel="noopener noreferrer">contact us</a>, and we will be happy to explain.</p>`,
+				answer: `<p>If you miss the renewal for one year and then decide to renew, you will need to pay the yearly renewal fee for the missed period, in addition to the fee for the new period. If you miss 6 months after the initial expiration date, you can still renew by paying the annual fee, and the renewal will be calculated based on the original expiration date of your license, not from the moment you choose to renew. If you require further clarifications on this, please <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">contact us</a>, and we will be happy to explain.</p>`,
 			},
 			{
 				id: 'tbmq-perp-extra-fees',
@@ -101,12 +101,12 @@ export const tbmqSelfManagedPerpFaq: FaqCategory[] = [
 			{
 				id: 'tbmq-perp-refund',
 				question: 'Can I request a refund after purchasing the license?',
-				answer: `<p>Since the Perpetual License is a one-time purchase granting lifetime access, all sales are final. However, we encourage customers to explore our subscription options before committing to a perpetual license. Subscriptions provide full access to TBMQ Professional Edition, allowing you to evaluate its features and scalability. If you need guidance on selecting the best licensing option for your needs, our <a target="_blank" href="/contact-us/" rel="noopener noreferrer">sales team</a> is happy to assist you.</p>`,
+				answer: `<p>Since the Perpetual License is a one-time purchase granting lifetime access, all sales are final. However, we encourage customers to explore our subscription options before committing to a perpetual license. Subscriptions provide full access to TBMQ Professional Edition, allowing you to evaluate its features and scalability. If you need guidance on selecting the best licensing option for your needs, our <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">sales team</a> is happy to assist you.</p>`,
 			},
 			{
 				id: 'tbmq-perp-bulk-discount',
 				question: 'Do you offer discounts for multiple licenses?',
-				answer: `<p><a target="_blank" href="/contact-us/" rel="noopener noreferrer">Contact our sales team</a> for bulk pricing options.</p>`,
+				answer: `<p><a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">Contact our sales team</a> for bulk pricing options.</p>`,
 			},
 			{
 				id: 'tbmq-perp-instance-price',
@@ -178,7 +178,7 @@ export const tbmqSelfManagedPerpFaq: FaqCategory[] = [
 			{
 				id: 'tbmq-perp-offline',
 				question: 'Can I run offline?',
-				answer: `<p>By default, the platform requires active Internet access or at least access to License server from your host machine. If Offline access is a must, please <a target="_blank" href="/contact-us/" rel="noopener noreferrer">contact us</a> to discuss options.</p>`,
+				answer: `<p>By default, the platform requires active Internet access or at least access to License server from your host machine. If Offline access is a must, please <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">contact us</a> to discuss options.</p>`,
 			},
 			{
 				id: 'tbmq-perp-backup',
@@ -246,7 +246,7 @@ export const tbmqSelfManagedPerpFaq: FaqCategory[] = [
 			{
 				id: 'tbmq-perp-convert-trial',
 				question: 'Can I convert a trial instance into a perpetual license?',
-				answer: `<p>Yes, you can convert your self-managed subscription to a perpetual license by purchasing the perpetual license and replacing the license key in the configuration files. For more details, please <a target="_blank" href="/contact-us/" rel="noopener noreferrer">contact us</a>.</p>`,
+				answer: `<p>Yes, you can convert your self-managed subscription to a perpetual license by purchasing the perpetual license and replacing the license key in the configuration files. For more details, please <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">contact us</a>.</p>`,
 			},
 			{
 				id: 'tbmq-perp-refunds',
@@ -272,18 +272,18 @@ export const tbmqSelfManagedPerpFaq: FaqCategory[] = [
 			{
 				id: 'tbmq-perp-additional-support',
 				question: 'Can I purchase additional support for my perpetual license?',
-				answer: `<p>Yes, you can purchase additional services such as managed services, advanced SLAs, consultancy, development, and training. For more details, please <a target="_blank" href="/contact-us/" rel="noopener noreferrer">contact our sales team</a>.</p>`,
+				answer: `<p>Yes, you can purchase additional services such as managed services, advanced SLAs, consultancy, development, and training. For more details, please <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">contact our sales team</a>.</p>`,
 			},
 			{
 				id: 'tbmq-perp-24-7',
 				question: 'Do you offer 24/7 support?',
-				answer: `<p>Yes, we can provide 24/7 support as part of our managed services with an additional signed SLA. Please <a target="_blank" href="/contact-us/" rel="noopener noreferrer">contact us</a> for more details.</p>`,
+				answer: `<p>Yes, we can provide 24/7 support as part of our managed services with an additional signed SLA. Please <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">contact us</a> for more details.</p>`,
 			},
 			{
 				id: 'tbmq-perp-maintenance',
 				question:
 					'Do you provide full maintenance services for TBMQ deployed on my infrastructure?',
-				answer: `<p>Yes, we offer full maintenance services for instances deployed on your infrastructure. These services can be customized based on your needs and are provided under an additional SLA, ensuring regular monitoring, updates, and issue resolution. For more details please <a target="_blank" href="/contact-us/" rel="noopener noreferrer">contact us</a>.</p>`,
+				answer: `<p>Yes, we offer full maintenance services for instances deployed on your infrastructure. These services can be customized based on your needs and are provided under an additional SLA, ensuring regular monitoring, updates, and issue resolution. For more details please <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">contact us</a>.</p>`,
 			},
 			{
 				id: 'tbmq-perp-contact-support',
@@ -293,7 +293,7 @@ export const tbmqSelfManagedPerpFaq: FaqCategory[] = [
 			{
 				id: 'tbmq-perp-setup-help',
 				question: 'How can I get help with installation and setup?',
-				answer: `<p>All perpetual license packages provide dedicated support with predefined response time and access to the ThingsBoard Support Portal. Our expert support team is available to assist you with system deployment by following our recommended <a target="_blank" href="/docs/mqtt-broker/installation/" rel="noopener noreferrer">installation methods</a> and architecture, ensuring a smooth and efficient setup. For custom installation scripts or alternative deployment scenarios, additional support options are available and you can <a target="_blank" href="/contact-us/" rel="noopener noreferrer">contact us</a> to discuss your needs.</p>`,
+				answer: `<p>All perpetual license packages provide dedicated support with predefined response time and access to the ThingsBoard Support Portal. Our expert support team is available to assist you with system deployment by following our recommended <a target="_blank" href="/docs/mqtt-broker/installation/" rel="noopener noreferrer">installation methods</a> and architecture, ensuring a smooth and efficient setup. For custom installation scripts or alternative deployment scenarios, additional support options are available and you can <a target="_blank" href="/contact-us/?subject=TBMQ" rel="noopener noreferrer">contact us</a> to discuss your needs.</p>`,
 			},
 		],
 	},
diff --git a/src/data/redirects.ts b/src/data/redirects.ts
index bc0d830742..a51e82f753 100644
--- a/src/data/redirects.ts
+++ b/src/data/redirects.ts
@@ -15,6 +15,10 @@
  *   SINGLE         — one page moved to a different path
  *   GONE           — page removed, redirect to fallback
  */
+// Relative import (not `@data/…`): this file is loaded by plain Node in
+// `pnpm generate:redirects` and by Astro's config loader, where tsconfig
+// path aliases don't resolve.
+import { TBMQ_ORIGIN, TBMQ_URLS } from './external-sites.ts';
 
 // ---------------------------------------------------------------------------
 // Types
@@ -146,17 +150,6 @@ export const CATCH_ALL_REDIRECTS: CatchAllRedirect[] = [
 		newPrefix: 'iot-gateway/installation',
 		entries: [], // PREFIX_RENAME — splat rule in _redirects; rpi/windows overrides in SINGLE_REDIRECTS
 	},
-	// TBMQ install: mqtt-broker/install/* → mqtt-broker/installation/*
-	{
-		oldPrefix: 'mqtt-broker/install',
-		newPrefix: 'mqtt-broker/installation',
-		entries: [], // PREFIX_RENAME — splat rule in _redirects
-	},
-	{
-		oldPrefix: 'mqtt-broker/pe/install',
-		newPrefix: 'mqtt-broker/pe/installation',
-		entries: [],
-	},
 	// Trendz install: trendz/install/* → trendz/installation/*
 	{
 		oldPrefix: 'trendz/install',
@@ -179,10 +172,9 @@ export const CATCH_ALL_REDIRECTS: CatchAllRedirect[] = [
 		excludeSlugs: ['user-guide/cli', 'reference/java-client', 'reference/python-client'],
 	},
 	{ oldPrefix: 'pe/mobile', newPrefix: 'mobile/pe', entries: [] },
-	// TBMQ PE Jekyll URLs — must come before `pe/mqtt-broker` so install/* maps directly
-	// to mqtt-broker/pe/installation/* (Cloudflare doesn't chain redirects)
-	{ oldPrefix: 'pe/mqtt-broker/install', newPrefix: 'mqtt-broker/pe/installation', entries: [] },
-	{ oldPrefix: 'pe/mqtt-broker', newPrefix: 'mqtt-broker/pe', entries: [] },
+	// TBMQ prefixes (mqtt-broker/install, mqtt-broker/pe/install, pe/mqtt-broker/…)
+	// are cross-origin now — the TBMQ cutover group in DYNAMIC_REDIRECTS below
+	// forwards the whole tree verbatim and tbmq.io resolves these legacy shapes.
 	{
 		oldPrefix: 'user-guide/install/upgrade-instructions',
 		entries: buildUpgradeRedirectEntries('installation/upgrade-instructions'),
@@ -1118,35 +1110,6 @@ export const SINGLE_REDIRECTS: SingleRedirect[] = [
 	{ oldPath: 'paas/eu/samples/analytics/ollama', target: '/docs/paas/eu/user-guide/local-ai-ollama/' },
 	{ oldPath: 'samples/analytics/ollama/nginx', target: '/docs/user-guide/local-ai-ollama/' },
 	{ oldPath: 'samples/analytics/spark-integration-with-thingsboard', target: '/docs/user-guide/ai-models/' },
-	// TBMQ CE redirects
-	{ oldPath: 'mqtt-broker/api', target: '/docs/mqtt-broker/rest-api/' },
-	{ oldPath: 'mqtt-broker/faq', target: '/docs/mqtt-broker/why-tbmq/' },
-	{ oldPath: 'mqtt-broker/getting-started-guides/what-is-thingsboard-mqtt-broker', target: '/docs/mqtt-broker/why-tbmq/' },
-	{ oldPath: 'mqtt-broker/image-gallery', target: '/docs/mqtt-broker/pe/image-gallery/' },
-	{ oldPath: 'mqtt-broker/install/cluster/helm-cluster-setup-options', target: '/docs/mqtt-broker/installation/' },
-	{ oldPath: 'mqtt-broker/install/installation-options', target: '/docs/mqtt-broker/installation/' },
-	{ oldPath: 'mqtt-broker/install/cluster/helm-cluster-upgrading-options', target: '/docs/mqtt-broker/installation/upgrade-instructions/' },
-	{ oldPath: 'mqtt-broker/install/cluster/resources/upgrade-options/docker-compose-upgrade-tbmq-with-from-version', target: '/docs/mqtt-broker/installation/upgrade-instructions/' },
-	{ oldPath: 'mqtt-broker/install/cluster/resources/upgrade-options/docker-compose-upgrade-tbmq-without-from-version', target: '/docs/mqtt-broker/installation/upgrade-instructions/' },
-	{ oldPath: 'mqtt-broker/install/cluster/resources/upgrade-options/k8s-upgrade-tbmq-with-from-version', target: '/docs/mqtt-broker/installation/upgrade-instructions/' },
-	{ oldPath: 'mqtt-broker/subscription', target: '/docs/mqtt-broker/pe/subscription/' },
-	{ oldPath: 'mqtt-broker/troubleshooting', target: '/docs/mqtt-broker/help/' },
-	{ oldPath: 'mqtt-broker/user-guide/ui/mail-server', target: '/docs/mqtt-broker/user-guide/ui/settings/' },
-	{ oldPath: 'mqtt-broker/white-labeling', target: '/docs/mqtt-broker/pe/white-labeling/' },
-	// TBMQ PE redirects
-	{ oldPath: 'pe/mqtt-broker/api', target: '/docs/mqtt-broker/pe/rest-api/' },
-	{ oldPath: 'pe/mqtt-broker/faq', target: '/docs/mqtt-broker/pe/why-tbmq/' },
-	{ oldPath: 'pe/mqtt-broker/getting-started-guides/what-is-thingsboard-mqtt-broker', target: '/docs/mqtt-broker/pe/why-tbmq/' },
-	{ oldPath: 'pe/mqtt-broker/image-gallery', target: '/docs/mqtt-broker/pe/image-gallery/' },
-	{ oldPath: 'pe/mqtt-broker/install/cluster/helm-cluster-setup-options', target: '/docs/mqtt-broker/pe/installation/' },
-	{ oldPath: 'pe/mqtt-broker/install/installation-options', target: '/docs/mqtt-broker/pe/installation/' },
-	{ oldPath: 'pe/mqtt-broker/install/cluster/helm-cluster-upgrading-options', target: '/docs/mqtt-broker/pe/installation/upgrade-instructions/' },
-	{ oldPath: 'pe/mqtt-broker/install/cluster/resources/upgrade-options/docker-compose-upgrade-tbmq-with-from-version', target: '/docs/mqtt-broker/pe/installation/upgrade-instructions/' },
-	{ oldPath: 'pe/mqtt-broker/install/cluster/resources/upgrade-options/docker-compose-upgrade-tbmq-without-from-version', target: '/docs/mqtt-broker/pe/installation/upgrade-instructions/' },
-	{ oldPath: 'pe/mqtt-broker/install/cluster/resources/upgrade-options/k8s-upgrade-tbmq-with-from-version', target: '/docs/mqtt-broker/pe/installation/upgrade-instructions/' },
-	{ oldPath: 'pe/mqtt-broker/troubleshooting', target: '/docs/mqtt-broker/pe/help/' },
-	{ oldPath: 'pe/mqtt-broker/user-guide/ui/mail-server', target: '/docs/mqtt-broker/pe/user-guide/ui/settings/' },
-
 	// Services (docs → non-docs)
 	{ oldPath: 'services', target: '/services/' },
 	{ oldPath: 'services/consulting', target: '/services/development-services/' },
@@ -1318,7 +1281,6 @@ export const SINGLE_REDIRECTS: SingleRedirect[] = [
 	{ oldPath: 'user-guide/install', target: '/docs/installation/' },
 	{ oldPath: 'user-guide/install/openbsd', target: '/docs/installation/' },
 	{ oldPath: 'user-guide/install-and-use/install', target: '/docs/installation/' },
-	{ oldPath: 'mqtt-broker/security', target: '/docs/mqtt-broker/security/overview/' },
 	{ oldPath: 'reference/apis', target: '/docs/apis-and-sdks/' },
 	{ oldPath: 'reference/device-connectivity-api', target: '/docs/apis-and-sdks/' },
 	{ oldPath: 'reference/edge', target: '/docs/edge/' },
@@ -1350,6 +1312,9 @@ export const NON_DOCS_REDIRECTS: Record<string, string> = {
 	// Services
 	'/services/support/': '/services/',
 
+	// TBMQ — moved to tbmq.io, whose site root is the product landing
+	'/products/mqtt-broker/': TBMQ_URLS.product,
+
 	// Trendz
 	'/products/trendz/trndz-request-demo/': '/products/trendz/request-demo/',
 	'/images/trendz/trndz-request-demo/': '/products/trendz/request-demo/',
@@ -1477,6 +1442,19 @@ export const DYNAMIC_REDIRECTS: DynamicRedirectGroup[] = [
 			{ source: '/docs/license/*', target: '/docs/license-server/:splat' },
 		],
 	},
+	{
+		comment:
+			'TBMQ cutover — the docs tree moved to tbmq.io. Forwarded verbatim ' +
+			'(mqtt-broker/ segment kept): tbmq.io keys its full legacy redirect table ' +
+			'on that shape and strips the segment on its own edge, so every rename ' +
+			'lives in one repo and this side stays a two-rule identity forward. ' +
+			'Deliberately absent from astro.redirects.ts so the local TBMQ pages stay ' +
+			'browsable in dev until deleted.',
+		entries: [
+			{ source: '/docs/pe/mqtt-broker/*', target: `${TBMQ_ORIGIN}/docs/pe/mqtt-broker/:splat` },
+			{ source: '/docs/mqtt-broker/*', target: `${TBMQ_ORIGIN}/docs/mqtt-broker/:splat` },
+		],
+	},
 	{
 		comment: 'Docs — versioned releases-table pages moved under /releases/',
 		entries: [