Standardize references to Pro and Enterprise plans (#921)

devalog · web-flow · commit 570747599c3b · 2025-09-22T16:19:29.000-04:00
diff --git a/fern/products/api-def/asyncapi-pages/auth.mdx b/fern/products/api-def/asyncapi-pages/auth.mdx
@@ -141,6 +141,8 @@ components:
 
 ## OAuth2 security scheme
 
+<Markdown src="/snippets/pro-plan.mdx"/>
+
 OAuth2 authentication is supported for AsyncAPI specifications:
 
 ```yml title="asyncapi.yml" {3-11}
diff --git a/fern/products/api-def/asyncapi-pages/extensions/audiences.mdx b/fern/products/api-def/asyncapi-pages/extensions/audiences.mdx
@@ -3,6 +3,8 @@ title: Use audiences to filter your API
 subtitle: Use `x-fern-audiences` to filter to relevant operations, channels and message schemas
 ---
 
+<Markdown src="/snippets/pro-plan.mdx"/>
+
 Audiences are a useful tool for segmenting your event-driven API for different consumers. Common examples of audiences include `public`
 and `beta`.
 
diff --git a/fern/products/api-def/ferndef-pages/audiences.mdx b/fern/products/api-def/ferndef-pages/audiences.mdx
@@ -3,6 +3,8 @@ title: Audiences in Fern Definition
 subtitle: Use audiences in your Fern Definition to segment your API for different groups of consumers.
 ---
 
+<Markdown src="/snippets/pro-plan.mdx"/>
+
 Audiences are a useful tool for segmenting your API for different consumers. You can configure your Fern Docs to publish documentation specific to an `Audience`. You can use [audiences in your OpenAPI Specification](/learn/api-definitions/openapi/extensions/audiences), too. 
 
 Common examples of audiences include:
diff --git a/fern/products/api-def/ferndef-pages/auth.mdx b/fern/products/api-def/ferndef-pages/auth.mdx
@@ -178,6 +178,8 @@ client = new Client({
 
 ## OAuth client credentials
 
+<Markdown src="/snippets/pro-plan.mdx"/>
+
 If your API uses OAuth, you can specify an oauth scheme in `api.yml` and define a token retrieval endpoint in a separate `auth.yml` file ([example](https://github.com/fern-api/fern/blob/3137938b70e058f3691ddef34d5c1cc29acc4b80/test-definitions/fern/apis/oauth-client-credentials/definition/api.yml)). 
 
 ```yaml api.yml
diff --git a/fern/products/api-def/ferndef-pages/endpoints/sse.mdx b/fern/products/api-def/ferndef-pages/endpoints/sse.mdx
@@ -3,10 +3,9 @@ title: Server-Sent Events and Streaming APIs
 subtitle: Use the `response-stream` key to model streaming endpoints
 ---
 
-<Note>
-  Specifying `response-stream` on an endpoints allows you to represent endpoint responses that are streaming. 
-</Note>
+<Markdown src="/snippets/pro-plan.mdx"/>
 
+Specifying `response-stream` on an endpoints allows you to represent endpoint responses that are streaming. 
 
 ## JSON streaming
 
diff --git a/fern/products/api-def/ferndef-pages/websockets.mdx b/fern/products/api-def/ferndef-pages/websockets.mdx
@@ -87,7 +87,7 @@ Fern renders a unique reference page for WebSockets. The **Handshake** section o
 
 ### WebSocket Playground
 
-<Markdown src="/snippets/pro-callout.mdx" />
+<Markdown src="/snippets/pro-plan.mdx" />
 
 Users can connect to and use WebSockets from right within the API Reference (check one of Hume's WebSockets [here](https://dev.hume.ai/reference/empathic-voice-interface-evi/chat/chat)). 
 
diff --git a/fern/products/api-def/grpc-pages/overview.mdx b/fern/products/api-def/grpc-pages/overview.mdx
@@ -3,6 +3,8 @@ title: What is gRPC?
 description: gRPC is a high-performance RPC framework that uses Protocol Buffers
 ---
 
+<Markdown src="/snippets/enterprise-plan.mdx"/>
+
 <Note>
   Fern only supports gRPC SDK generation for .NET/C#.
 </Note>
diff --git a/fern/products/api-def/openapi-pages/endpoints/sse.mdx b/fern/products/api-def/openapi-pages/endpoints/sse.mdx
@@ -3,10 +3,7 @@ title: Server-Sent Events and Streaming APIs
 subtitle: Use the `x-fern-streaming` extension to model streaming endpoints
 ---
 
-<Note>
-  The `x-fern-streaming` extension allows you to represent endpoints that are streaming. 
-</Note>
-
+The `x-fern-streaming` extension allows you to represent endpoints that are streaming. 
 
 ## JSON streaming
 
@@ -42,6 +39,8 @@ components:
 
 ## Server-sent events 
 
+<Markdown src="/snippets/pro-plan.mdx"/>
+
 If your API returns server-sent-events, with the `data` and `event` keys as seen below
 
 ```json
diff --git a/fern/products/api-def/openapi-pages/extensions/audiences.mdx b/fern/products/api-def/openapi-pages/extensions/audiences.mdx
@@ -3,6 +3,8 @@ title: Use audiences to filter your API
 subtitle: Use `x-fern-audiences` to filter to relevant endpoints, schemas and properties
 ---
 
+<Markdown src="/snippets/pro-plan.mdx"/>
+
 Audiences are a useful tool for segmenting your API for different consumers. Common examples of audiences include `public`
 and `beta`.
 
diff --git a/fern/products/api-def/openrpc-pages/overview.mdx b/fern/products/api-def/openrpc-pages/overview.mdx
@@ -3,6 +3,8 @@ title: What is an OpenRPC Specification?
 description: OpenRPC is a standard for documenting JSON-RPC APIs
 ---
 
+<Markdown src="/snippets/enterprise-plan.mdx"/>
+
 The OpenRPC Specification is a framework used by developers to document JSON-RPC APIs. The specification 
 is written in JSON or YAML and contains all of your methods, parameters, schemas, and server configurations. 
 Fern is compatible with OpenRPC specification [v1.3.2](https://spec.open-rpc.org/) and [v1.2.6](https://github.com/open-rpc/spec/releases/tag/1.2.6).
diff --git a/fern/products/api-def/pages/project-structure.mdx b/fern/products/api-def/pages/project-structure.mdx
@@ -106,6 +106,10 @@ groups:
 </Accordion>
 <Accordion title="Combined SDKs from multiple APIs">
 
+<Warning title="Pro and Enterprise feature">
+    This feature is available only for the [Pro and Enterprise plans](https://buildwithfern.com/pricing). You can merge up to five APIs into a single SDK on the Pro plan, and unlimited APIs on the Enterprise plan. To get started, reach out to support@buildwithfern.com.
+</Warning>
+
 Use this approach to merge multiple APIs into a single set of SDKs.
 
 ```bash
diff --git a/fern/products/ask-fern/pages/getting-started/api-get-started.mdx b/fern/products/ask-fern/pages/getting-started/api-get-started.mdx
@@ -3,7 +3,7 @@ title: 'Introduction'
 subtitle: 'Welcome to the Fern API reference.'
 ---
 
-<Markdown src="/snippets/pro-callout.mdx" />
+<Markdown src="/snippets/pro-plan.mdx" />
 
 The Fern AI API allows you to manage your Ask Fern configuration using Fern's public RESTful API. You can use the API to:
 
diff --git a/fern/products/cli-api-reference/pages/api-get-started.mdx b/fern/products/cli-api-reference/pages/api-get-started.mdx
@@ -3,7 +3,7 @@ title: 'Introduction'
 subtitle: 'Welcome to the Fern API reference.'
 ---
 
-<Markdown src="/snippets/pro-callout.mdx" />
+<Markdown src="/snippets/pro-plan.mdx" />
 
 The Fern API allows you to manage SDKs and code snippets using Fern's public RESTful API.
 
diff --git a/fern/products/docs/pages/api-references/audiences.mdx b/fern/products/docs/pages/api-references/audiences.mdx
@@ -3,6 +3,8 @@ title: Audiences
 subtitle: Use audiences to filter the endpoints, schemas, and properties that are displayed in your API Reference.
 ---
 
+<Markdown src="/snippets/pro-plan.mdx"/>
+
 Audiences are a useful tool for segmenting your API for different consumers. Common examples of audiences include `public` 
 and `beta`. You can configure audiences in both [the OpenAPI Specification](/learn/api-definitions/openapi/extensions/audiences) as well as [the Fern Definition](/learn/api-definition/fern/audiences).
 
diff --git a/fern/products/docs/pages/api-references/autopopulate-api-key.mdx b/fern/products/docs/pages/api-references/autopopulate-api-key.mdx
@@ -3,9 +3,7 @@ title: Auto-populate API keys
 subtitle: Make integrating with your API frictionless by adding your login flow to the API Explorer.
 ---
 
-<Tip>
-This feature is available on the Pro plan. [Contact us](https://buildwithfern.com/contact) to learn more.
-</Tip>
+<Markdown src="/snippets/pro-plan.mdx"/>
 
 Fern can integrate with your authentication flow, allowing users to login and have their API key automatically populated with the click of a button. 
 
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,6 +3,8 @@ title: Generate WebSocket Reference
 description: Learn how to generate and customize WebSocket API reference documentation
 ---
 
+<Markdown src="/snippets/pro-plan.mdx"/>
+
 Fern generates WebSocket API reference documentation from your AsyncAPI specification or Fern Definition. The AsyncAPI specification describes message-driven APIs in a machine-readable format. Fern supports the [v2](https://www.asyncapi.com/docs/reference/specification/v2.x) and [v3](https://www.asyncapi.com/docs/reference/specification/v3.0.0) specifications.
 
 <Frame caption={<a href="https://developers.deepgram.com/reference/text-to-speech-api/speak-streaming">Example of how a WebSocket API Reference renders in Fern</a>}>
diff --git a/fern/products/docs/pages/api-references/sdk-snippets.mdx b/fern/products/docs/pages/api-references/sdk-snippets.mdx
@@ -132,7 +132,9 @@ navigation:
 
 ## Access via API
 
-If you'd like to bring SDK snippets into your own documentation, you can use the [Snippets API](/learn/api-reference/snippets/get). API access requires a [SDK Business plan](https://buildwithfern.com/pricing) or above.
+<Markdown src="/snippets/pro-plan.mdx"/>
+
+If you'd like to bring SDK snippets into your own documentation, you can use the [Snippets API](/learn/api-reference/snippets/get).
 
 Merge.dev is an example of a Fern customer that uses the Snippets API to bring Python code samples [into their API Reference](https://docs.merge.dev/hris/employees/#employees_list).
 
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)
 ---
 
-<Note>RBAC is part of the pro plan.</Note>
+<Markdown src="/snippets/pro-plan.mdx"/>
 
 ## Introduction
 
diff --git a/fern/products/docs/pages/authentication/sso.mdx b/fern/products/docs/pages/authentication/sso.mdx
@@ -3,6 +3,8 @@ title: Single Sign-On
 subtitle: Enterprise authentication for secure access to your docs
 ---
 
+<Markdown src="/snippets/enterprise-plan.mdx"/>
+
 Fern’s Single Sign-On (SSO) is an enterprise feature that lets your team securely access your docs through your organization’s identity provider.
 
 <Note>SSO does not support Role-Based Access Control or API Key Injection.</Note>
@@ -47,5 +49,5 @@ Fern supports SSO integration with any identity provider that implements industr
 
 ## Setting up SSO
 
-SSO is available as part of the Enterprise plan. Reach out via Slack or [contact our team](https://buildwithfern.com/contact) to begin the SSO setup process. Fern will work with one of your security administrators to connect to your identity provider.
+Reach out via Slack or [contact our team](https://buildwithfern.com/contact) to begin the SSO setup process. Fern will work with one of your security administrators to connect to your identity provider.
 
diff --git a/fern/products/docs/pages/component-library/custom-components/custom-css-js.mdx b/fern/products/docs/pages/component-library/custom-components/custom-css-js.mdx
@@ -4,11 +4,6 @@ subtitle: Add custom CSS, global JavaScript, and UI components.
 description: Add brand-specific styling, user interactions. and components to make your docs your own.
 ---
 
-<Note>
-Custom CSS & JS are available on the Basic plan. 
-Adding Custom Components is available on the Pro plan.
-</Note>
-
 This page covers how to customize your docs with CSS, JavaScript, and custom components. However, you can [customize many things directly in your `docs.yml` file](/docs/configuration/what-is-docs-yml), including colors, typography, navbar links, layout, analytics, and metadata. Try these built-in options first before adding custom code. 
 
 ## Custom CSS
@@ -204,6 +199,8 @@ js:
 
 ## Custom components
 
+<Markdown src="/snippets/pro-plan.mdx"/>
+
 You can use custom CSS and JS to replace Fern's default UI components with your own. The `header` and `footer` 
 are the most commonly replaced components. You can replace any component in the docs, 
 including the sidebar, tabs, search bar, and more.
diff --git a/fern/products/docs/pages/enterprise/self-hosted-set-up.mdx b/fern/products/docs/pages/enterprise/self-hosted-set-up.mdx
@@ -3,7 +3,7 @@ title: Set up self-hosted documentation
 description: Learn how to set up self-hosted documentation on your own infrastructure.
 ---
 
-<Note>Self-hosted documentation is only available for the enterprise plan.</Note>
+<Markdown src="/snippets/enterprise-plan.mdx" />
 
 ## Prerequisites
 
diff --git a/fern/products/docs/pages/enterprise/self-hosted.mdx b/fern/products/docs/pages/enterprise/self-hosted.mdx
@@ -3,7 +3,7 @@ title: Self-hosted documentation
 description: Fern supports self-hosting so that you can run your docs site on your own infrastructure.
 ---
 
-<Note>Self-hosted documentation is only available for the enterprise plan.</Note>
+<Markdown src="/snippets/enterprise-plan.mdx" />
 
 Fern documentation websites are hosted on Fern's infrastructure by default. Self-hosting allows you to deploy your documentation site on your own infrastructure to meet specific security or compliance requirements.
 
diff --git a/fern/products/docs/pages/integrations/feature-flags.mdx b/fern/products/docs/pages/integrations/feature-flags.mdx
@@ -4,6 +4,8 @@ subtitle: Control documentation visibility with LaunchDarkly
 description: Learn how to use Feature Flags in your Fern documentation
 ---
 
+<Markdown src="/snippets/pro-plan.mdx"/>
+
 Fern supports conditional rendering of documentation content using feature flags, powered by [LaunchDarkly](https://app.launchdarkly.com/signup) integration. Control visibility of documentation sections based on feature flag states for different release stages or user segments.
 
 ## Use Cases
diff --git a/fern/products/docs/pages/integrations/overview.mdx b/fern/products/docs/pages/integrations/overview.mdx
@@ -97,4 +97,6 @@ are available during the workflow run.
 
 ## Connect other integrations
 
+<Markdown src="/snippets/enterprise-plan.mdx"/>
+
 If you want to integrate with a third-party analytics or support platforms that Fern doesn't directly support, you can do so [using custom JS](/docs/customization/custom-css-js#custom-javascript). 
diff --git a/fern/products/docs/pages/integrations/postman.mdx b/fern/products/docs/pages/integrations/postman.mdx
@@ -3,6 +3,8 @@ title: "Postman Integration"
 description: "Generate a postman collection full of example requests and responses"
 ---
 
+<Markdown src="/snippets/pro-plan.mdx"/>
+
 You can generate a Postman collection full of example requests and responses and
 publish your collection to Postman. The configuration for the postman generator
 lives in your fern folder, in a file called
diff --git a/fern/products/docs/pages/navigation/products.mdx b/fern/products/docs/pages/navigation/products.mdx
@@ -3,6 +3,8 @@ title: Product switching
 subtitle: Allow users to seamlessly navigate between different products you offer. 
 ---
 
+<Markdown src="/snippets/pro-plan.mdx"/>
+
 <Frame>
   <video 
     style={{ aspectRatio: '16 / 9', width: '100%' }}
diff --git a/fern/products/sdks/guides/configure-auto-pagination.mdx b/fern/products/sdks/guides/configure-auto-pagination.mdx
@@ -3,7 +3,7 @@ title: Configure Auto Pagination
 description: Paginate through API responses easily with offset, cursor, and link-based pagination.
 ---
 
-<Markdown src="/snippets/pro-callout.mdx"/>
+<Markdown src="/snippets/pro-plan.mdx"/>
 
 Fern's auto pagination supports offset-based and cursor-based pagination schemes,
 providing SDK users with simple iterators to loop through all results instead of
diff --git a/fern/products/sdks/guides/configure-idempotency.mdx b/fern/products/sdks/guides/configure-idempotency.mdx
@@ -3,7 +3,7 @@ title: Configure Idempotency Headers
 description: SDKs that safely support retrying requests
 ---
 
-<Markdown src="/snippets/pro-callout.mdx"/>
+<Markdown src="/snippets/pro-plan.mdx"/>
 
 For endpoints you've configured as idempotent, Fern's SDKs allow you to
 specify idempotency headers. Typically the headers include `Idempotency-Key`,
diff --git a/fern/products/sdks/guides/filter-your-endpoints-audiences.mdx b/fern/products/sdks/guides/filter-your-endpoints-audiences.mdx
@@ -3,7 +3,7 @@ title: Filter Your Endpoints (Audiences)
 description: Guide to filtering your API endpoints using audiences.
 ---
 
-<Markdown src="/snippets/pro-callout.mdx"/>
+<Markdown src="/snippets/pro-plan.mdx"/>
 
 Use audiences to generate tailored SDKs for different groups of API consumers. Common examples of audiences include:
 - Internal consumers (e.g., frontend developers who use the API)
diff --git a/fern/products/sdks/guides/retries-with-backoff.mdx b/fern/products/sdks/guides/retries-with-backoff.mdx
@@ -3,7 +3,7 @@ title: Retries with Backoff
 description: Automatically retry failures with exponential backoff
 ---
 
-<Markdown src="/snippets/pro-callout.mdx" />
+<Markdown src="/snippets/pro-plan.mdx" />
 
 Fern SDKs will automatically retry failed requests with exponential backoff. A request will be retried as
 long as the request is deemed retryable and the number of retry attempts has
diff --git a/fern/products/sdks/guides/self-hosted.mdx b/fern/products/sdks/guides/self-hosted.mdx
@@ -4,7 +4,7 @@ description: Fern supports self-hosting SDK generation so that you can run SDK g
   on your own infrastructure.
 ---
 
-<Note>Self-hosted SDK generation is only available for the enterprise plan.</Note>
+<Markdown src="/snippets/enterprise-plan.mdx" />
 
 Fern SDK generation runs on Fern's infrastructure by default. Self-hosting allows you to run SDK generation on your own infrastructure to meet specific security or compliance requirements.
 
diff --git a/fern/products/sdks/overview/java/configuration.mdx b/fern/products/sdks/overview/java/configuration.mdx
@@ -31,6 +31,8 @@ The provided string will be used as the client class name.
 
 <ParamField path="custom-dependencies" type="List<string>" required={false} toc={true}>
 
+<Markdown src="/snippets/pro-plan.mdx"/>
+
 Example:
 
     ```yaml
diff --git a/fern/products/sdks/overview/java/custom-code.mdx b/fern/products/sdks/overview/java/custom-code.mdx
@@ -287,7 +287,7 @@ protected void setAdditional(ClientOptions.Builder builder) {
 
 ## Adding custom dependencies
 
-<Markdown src="/snippets/pro-callout.mdx"/>
+<Markdown src="/snippets/pro-plan.mdx"/>
 
 To add packages that your custom code requires, update your `generators.yml`.
 
diff --git a/fern/products/sdks/overview/python/configuration.mdx b/fern/products/sdks/overview/python/configuration.mdx
@@ -63,6 +63,9 @@ When enabled, excludes type definitions from being exported in the package's `__
 </ParamField>
 
 <ParamField path="extra_dependencies" type="object" default="{}" required={false} toc={true}>
+
+  <Markdown src="/snippets/pro-plan.mdx"/>
+
   If you want to add custom dependencies to your generated SDK, you can specify them using this configuration. For example, to add a dependency on boto3, your config would look like:
   ```yaml
   config:
@@ -72,6 +75,9 @@ When enabled, excludes type definitions from being exported in the package's `__
 </ParamField>
 
 <ParamField path="extra_dev_dependencies" type="object" default="{}" required={false} toc={true}>
+
+<Markdown src="/snippets/pro-plan.mdx"/>
+
 Specify additional development dependencies to include in the generated SDK's setup configuration. These are dependencies used for development and testing but not required by end users.
 </ParamField>
 
diff --git a/fern/products/sdks/overview/python/custom-code.mdx b/fern/products/sdks/overview/python/custom-code.mdx
@@ -116,7 +116,7 @@ To get started adding custom code:
 
 ## Adding custom dependencies
 
-<Markdown src="/snippets/pro-callout.mdx"/>
+<Markdown src="/snippets/pro-plan.mdx"/>
 
 To add packages that your custom code requires, update your `generators.yml`.
 
diff --git a/fern/products/sdks/overview/typescript/configuration.mdx b/fern/products/sdks/overview/typescript/configuration.mdx
@@ -88,6 +88,9 @@ const bar: MyRootType.Foo.Bar = {};
 </ParamField>
 
 <ParamField path="extraDependencies" type="object" default="{}" toc={true}>
+
+<Markdown src="/snippets/pro-plan.mdx"/>
+
   Specify extra dependencies in the generated `package.json`. This is useful
 when you utilize [`.fernignore`](https://buildwithfern.com/learn/sdks/capabilities/custom-code) to
 supplement the generated client with custom code. 
@@ -102,6 +105,9 @@ config:
 </ParamField>
 
 <ParamField path="extraDevDependencies" type="object" default="{}" toc={true}>
+
+<Markdown src="/snippets/pro-plan.mdx"/>
+
   Specify extra dev dependencies in the generated `package.json`. 
 
 ```yaml
diff --git a/fern/products/sdks/overview/typescript/custom-code.mdx b/fern/products/sdks/overview/typescript/custom-code.mdx
@@ -108,7 +108,7 @@ To get started adding custom code:
 
 ## Custom dependencies
 
-<Markdown src="/snippets/pro-callout.mdx"/>
+<Markdown src="/snippets/pro-plan.mdx"/>
 
 To add packages that your custom code requires, update your `generators.yml`.
 
diff --git a/fern/snippets/enterprise-plan.mdx b/fern/snippets/enterprise-plan.mdx
@@ -0,0 +1,3 @@
+<Warning title="Enterprise feature">
+    This feature is available only for the [Enterprise plan](https://buildwithfern.com/pricing). To get started, reach out to support@buildwithfern.com.
+</Warning>
diff --git a/fern/snippets/pro-plan.mdx b/fern/snippets/pro-plan.mdx
