@eventcatalog/core 5.0.0-beta.9 → 5.0.0

package/dist/docs/federation/legacy-federation/01-installation.md

@@ -8,20 +8,16 @@ description: Installation of the EventCatalog Federation plugin
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PluginLicense from '@site/src/components/MDX/PluginLicense';
 import Beta from '@site/src/components/MDX/Beta';
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
 
-<EventCatalogEnterprise />
+:::warning Deprecated
 
-:::warning Legacy Federation
+The `@eventcatalog/generator-federation` generator is deprecated. Federation is now built into EventCatalog and runs with `eventcatalog federate`. See the [EventCatalog Federation docs](/docs/federation/overview) to get started.
 
-This page documents the legacy `@eventcatalog/generator-federation` implementation. For new projects, use the [current built-in EventCatalog Federation](/docs/federation/overview).
+This page documents the legacy generator for existing users.
 
 :::
 
-<PluginLicense url="#commercial-use" />
-
 The EventCatalog Federation plugin is designed for your [main catalog](/docs/federation/legacy-federation/configuration).
 
 This plugin will allow you to merge multiple EventCatalog instances into a single catalog.
@@ -114,62 +110,15 @@ generators: [
   ],
 ```
 
-### Configure license key
-
-The EventCatalog Federation plugin requires an EventCatalog Scale license key to work with EventCatalog.
-
-You can get a trial Scale license key from [EventCatalog Cloud](https://eventcatalog.cloud).
-
-You have a few options for setting the license key:
-
-1. [Setting license key in `.env` file (recommended)](#setting-license-key-in-env-file-recommended)
-2. [Setting license key in eventcatalog.config.js](#setting-license-key-in-eventcatalogconfigjs)
-
-#### 1. Setting license key in `.env` file (recommended) {#setting-license-key-in-env-file-recommended}
-
-<AddedIn version="2.35.4" />
-
-Create a `.env` file in the root of your project and add the following:
-
-```bash title=".env"
-EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
-```
-
-:::tip Using an Older API Key?
-
-If you already have an older Federation plugin key, you can still use it with the Federation-specific environment variable.
-
-```bash title=".env"
-EVENTCATALOG_LICENSE_KEY_FEDERATION=your-license-key
-```
-
-:::
-
-#### 2. Setting license key in eventcatalog.config.js {#setting-license-key-in-eventcatalogconfigjs}
-
-If you prefer, you can set the license key in the `eventcatalog.config.js` file
-using the `licenseKey` property in the EventCatalog Federation plugin.
-
-```js title="eventcatalog.config.js"
-export default {
-  generators: [
-    [
-      '@eventcatalog/generator-federation',
-      {
-        licenseKey: '[INSERT_YOUR_LICENSE_KEY]', // or process.env.EVENTCATALOG_SCALE_LICENSE_KEY
-      },
-    ],
-  ],
-};
-```
+### License
 
-#### White listing EventCatalog domains
+The EventCatalog Federation plugin is open source under the MIT License and doesn't need a license key.
 
-If you are behind a firewall you will need to white list the domain `https://api.eventcatalog.cloud` in your firewall. This is because the plugin needs to verify your license key.
+If your config still sets `licenseKey` or an `EVENTCATALOG_LICENSE_KEY_*` variable, you can remove it; it's ignored.
 
 ## Run the generator
 
