@eventcatalog/core 5.0.0-beta.8 → 5.0.0

package/dist/docs/federation/01-first-federation.md

@@ -6,10 +6,6 @@ description: Create two local EventCatalog projects and combine them into one or
 slug: /federation/first-federation
 ---
 
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
-
-<EventCatalogEnterprise />
-
 This tutorial takes you through the first successful Federation workflow:
 
 1. Create a team catalog
@@ -52,9 +48,14 @@ Before you start, make sure you have:
 
 - [Node.js 22 or later](https://nodejs.org/en/download/)
 - Git installed
-- An EventCatalog Enterprise offline license. Email [hello@eventcatalog.dev](mailto:hello@eventcatalog.dev?subject=EventCatalog%20Federation%20Trial) to request a trial key.
 - A terminal and text editor
 
+:::info License
+
+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.
+
+:::
+
 Check Node and Git with:
 
 ```bash
@@ -91,19 +92,6 @@ federation-tutorial/
 └── organization-catalog/
 ```
 
-## Add your Enterprise license
-
-Federation uses an offline Enterprise license. Save the `license.jwt` file we send you in the root of the organization catalog:
-
-```text
-organization-catalog/
-├── license.jwt
-├── eventcatalog.config.js
-└── package.json
-```
-
-To try Federation, email [hello@eventcatalog.dev](mailto:hello@eventcatalog.dev?subject=EventCatalog%20Federation%20Trial) and ask for an offline trial key. You can commit `license.jwt` with the central catalog so it is available locally and in CI/CD. If your organization prefers not to commit it, provide the file during your CI/CD job instead.
-
 ## Configure the local source
 
 Open `organization-catalog/eventcatalog.config.js` and add `federation.sources` to the exported configuration:

package/dist/docs/federation/explanation/how-it-works.md

@@ -5,10 +5,6 @@ title: How EventCatalog Federation works
 description: Understand how EventCatalog indexes, resolves, and materializes several catalogs into one organization view.
 ---
 
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
-
-<EventCatalogEnterprise />
-
 EventCatalog Federation is a build-time composition process.
 
 It reads independently owned catalogs, converts them into a common index, validates the combined graph, and writes generated catalog files that the normal EventCatalog application can render.

package/dist/docs/federation/explanation/lockfile-and-cache.md

@@ -5,10 +5,6 @@ title: Federation lockfile and content cache
 description: Understand what eventcatalog.lock records, what it does not pin, and how the Federation cache works.
 ---
 
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
-
-<EventCatalogEnterprise />
-
 Federation writes two kinds of local state:
 
 - `eventcatalog.lock` records the source state and managed public files from a completed run.

package/dist/docs/federation/explanation/mvp-status-and-feedback.md

@@ -5,10 +5,6 @@ title: Federation MVP status and feedback
 description: Understand the current Federation release boundaries and how to share useful feedback.
 ---
 
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
-
-<EventCatalogEnterprise />
-
 EventCatalog Federation is being introduced as an initial working release for feedback.
 
 The core workflow is ready to combine real catalogs, validate ownership, and build an organization-wide view. The first release deliberately keeps source configuration and execution explicit while EventCatalog learns how teams want to operate Federation.

package/dist/docs/federation/explanation/ownership-and-references.md

@@ -5,10 +5,6 @@ title: Ownership and cross-catalog references
 description: Understand how Federation assigns ownership and resolves relationships across catalog boundaries.
 ---
 
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
-
-<EventCatalogEnterprise />
-
 Federation separates **owning a resource** from **referring to a resource**.
 
 A catalog owns a resource when it contains the resource documentation. Other catalogs can use normal EventCatalog relationship pointers to refer to that ID without copying its definition.

package/dist/docs/federation/how-to/configure-github-sources.md

@@ -5,10 +5,6 @@ title: Configure GitHub federation sources
 description: Add public or private GitHub-hosted EventCatalog projects to a central catalog.
 ---
 
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
-
-<EventCatalogEnterprise />
-
 Use this guide when the catalogs you want to federate are stored in GitHub repositories.
 
 ## Prerequisites
@@ -18,9 +14,14 @@ You need:
 - A central EventCatalog project
 - One or more EventCatalog projects in GitHub
 - Git installed on the machine running Federation
-- An EventCatalog Enterprise offline license. Email [hello@eventcatalog.dev](mailto:hello@eventcatalog.dev?subject=EventCatalog%20Federation%20Trial) to request a trial key.
 - A GitHub token with read access when a repository is private
 
+:::info License
+
+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.
+
+:::
+
 ## Add a catalog at the repository root
 
 Add the source to `federation.sources` in the central `eventcatalog.config.js`:

package/dist/docs/federation/how-to/configure-validation-rules.md

@@ -5,10 +5,6 @@ title: Configure Federation validation rules
 description: Change federation diagnostics to off, warn, or error for your organization.
 ---
 
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
-
-<EventCatalogEnterprise />
-
 Federation rules work like lint rules. Every supported rule has one of three levels:
 
 | Level | Behavior |

package/dist/docs/federation/how-to/run-in-ci.md

@@ -5,10 +5,6 @@ title: Run EventCatalog Federation in CI
 description: Fetch and validate federated catalogs before building the organization catalog in CI.
 ---
 
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
-
-<EventCatalogEnterprise />
-
 Run Federation before the normal EventCatalog build so the generated organization view exists when EventCatalog renders the site.
 
 ## Add explicit scripts
@@ -27,17 +23,14 @@ Add separate and combined scripts to the central catalog:
 
 Keeping `federate` and `build` separate makes it clear which stage failed. The combined script is useful for deployment platforms that accept one build command.
 
-## Provide your Enterprise license and repository tokens
-
-Federation requires an EventCatalog Enterprise offline license. Email [hello@eventcatalog.dev](mailto:hello@eventcatalog.dev?subject=EventCatalog%20Federation%20Trial) to request a trial key.
+## Provide repository tokens
 
-The simplest option is to commit `license.jwt` in the central catalog root. Federation will find it automatically when CI runs. If your organization prefers not to commit the file, store its contents in your CI provider and write `license.jwt` during the job. Set `EC_LICENSE` only when you write the file somewhere other than the catalog root.
+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.
 
 Provide these environment variables when needed:
 
 | Variable | When it is needed |
 | --- | --- |
-| `EC_LICENSE` | Optional path to the Enterprise offline license file when it is not stored at `./license.jwt` |
 | `EVENTCATALOG_GITHUB_TOKEN` | Recommended for private GitHub sources |
 | `GITHUB_TOKEN` | Used as a fallback when `EVENTCATALOG_GITHUB_TOKEN` is not set |
 

package/dist/docs/federation/how-to/share-assets-and-components.md

@@ -5,10 +5,6 @@ title: Share public assets and custom components through Federation
 description: Include source catalog images, files, and custom components in the organization catalog.
 ---
 
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
-
-<EventCatalogEnterprise />
-
 Federation includes top-level `public/` assets and `components/` custom components from source catalogs.
 
 Use this guide when federated resource pages depend on images, downloadable files, or custom components owned by the source catalog.

package/dist/docs/federation/how-to/use-local-sources.md

@@ -5,10 +5,6 @@ title: Use local catalogs during development
 description: Run the federation pipeline against catalogs on your local filesystem.
 ---
 
-import EventCatalogEnterprise from '@site/src/components/MDX/EventCatalogEnterprise';
-
-<EventCatalogEnterprise />
-
 Use filesystem sources to test cross-catalog relationships, ownership conflicts, rules, assets, and custom components before pushing source changes to GitHub.
 
 ## Configure a filesystem source

package/dist/docs/federation/legacy-federation/00-introduction.md

@@ -8,21 +8,18 @@ description: Merge multiple EventCatalog instances into a single catalog
 ---
 
 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="#commercial-use" />
 
 <iframe width="100%" height="415" src="https://www.youtube.com/embed/KnTQkrt-7cc?si=RjEasqw_KJ6AN4cr" 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>
 
@@ -30,7 +27,6 @@ This page documents the legacy `@eventcatalog/generator-federation` implementati
 
 **EventCatalog Federation** is a feature that allows you to merge multiple EventCatalog instances into a single catalog. 
 
-
 This is useful if you:
 
 - Have **multiple teams** that want to own there own EventCatalog / Documentation
@@ -52,8 +48,7 @@ EventCatalog Federation is powered by the [EventCatalog Federation Generator](ht
 5. You use the federation generator to merge your teams catalogs into the main catalog
 6. You setup CI/CD to keep your main catalog up to date with your teams catalogs (or just rebuild every X time)
 
-To use the federation generator you will need an EventCatalog Scale license key from [EventCatalog Cloud](https://eventcatalog.cloud).
-You can get a free 30-day trial Scale license key for the plugin.
+The federation generator is open source under the MIT License and doesn't need a license key.
 
 You can read more documentation:
 
@@ -62,17 +57,4 @@ You can read more documentation:
 - [Configuring your team catalogs](/docs/federation/legacy-federation/setup-team-catalog)
     - This is the documentation for how to setup your team catalogs
 
-## Commercial Use
-
-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`._
-
-
-<a href="https://eventcatalog.cloud" target="_blank" className="bg-purple-500 hover:bg-purple-100 cursor-pointer hover:text-white !hover:underline px-2 py-1 rounded-md text-white ">Login to EventCatalog Dashboard</a>

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.