docs: add Intelligence CTAs to restored threads pages

BenTaylorDev · claude · MikeRyanDev · commit 0ada76b9ac01 · 2026-05-05T05:28:17.000-07:00
The Threads, Intelligence Platform explainer, multi-conversation
tutorial, useThreads reference, and the shared threads snippet were
restored at their pre-rollout state, so they carried no OpsPlatformCTA
while peer pages picked one up earlier on this branch. Wires each
restored page to the new try_for_free_clicked event with snake_case
surface identifiers, and fixes the "a Enterprise" → "an Enterprise"
article mismatch the rebrand left in both self-hosting pages.

Co-Authored-By: Claude Opus 4.7 (1M context) &lt;noreply@anthropic.com&gt;
diff --git a/docs/content/docs/(root)/premium/self-hosting.mdx b/docs/content/docs/(root)/premium/self-hosting.mdx
@@ -17,7 +17,7 @@ CopilotKit Intelligence — the platform that powers threads, shared state, the
 - Your organization requires CopilotKit Intelligence to run inside your own VPC or data center for compliance, data residency, or security reasons
 - You want to connect Intelligence to internal databases, identity providers, or secret stores that are not reachable from Copilot Cloud
 - You need to operate the platform under your existing Kubernetes tooling, CI/CD, and observability stack
-- You have a Enterprise Intelligence Platform license and the platform-engineering capacity to run a production Kubernetes workload
+- You have an Enterprise Intelligence Platform license and the platform-engineering capacity to run a production Kubernetes workload
 
 If none of these apply, use [Copilot Cloud](https://cloud.copilotkit.ai) — it is the fastest path to a working Intelligence deployment and requires no cluster operations.
 
diff --git a/docs/content/docs/(root)/threads.mdx b/docs/content/docs/(root)/threads.mdx
@@ -16,6 +16,13 @@ import {
 
 CopilotKit threads enable persistent, resumable multi-turn conversations. The `useThreads` hook lists, creates, renames, archives, and deletes threads with realtime synchronization via WebSocket. Threads work with any agent framework — the Enterprise Intelligence Platform stores conversation history server-side, so users can close their browser and pick up where they left off. Thread metadata updates (renames, archives, new threads) are pushed to all connected clients in realtime without polling.
 
+<OpsPlatformCTA
+  variant="inline"
+  title="Threads run on the Enterprise Intelligence Platform"
+  body="Get persistent threads, realtime sync, and observability on the free Developer tier."
+  surface="docs_threads"
+/>
+
 ## When should I use this?
 
 - Your app needs multiple saved conversations per user (like a chat history sidebar)
diff --git a/docs/content/docs/learn/intelligence-platform.mdx b/docs/content/docs/learn/intelligence-platform.mdx
@@ -12,6 +12,13 @@ The Enterprise Intelligence Platform is the backend that powers threads, shared
 
 This page covers the logical architecture that applies to both deployment modes, plus the operational concerns specific to running the platform in your own cluster. Self-hosting is a premium deployment mode: it gives you data residency and compliance control at the cost of running a production Kubernetes workload.
 
+<OpsPlatformCTA
+  variant="inline"
+  title="Try the Enterprise Intelligence Platform"
+  body="Spin up a hosted project on Copilot Cloud — no credit card, free Developer tier."
+  surface="docs_learn_intelligence_platform"
+/>
+
 ## Key concepts
 
 ### Two planes
diff --git a/docs/content/docs/learn/threads.mdx b/docs/content/docs/learn/threads.mdx
@@ -12,6 +12,13 @@ A thread is a persistent, server-side container for a multi-turn conversation be
 
 Threads are a platform-level concept, not tied to any specific agent framework. Whether your backend uses LangGraph, Mastra, CrewAI, or any other framework, threads work the same way.
 
+<OpsPlatformCTA
+  variant="inline"
+  title="Want to see threads in your own app?"
+  body="Persistent threads ship with the Enterprise Intelligence Platform on the free Developer tier."
+  surface="docs_learn_threads"
+/>
+
 ## Key concepts
 
 ### Thread vs. Run
diff --git a/docs/content/docs/learn/tutorials/multi-conversation-chat.mdx b/docs/content/docs/learn/tutorials/multi-conversation-chat.mdx
@@ -24,6 +24,13 @@ A chat application with a thread sidebar — similar to ChatGPT or Claude's conv
 - A CopilotKit project with the Enterprise Intelligence Platform configured (via [Copilot Cloud](https://cloud.copilotkit.ai) or [self-hosted](/premium/self-hosting))
 - `@copilotkit/react-core` v1.50+
 
+<OpsPlatformCTA
+  variant="inline"
+  title="Need an Intelligence Platform project?"
+  body="The free Developer tier on Copilot Cloud has everything this tutorial uses — threads, realtime sync, and a license key."
+  surface="docs_tutorial_multi_conversation_chat"
+/>
+
 ## Steps
 
 <Steps>
diff --git a/docs/content/docs/reference/v2/hooks/useThreads.mdx b/docs/content/docs/reference/v2/hooks/useThreads.mdx
@@ -11,6 +11,14 @@ doc_type: reference
 
 Threads are sorted by most recently updated first. The hook supports cursor-based pagination when a `limit` is provided.
 
+<OpsPlatformCTA
+  variant="card"
+  title="useThreads needs an Enterprise Intelligence Platform project"
+  body="Sign up for a free account to get a publicLicenseKey and start syncing threads."
+  ctaLabel="Create a free account"
+  surface="docs_reference_use_threads"
+/>
+
 ## Signature
 
 ```tsx
diff --git a/docs/snippets/shared/premium/self-hosting.mdx b/docs/snippets/shared/premium/self-hosting.mdx
@@ -10,7 +10,7 @@ CopilotKit Intelligence — the platform that powers threads, shared state, the
 - Your organization requires CopilotKit Intelligence to run inside your own VPC or data center for compliance, data residency, or security reasons
 - You want to connect Intelligence to internal databases, identity providers, or secret stores that are not reachable from Copilot Cloud
 - You need to operate the platform under your existing Kubernetes tooling, CI/CD, and observability stack
-- You have a Enterprise Intelligence Platform license and the platform-engineering capacity to run a production Kubernetes workload
+- You have an Enterprise Intelligence Platform license and the platform-engineering capacity to run a production Kubernetes workload
 
 If none of these apply, use [Copilot Cloud](https://cloud.copilotkit.ai) — it is the fastest path to a working Intelligence deployment and requires no cluster operations.
 
diff --git a/docs/snippets/shared/threads/threads.mdx b/docs/snippets/shared/threads/threads.mdx
@@ -5,6 +5,13 @@ import { Tabs, Tab } from "fumadocs-ui/components/tabs";
 
 CopilotKit threads enable persistent, resumable multi-turn conversations. The `useThreads` hook lists, creates, renames, archives, and deletes threads with realtime synchronization via WebSocket. Threads work with any agent framework — the Enterprise Intelligence Platform stores conversation history server-side, so users can close their browser and pick up where they left off. Thread metadata updates (renames, archives, new threads) are pushed to all connected clients in realtime without polling.
 
+<OpsPlatformCTA
+  variant="inline"
+  title="Threads run on the Enterprise Intelligence Platform"
+  body="Get persistent threads, realtime sync, and observability on the free Developer tier."
+  surface="docs_threads_integration"
+/>
+
 ## When should I use this?
 
 - Your app needs multiple saved conversations per user (like a chat history sidebar)