-Once you have configured the plugin and license key you can run the generator.
+Once you have configured the plugin you can run the generator.
 
 ```sh
 npm run generate

package/dist/docs/federation/legacy-federation/02-plugin-configuration.md

@@ -7,20 +7,16 @@ title: Plugin Configuration
 description: Configuration of the EventCatalog Federation plugin
 ---
 
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
+:::warning Deprecated
 
-<EventCatalogEnterprise />
+The `@eventcatalog/generator-federation` generator is deprecated. Federation is now built into EventCatalog and runs with `eventcatalog federate`. See the [EventCatalog Federation docs](/docs/federation/overview) to get started.
 
-:::warning Legacy Federation
-
-This page documents the legacy `@eventcatalog/generator-federation` implementation. For new projects, use the [current built-in EventCatalog Federation](/docs/federation/overview).
+This page documents the legacy generator for existing users.
 
 :::
 
 API Configuration for the EventCatalog Federation plugin
 
-
-
 ## Overview
 
 The EventCatalog Federation plugin is configured in the `eventcatalog.config.js` file inside the `generators` array.
@@ -201,17 +197,3 @@ export default {
 
 You can view an example configuration in the [EventCatalog Federation plugin GitHub repository](https://github.com/event-catalog/generators/blob/main/examples/generator-federation/basic/central-catalog/eventcatalog.config.js).
 
-
-
-
-
-
-
-
-
-
-
-
-
-
-

package/dist/docs/federation/legacy-federation/03-examples.md

@@ -7,13 +7,11 @@ title: Examples
 description: Examples of using the Federation plugin
 ---
 
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
+:::warning Deprecated
 
-<EventCatalogEnterprise />
+The `@eventcatalog/generator-federation` generator is deprecated. Federation is now built into EventCatalog and runs with `eventcatalog federate`. See the [EventCatalog Federation docs](/docs/federation/overview) to get started.
 
-:::warning Legacy Federation
-
-This page documents the legacy `@eventcatalog/generator-federation` implementation. For new projects, use the [current built-in EventCatalog Federation](/docs/federation/overview).
+This page documents the legacy generator for existing users.
 
 :::
 

package/dist/docs/federation/legacy-federation/04-configuration.md

@@ -8,21 +8,18 @@ description: Configuring federation in your EventCatalog
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PluginLicense from '@site/src/components/MDX/PluginLicense';
 import Beta from '@site/src/components/MDX/Beta';
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
 
-<EventCatalogEnterprise />
+:::warning Deprecated
 
-:::warning Legacy Federation
+The `@eventcatalog/generator-federation` generator is deprecated. Federation is now built into EventCatalog and runs with `eventcatalog federate`. See the [EventCatalog Federation docs](/docs/federation/overview) to get started.
 
-This page documents the legacy `@eventcatalog/generator-federation` implementation. For new projects, use the [current built-in EventCatalog Federation](/docs/federation/overview).
+This page documents the legacy generator for existing users.
 
 :::
 
 <!-- <Beta /> -->
 <AddedIn version="2.18.0" />
-<PluginLicense url="/docs/federation/legacy-federation/introduction#commercial-use" />
 
 EventCatalog Federation is powered by the [EventCatalog Federation Generator](https://github.com/event-catalog/generators), this let's you define the repositories you want to merge into your main catalog.
 
@@ -172,8 +169,6 @@ If you want to learn more about the federation generator you can read the [Event
 
 ### Running the generator
 
-You will need an EventCatalog Scale license key to run the generator. You can get a free 30-day trial Scale license key from [EventCatalog Cloud](https://eventcatalog.cloud).
-
 Once you have configured the federation generator you can run the generator.
 
 Inside your main catalog run the following command:

package/dist/docs/federation/legacy-federation/05-setup-team-catalog.md

@@ -8,21 +8,18 @@ description: Configuring federation in your EventCatalog
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PluginLicense from '@site/src/components/MDX/PluginLicense';
 import Beta from '@site/src/components/MDX/Beta';
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
 
-<EventCatalogEnterprise />
+:::warning Deprecated
 
-:::warning Legacy Federation
+The `@eventcatalog/generator-federation` generator is deprecated. Federation is now built into EventCatalog and runs with `eventcatalog federate`. See the [EventCatalog Federation docs](/docs/federation/overview) to get started.
 
-This page documents the legacy `@eventcatalog/generator-federation` implementation. For new projects, use the [current built-in EventCatalog Federation](/docs/federation/overview).
+This page documents the legacy generator for existing users.
 
 :::
 
 <!-- <Beta /> -->
 <AddedIn version="2.18.0" />
-<PluginLicense url="/docs/federation/legacy-federation/introduction#commercial-use" />
 
 Multiple teams can own their own EventCatalog, this is useful if you have multiple teams that want to own their own EventCatalog / Documentation.
 

package/dist/docs/federation/reference/cli.md

@@ -5,10 +5,6 @@ title: Federation CLI reference
 description: Command, option, environment variable, and output reference for eventcatalog federate.
 ---
 
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
-
-<EventCatalogEnterprise />
-
 Run Federation from the central catalog directory:
 
 ```bash
