fern-api · devalog · Feb 20, 2026 · Feb 19, 2026 · Feb 20, 2026 · Feb 20, 2026
diff --git a/fern/products/dashboard/pages/pdf-export.mdx b/fern/products/dashboard/pages/pdf-export.mdx
@@ -3,6 +3,8 @@ title: PDF export
 description: Export your documentation site as a PDF from the Fern Dashboard.
 ---
 
+<Markdown src="/snippets/pro-plan.mdx"/>
+
 Export your complete documentation site as a PDF directly from the [Fern Dashboard](https://dashboard.buildwithfern.com/). The generated PDF includes a cover page, table of contents with clickable links, and all content pages with headers and footers.
 
 ## Export your site

diff --git a/fern/products/docs/pages/api-references/generate-websocket-ref.mdx b/fern/products/docs/pages/api-references/generate-websocket-ref.mdx
@@ -3,8 +3,6 @@ title: Generate WebSocket Reference
 description: Use Fern Docs to generate WebSocket Reference documentation from an AsyncAPI spec or Fern Definition.
 ---
 
-<Markdown src="/snippets/pro-plan.mdx"/>
-
 Fern generates WebSocket Reference documentation from an [AsyncAPI specification](/learn/api-definitions/asyncapi/overview) or [Fern Definition](/learn/api-definition/fern/websockets).
 
 <Frame caption={<a href="https://developers.deepgram.com/reference/text-to-speech/speak-streaming">Example of how a WebSocket API Reference renders in Fern</a>}>

diff --git a/fern/products/docs/pages/authentication/api-key-injection.mdx b/fern/products/docs/pages/authentication/api-key-injection.mdx
@@ -3,7 +3,7 @@ title: API key injection
 subtitle: Automatically populate API keys in the API Explorer for logged-in users.
 ---
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 API key injection is a feature of [JWT](/learn/docs/authentication/setup/jwt) and [OAuth](/learn/docs/authentication/setup/oauth) authentication. When a user logs in, a [`fern_token`](/learn/docs/authentication/overview#how-authentication-works) cookie is set in their browser with a `fern.playground` claim that tells the [API Explorer](/learn/docs/api-references/api-explorer) what values to pre-fill — API keys, headers, or other credentials. You can combine it with [RBAC](/learn/docs/authentication/features/rbac) in a single token.
 

diff --git a/fern/products/docs/pages/authentication/jwt-setup.mdx b/fern/products/docs/pages/authentication/jwt-setup.mdx
@@ -3,6 +3,8 @@ title: Set up JWT
 subtitle: Self-managed authentication integrated with your login system
 ---
 
+<Markdown src="/snippets/enterprise-plan.mdx"/>
+
 With JWT, you manage the entire auth flow. This involves building and signing a [`fern_token`](/learn/docs/authentication/overview#how-authentication-works) cookie that integrates your docs with your existing login system. Like [OAuth](/learn/docs/authentication/setup/oauth), JWT enables:
 
 - **Login only** — gate docs behind authentication

diff --git a/fern/products/docs/pages/authentication/oauth-setup.mdx b/fern/products/docs/pages/authentication/oauth-setup.mdx
@@ -3,6 +3,8 @@ title: Set up OAuth
 subtitle: Fern-managed authentication integrated with your login system
 ---
 
+<Markdown src="/snippets/enterprise-plan.mdx"/>
+
 With OAuth, Fern manages the auth flow for you. You give Fern access to your OAuth provider, and Fern handles the [`fern_token`](/learn/docs/authentication/overview#how-authentication-works) cookie that integrates your docs with your existing login system. Like [JWT](/learn/docs/authentication/setup/jwt), OAuth enables:
 
 - **[RBAC](/learn/docs/authentication/features/rbac)** — restrict content by user role

diff --git a/fern/products/docs/pages/authentication/password.mdx b/fern/products/docs/pages/authentication/password.mdx
@@ -3,7 +3,7 @@ title: Password protection
 subtitle: Protect your documentation site with a shared password for simple access control.
 ---
 
-<Markdown src="/snippets/enterprise-plan.mdx"/>
+<Markdown src="/snippets/pro-plan.mdx"/>
 
 Password protection allows you to restrict access to your documentation site using a shared password. This is useful for pre-release documentation, internal resources, or any content you want to keep private without requiring individual user accounts.
 

diff --git a/fern/products/docs/pages/authentication/rbac.mdx b/fern/products/docs/pages/authentication/rbac.mdx
@@ -4,7 +4,7 @@ subtitle: Control who can view your documentation
 description: Learn how to restrict access to your documentation using role-based access control (RBAC)
 ---
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 RBAC is a feature of [JWT](/learn/docs/authentication/setup/jwt) and [OAuth](/learn/docs/authentication/setup/oauth) authentication. Once a user logs in through either method, Fern checks the [`fern_token`](/learn/docs/authentication/overview#how-authentication-works) cookie to determine their roles and controls access to pages, sections, and other navigation items accordingly. 
 

diff --git a/...ucts/docs/pages/component-library/custom-components/custom-react-components.mdx b/...ucts/docs/pages/component-library/custom-components/custom-react-components.mdx
@@ -4,7 +4,7 @@ description: Add custom React components to your Fern docs for interactive, serv
 slug: customization/custom-react-components
 ---
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 You can extend Fern's built-in component library by adding your own custom React components. This allows you to create unique, interactive elements that match your documentation needs. Components are server-side rendered for better SEO and performance, with no layout shifts.
 

diff --git a/fern/products/docs/pages/customization/custom-header-footer.mdx b/fern/products/docs/pages/customization/custom-header-footer.mdx
@@ -3,7 +3,7 @@ title: Header and footer
 description: Replace Fern's default header or footer with your own server-rendered React components for better SEO and performance.
 ---
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 Replace Fern's default header or footer with your own React components. Components are server-side rendered for better SEO and performance, with no layout shifts.
 

diff --git a/fern/products/docs/pages/navigation/versions.mdx b/fern/products/docs/pages/navigation/versions.mdx
@@ -4,7 +4,7 @@ subtitle: Learn how to add versioning to your Fern documentation. Configure mult
 ---
 
 <Warning>
-  Versioning is available on [all plans](https://buildwithfern.com/pricing#Docs): up to 3 versions on Basic, 10 versions on Pro, or unlimited on Enterprise. Contact support@buildwithfern.com for more information.
+  Versioning is available on [all plans](https://buildwithfern.com/pricing#Docs): up to 3 versions on Hobby, 10 versions on Pro, or unlimited on Enterprise. Contact support@buildwithfern.com for more information.
 </Warning>
 
 <Frame>
@@ -201,4 +201,4 @@ The dropdown menu for the version selector can be customized using the `fern-ver
     <img src="webflow-version-selector.avif" alt="Example of a styled version selector" />
   </Frame>
 </Accordion>
-</AccordionGroup>
+</AccordionGroup>