@@ -20,11 +16,12 @@ The command loads `federation.sources` and `federation.rules` from `eventcatalog
 ## Requirements
 
 - A central EventCatalog project
-- An EventCatalog Enterprise offline license file
 - At least one configured source, unless you are cleaning previous output
 - Git for GitHub sources that do not publish an index
 - Network and repository access for GitHub sources
 
+Federation is free for organizations that [qualify for Free Use](/license-faq), using their free license key. Commercial customers need the [Enterprise plan](/pricing). Every organization can try it during its 60-day evaluation.
+
 ## Options
 
 | Option | Description | Default |
@@ -69,11 +66,8 @@ EVENTCATALOG_FEDERATION_LOCAL=true npx eventcatalog federate
 
 ## Environment variables
 
-Place the Enterprise `license.jwt` file in the central catalog root. You can commit it with the catalog or write it during CI/CD. If you store it elsewhere, set `EC_LICENSE` to its file path. Email [hello@eventcatalog.dev](mailto:hello@eventcatalog.dev?subject=EventCatalog%20Federation%20Trial) to request an offline trial key.
-
 | Variable | Description |
 | --- | --- |
-| `EC_LICENSE` | Optional path to the Enterprise offline license file. Defaults to `license.jwt` in the catalog root. |
 | `EVENTCATALOG_GITHUB_TOKEN` | Preferred GitHub token for private repositories and authenticated content requests. |
 | `GITHUB_TOKEN` | GitHub token fallback when `EVENTCATALOG_GITHUB_TOKEN` is not set. |
 

package/dist/docs/federation/reference/configuration.md

@@ -5,10 +5,6 @@ title: Federation configuration reference
 description: Reference for federation sources and rule levels in eventcatalog.config.js.
 ---
 
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
-
-<EventCatalogEnterprise />
-
 Configure Federation under the `federation` key in the central catalog's `eventcatalog.config.js`.
 
 ```js title="eventcatalog.config.js"

package/dist/docs/federation/reference/diagnostic-rules.md

@@ -5,10 +5,6 @@ title: Federation diagnostic rule reference
 description: Reference for every Federation rule, default level, trigger, output attributes, and resolution.
 ---
 
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
-
-<EventCatalogEnterprise />
-
 Federation diagnostics use stable rule IDs. Configure each rule as `off`, `warn`, or `error` under `federation.rules`.
 
 | Rule | Default | Summary |
@@ -159,7 +155,6 @@ Changing structural rules from `error` can allow ambiguous ownership or types in
 
 Some failures stop Federation directly and do not have configurable `federation/*` rule IDs. These include:
 
-- Missing or invalid license access
 - Duplicate configured source IDs
 - Unsupported source locators
 - GitHub authentication or network failures

package/dist/docs/federation/reference/generated-output.md

@@ -5,10 +5,6 @@ title: Federation generated output reference
 description: Reference for federated resources, shared components, public assets, the lockfile, and content cache.
 ---
 
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
-
-<EventCatalogEnterprise />
-
 A successful Federation run can create or update four locations in the central catalog:
 
 ```text

package/dist/docs/federation/reference/supported-content.md

@@ -5,10 +5,6 @@ title: Federation supported content
 description: Reference for resources, files, assets, and catalog-level content included by Federation.
 ---
 
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
-
-<EventCatalogEnterprise />
-
 Federation indexes and materializes normal EventCatalog resource content from every configured source.
 
 ## Supported resources

package/dist/docs/federation/reference/troubleshooting.md

@@ -5,10 +5,6 @@ title: Troubleshooting EventCatalog Federation
 description: Fix common source, ownership, relationship, asset, cache, and generated-output problems.
 ---
 
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
-
-<EventCatalogEnterprise />
-
 Run with verbose diagnostics before investigating a warning:
 
 ```bash
@@ -17,16 +13,6 @@ npx eventcatalog federate --verbose
 
 Errors always include details. Verbose mode adds the attributes for warnings.
 
-## Federation is not enabled
-
-If the command reports that Federation is an Enterprise feature:
-
-- Confirm the Enterprise `license.jwt` file is in the central catalog root
-- If the file is stored elsewhere, confirm `EC_LICENSE` points to it
-- Confirm the license has not expired
-- Email [hello@eventcatalog.dev](mailto:hello@eventcatalog.dev?subject=EventCatalog%20Federation%20Trial) to request or replace an offline trial key
-- Review [offline license validation](/docs/development/license-keys/license-validation#offline-validation)
-
 ## No sources are configured
 
 Add at least one entry to `federation.sources`:

package/dist/docs/plugins/02-generators.md

@@ -8,7 +8,7 @@ description: Understanding EventCatalog generators.
 ---
 EventCatalog generators are custom scripts executed before the build process begins.
 
-During the catalog build, your configured generators run dynamically, providing the opportunity to utilize open-source generators and plugins or develop your own custom solutions.
+During the catalog build, your configured generators run dynamically, providing the opportunity to use existing generators and plugins or develop your own custom solutions.
 
 ### Why use generators?
 

package/dist/docs/plugins/amazon-apigateway/00-intro.md

@@ -8,9 +8,6 @@ description: Getting started with Amazon EventBridge plugin
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PluginLicense from '@site/src/components/MDX/PluginLicense';
-
-<PluginLicense url="#commercial-use" />
 
 <!-- <iframe width="100%" height="415" src="https://www.youtube.com/embed/MeBuwAflwM4?si=rhio4gjfDPau4eqB" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> -->
 
@@ -44,32 +41,10 @@ This plugin will download OpenAPI specifications from your API Gateway and impor
 
 This will map your routes into commands, events and queries in your catalog and assign these to services and domains and teams in your organization.
 
-## Commercial and License
-
-This plugin requires an EventCatalog Scale license key to be used.
-
-You can get a 30-day trial Scale license key by going to [EventCatalog Cloud](https://eventcatalog.cloud).
-
-After the trial, you can continue using this plugin with EventCatalog Scale. 
-
-See [pricing](/pricing) for more information.
-
-_Have any questions? You can email us at `hello@eventcatalog.dev`._
-
-## License FAQ
-
-### What is the license key for?
-The EventCatalog Scale license key is required to use the Amazon API Gateway plugin with EventCatalog. It helps support ongoing development and maintenance of the plugin and project.
-
-### How do I get an EventCatalog Scale license key?
-You can obtain an EventCatalog Scale license key by visiting [EventCatalog Cloud](https://eventcatalog.cloud). Your organization can start with a 30-day trial.
-
-### Terms
-- **Trial Period**: 30-day free trial no credit card required
-- **Support**: Discord community support (extra for priority support)
+### License
 
-After your trial period ends, you can continue with EventCatalog Scale through [EventCatalog Cloud](https://eventcatalog.cloud).
+This plugin is open source under the MIT License and doesn't need a license key.
 
 ## Issues
 
-If you have any problems or feature requests please feel free to raise them on GitHub. https://github.com/event-catalog/generators or join our [Discord community](https://eventcatalog.dev/discord) to chat with the team and other users.
+If you have any problems or feature requests please feel free to raise them on GitHub. https://github.com/event-catalog/generators or join our [Discord community](https://eventcatalog.dev/discord) to chat with the team and other users.

package/dist/docs/plugins/amazon-apigateway/01-installation.md

@@ -8,12 +8,9 @@ description: Installation instructions for the Amazon API Gateway plugin
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PluginLicense from '@site/src/components/MDX/PluginLicense';
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-<PluginLicense url="#commercial-use" />
-
 This plugin requires the OpenAPI and Amazon API Gateway plugins to be installed.
 
 <!-- <iframe width="100%" height="415" src="https://www.youtube.com/embed/MeBuwAflwM4?si=rhio4gjfDPau4eqB" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> -->
@@ -123,63 +120,15 @@ export default {
 };
 ```
 
-### Configure license key
-
-The API Gateway and OpenAPI plugin both require a license key to work with EventCatalog.
-
-You can get a trial Scale license key from [EventCatalog Cloud](https://eventcatalog.cloud).
-
-You have a few options for setting the license key:
-
-1. [Setting license key in `.env` file (recommended)](#setting-license-key-in-env-file-recommended)
-2. [Setting license key in eventcatalog.config.js](#setting-license-key-in-eventcatalogconfigjs)
-
-#### 1. Setting license key in `.env` file (recommended) {#setting-license-key-in-env-file-recommended}
-
-<AddedIn version="2.35.4" />
-
-Create a `.env` file in the root of your project and add the following:
-
-```bash title=".env"
-EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
-```
-
-:::tip Using an Older API Key?
-
-If you already have older Amazon API Gateway and OpenAPI plugin keys, you can still use them with the plugin-specific environment variables.
-
-```bash title=".env"
-EVENTCATALOG_LICENSE_KEY_AMAZON_APIGATEWAY=your-license-key
-EVENTCATALOG_LICENSE_KEY_OPENAPI=your-license-key
-```
-
-:::
+### Licensing
 
-#### 2. Setting license key in eventcatalog.config.js {#setting-license-key-in-eventcatalogconfigjs}
+The API Gateway and OpenAPI plugins are open source under the MIT License and don't need a license key.
 
-If you prefer, you can set the license key in the `eventcatalog.config.js` file
-using the `licenseKey` property in both the API Gateway and OpenAPI plugin.
-
-```js title="eventcatalog.config.js"
-export default {
-  generators: [
-    [
-      '@eventcatalog/generator-eventbridge',
-      {
-        licenseKey: '[INSERT_YOUR_LICENSE_KEY]', // or process.env.EVENTCATALOG_SCALE_LICENSE_KEY
-      },
-    ],
-  ],
-};
-```
-
-#### White listing EventCatalog domains
-
-If you are behind a firewall you will need to white list the domain `https://api.eventcatalog.cloud` in your firewall. This is because the plugin needs to verify your license key.
+If your config still sets `licenseKey` or an `EVENTCATALOG_LICENSE_KEY_*` variable, you can remove it; it's ignored.
 
 ## Run the generator
 
-Once you have configured the plugin and license key you can run the generator.
+Once you have configured the plugin you can run the generator.
 
 ```sh
 npm run generate
@@ -193,4 +142,3 @@ Run your catalog locally to see the changes.
 npm run dev
 ```
 
-

package/dist/docs/plugins/amazon-apigateway/02-plugin-configuration.md

@@ -7,11 +7,7 @@ title: Plugin Configuration
 description: Configuration of the Amazon API Gateway plugin
 ---
 
-This plugin requires an EventCatalog Scale license key.
-
-You can get a 30-day free trial license key by signing up to [EventCatalog Cloud](https://eventcatalog.dev/cloud).
-
-Once you have your license key you can set the `EVENTCATALOG_SCALE_LICENSE_KEY` environment variable.
+This plugin is open source under the MIT License and doesn't need a license key.
 
 ## Overview
 
@@ -23,7 +19,6 @@ The Amazon API Gateway plugin is configured in the `eventcatalog.config.js` file
 |--------|------|----------|---------|-------------|
 | `output` | string | No | `amazon-apigateway-specs` | The output directory for the OpenAPI specifications (used by the OpenAPI Generator plugin) |
 | `credentials` | [AwsCredentialIdentity](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-smithy-types/Interface/AwsCredentialIdentity/) | No | - | AWS credentials to use for the import on AWS. If this is not provided it will default to the credentials on the machine. |
-| `licenseKey` | string | No | - | You can either pass the license key directly or set the `EVENTCATALOG_SCALE_LICENSE_KEY` environment variable. |
 | `apis` | API[] | Yes | - | Array of API configurations |
 
 ## API Configuration

package/dist/docs/plugins/apicurio/00-intro.md

@@ -8,17 +8,10 @@ title: Introduction
 description: Getting started with Apicurio Registry plugin
 ---
 
-
 import AddedIn from '@site/src/components/MDX/AddedIn';
 
-import PluginLicense from '@site/src/components/MDX/PluginLicense';
-
-<PluginLicense url="#commercial-use" />
-
-
 <iframe width="100%" height="415" src="https://www.youtube.com/embed/0DmGWa0sr6w?si=KsE4D9C_yN7998Vo" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
 
-
 ---
 
 Many teams building event-driven architectures use schema registries to manage their message schemas and API specifications.
@@ -67,36 +60,14 @@ EventCatalog supports [generators](/docs/plugins/generators). These are scripts
 
 The EventCatalog Apicurio Registry plugin is a generator. It will import your schemas and specifications from your Apicurio Registry into EventCatalog.
 
-## Commercial and License
-
-This plugin requires an EventCatalog Scale license key to be used.
-
-You can get a 30-day trial Scale license key by going to [EventCatalog Cloud](https://eventcatalog.cloud).
+### License
 
-After the trial, you can continue using this plugin with EventCatalog Scale.
-
-See [pricing](/pricing) for more information.
-
-_Have any questions? You can email us at `hello@eventcatalog.dev`._
+This plugin is open source under the MIT License and doesn't need a license key.
 
 ## Need a demo?
 
 If you would like a demo of the plugin, please feel free to reach out to us and book a time to chat at hello@eventcatalog.dev.
 
-## License FAQ
-
-### What is the license key for?
-The EventCatalog Scale license key is required to use the Apicurio Registry plugin with EventCatalog. It helps support ongoing development and maintenance of the plugin and project.
-
-### How do I get an EventCatalog Scale license key?
-You can obtain an EventCatalog Scale license key by visiting [EventCatalog Cloud](https://eventcatalog.cloud). New users can start with a 30-day free trial.
-
-### Terms
-- **Trial Period**: 30-day free trial no credit card required
-- **Support**: Discord community support (extra for priority support)
-
-After your trial period ends, you can continue with EventCatalog Scale through [EventCatalog Cloud](https://eventcatalog.cloud).
-
 ## Any questions or need help?
 
 If you have questions or need help, you can join our [Discord community](https://eventcatalog.dev/discord) or raise an issue on [GitHub](https://github.com/event-catalog/eventcatalog/issues).

package/dist/docs/plugins/apicurio/01-installation.md

@@ -8,13 +8,10 @@ description: Installation of the EventCatalog Apicurio Registry plugin
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PluginLicense from '@site/src/components/MDX/PluginLicense';
 import Beta from '@site/src/components/MDX/Beta';
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-<PluginLicense url="#commercial-use" />
-
 The Apicurio Registry plugin is used to generate a catalog from an Apicurio Registry and import your schemas and specifications into EventCatalog.
 
 You can map your schemas from your Apicurio Registry to events, commands, or queries in your catalog, and assign these to services and domains.
@@ -55,7 +52,6 @@ Add the plugin to the `generators` array.
 
   You can also create services and assign schemas to them, along with domains. [(see examples)](/docs/plugins/apicurio/plugin-configuration#example-configurations).
 
-
     ```js title="eventcatalog.config.js"
     // ...
     generators: [
@@ -115,35 +111,15 @@ We create an `orders` domain and an `Orders Service` that sends and receives mes
 
 ### Configure API keys
 
-The EventCatalog Apicurio Registry plugin requires API keys in your environment variables.
+The EventCatalog Apicurio Registry plugin is open source under the MIT License and doesn't need a license key. If your config still sets `licenseKey` or an `EVENTCATALOG_LICENSE_KEY_*` variable, you can remove it; it's ignored.
 
-1. An EventCatalog Scale license key for the Apicurio Registry plugin (30-day trial, at [EventCatalog Cloud](https://eventcatalog.cloud))
-2. Apicurio Registry access token (optional - only if your registry requires authentication)
-
-Create a `.env` file in the root, and add your keys to the project.
+If your Apicurio Registry requires authentication, create a `.env` file in the root and add your access token to the project.
 
 ```bash title=".env"
-# EventCatalog license key
-EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
-
 # Apicurio Registry Bearer Token (optional - only if your registry requires authentication)
 APICURIO_ACCESS_TOKEN=your-access-token-here
 ```
 
-:::tip Using an Older API Key?
-
-If you already have an older Apicurio Registry plugin key, you can still use it with the plugin-specific environment variable.
-
-```bash title=".env"
-EVENTCATALOG_LICENSE_KEY_APICURIO_SCHEMA_REGISTRY=your-license-key
-```
-
-:::
-
-#### White listing EventCatalog domains
-
-If you are behind a firewall you will need to white list the domain `https://api.eventcatalog.cloud` in your firewall. This is because the plugin needs to verify your license key.
-
 #### Run the plugin
 
 Run the plugin to import your schemas into EventCatalog.

package/dist/docs/plugins/apicurio/02-plugin-configuration.md

@@ -73,12 +73,10 @@ You can attach OpenAPI or AsyncAPI specifications stored in your Apicurio Regist
 
 You can attach OpenAPI or AsyncAPI specifications from your Apicurio Registry to services. These specifications can optionally be processed by their respective EventCatalog plugins to generate additional documentation.
 
-:::info Plugin Licenses Required
-The OpenAPI and AsyncAPI generators require an EventCatalog Scale license key. To use them with the Apicurio plugin, you'll need to:
-- Install the respective plugins: `npm install @eventcatalog/generator-openapi @eventcatalog/generator-asyncapi`
-- Obtain an EventCatalog Scale license key from [EventCatalog Cloud](https://eventcatalog.cloud) (30-day free trial available)
-- Configure the license key in your `.env` file:
-  - `EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key`
+:::info Plugin setup
+To use the OpenAPI and AsyncAPI generators with the Apicurio plugin, you'll need to install the respective plugins: `npm install @eventcatalog/generator-openapi @eventcatalog/generator-asyncapi`
+
+Both plugins are open source under the MIT License and don't need a license key.
 
 Learn more: [OpenAPI Plugin Docs](/docs/plugins/openapi/intro) | [AsyncAPI Plugin Docs](/docs/plugins/asyncapi/intro)
 :::
@@ -528,16 +526,10 @@ In this example we attach OpenAPI and AsyncAPI specifications to a service and u
 ```
 
 :::tip
-When using nested generators, make sure to:
-1. Install the respective plugins:
+When using nested generators, make sure to install the respective plugins:
 ```bash
 npm install @eventcatalog/generator-openapi @eventcatalog/generator-asyncapi
 ```
-2. Obtain an EventCatalog Scale license key from [EventCatalog Cloud](https://eventcatalog.cloud) (30-day free trial available)
-3. Add the license key to your `.env` file:
-```bash
-EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
-```
 
 See [OpenAPI Plugin Docs](/docs/plugins/openapi/intro) | [AsyncAPI Plugin Docs](/docs/plugins/asyncapi/intro) for more information.
 :::