@eventcatalog/core 5.0.0-beta.8 → 5.0.0

package/dist/docs/plugins/azure-schema-registry/01-installation.md

@@ -8,13 +8,10 @@ description: Installation of the EventCatalog Azure Schema 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" />
-
 Run the command below to install the EventCatalog Azure Schema Registry plugin.
 
 :::tip "Don't have an EventCatalog project yet?"
@@ -25,12 +22,6 @@ If you don't have an EventCatalog project yet, you can follow the instructions i
 npm i @eventcatalog/generator-azure-schema-registry
 ```
 
-:::info License Key
-The EventCatalog Azure Schema Registry 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).
-:::
-
 ## Configuration
 
 To use the plugin you need to configure it in your `eventcatalog.config.js` file.
@@ -199,12 +190,11 @@ generators: [
 
 The EventCatalog Azure Schema Registry plugin uses Azure's REST API with Bearer token authentication. You need to set the `AZURE_SCHEMA_REGISTRY_TOKEN` environment variable with your Azure access token.
 
-### Configure Azure Schema Registry License Key
+### Licensing
 
-The EventCatalog Azure Schema Registry 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).
+The EventCatalog Azure Schema 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.
 
 ---
 
@@ -285,23 +275,10 @@ az account get-access-token --resource https://eventhubs.azure.net --query acces
 Create or update your `.env` file in your EventCatalog project root:
 
 ```bash title=".env"
-# EventCatalog license key
-EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
-
 # Azure Schema Registry access token (paste the token from step 1)
 AZURE_SCHEMA_REGISTRY_TOKEN=eyJ0eXAiOiJKV1QiLCJhbGciOi...
 ```
 
-:::tip Using an Older API Key?
-
-If you already have an older Azure Schema Registry plugin key, you can still use it with the plugin-specific environment variable.
-
-```bash title=".env"
-EVENTCATALOG_LICENSE_KEY_AZURE_SCHEMA_REGISTRY=your-license-key
-```
-
-:::
-
 **Step 3: Run the Generator**
 
 ```bash
@@ -384,11 +361,7 @@ az role assignment create \
   --scope /subscriptions/{subscription-id}/resourceGroups/{resource-group}/providers/Microsoft.EventHub/namespaces/{namespace-name}
 ```
 
-## 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
 
 Run the plugin to import your schemas into EventCatalog.
 
@@ -398,7 +371,7 @@ _This command will run the generators in your eventcatalog.config.js file._
 npm run generate
 ```
 
-### View your catalog
+## View your catalog
 
 Run your catalog locally to see the changes
 
@@ -406,7 +379,7 @@ Run your catalog locally to see the changes
 npm run dev
 ```
 
-### Build your catalog for production
+## Build your catalog for production
 
 ```bash
 npm run build

package/dist/docs/plugins/azure-schema-registry/02-plugin-configuration.md

@@ -20,9 +20,6 @@ The plugin uses Azure's REST API with Bearer token authentication. You must set
 <summary>Example .env file</summary>
 
 ```bash
-# EventCatalog license key
-export EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
-
 # Azure Schema Registry access token
 export AZURE_SCHEMA_REGISTRY_TOKEN=your-azure-access-token
 ```
@@ -85,9 +82,7 @@ You can define and assign domains to organize your services.
 
 ### License
 
-| Option | Type | Default | Description |
-|--------|------|---------|-------------|
-| `licenseKey` | `string` | From env var | EventCatalog Scale license key. Can also be set via the `EVENTCATALOG_SCALE_LICENSE_KEY` environment variable. |
+This 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.
 
 ## Example Configurations
 
@@ -360,14 +355,6 @@ If the plugin can't find a schema:
 2. Check that your authenticated user/identity has read permissions on the schema registry
 3. Ensure the schema exists in the specified schema group
 
-### License Key Issues
-
-If you have problems with your license key:
-
-1. Ensure `https://api.eventcatalog.cloud` is not blocked by your firewall
-2. Verify your license key is correctly set in the `.env` file or passed via configuration
-3. Check your license hasn't expired at [EventCatalog Cloud](https://eventcatalog.cloud)
-
 ## Need Help?
 
 - [GitHub Issues](https://github.com/event-catalog/eventcatalog/issues)

package/dist/docs/plugins/azure-schema-registry/04-examples.md

@@ -106,7 +106,6 @@ Each example includes:
 - Azure CLI installed ([Install guide](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli))
 - Azure account with Event Hubs namespace
 - Azure Schema Registry with sample schemas
-- EventCatalog license key ([30-day trial available](https://eventcatalog.cloud))
 - Appropriate Azure permissions (`Azure Event Hubs Data Receiver` role)
 
 ### Quick Start
@@ -123,7 +122,6 @@ npm install
 
 # Copy and configure environment variables
 cp .env.example .env
-# Edit .env with your EventCatalog license key
 
 # Authenticate with Azure
 az login

package/dist/docs/plugins/backstage/00-overview.md

@@ -9,10 +9,6 @@ keywords:
   - integration
 ---
 
-import PluginLicense from '@site/src/components/MDX/PluginLicense';
-
-<PluginLicense url="#licensing" />
-
 The EventCatalog Backstage plugin embeds EventCatalog views in Backstage entity pages. Developers can explore architecture documentation without leaving the software catalog they use for ownership, APIs, dependencies, and operations.
 
 ![EventCatalog embedded in a Backstage entity page](/img/integrations/backstage/backstage-eventcatalog.png)
@@ -48,6 +44,4 @@ Read [How EventCatalog embeds work](/docs/plugins/backstage/how-embeds-work) for
 
 ## Licensing
 
-The plugin requires an EventCatalog Scale license for commercial use. You can start a 30-day trial in [EventCatalog Cloud](https://eventcatalog.cloud) and follow [Getting a license key for integrations](/docs/development/license-keys/integrations).
-
-For license terms, see the [plugin repository](https://github.com/event-catalog/backstage-plugin-eventcatalog).
+The Backstage plugin is open source under the MIT License and doesn't need a license key. If you previously set a license key for the plugin, you can remove it because it's ignored.

package/dist/docs/plugins/backstage/01-get-started.md

@@ -15,19 +15,10 @@ You will need:
 
 - a Backstage app with a software catalog entity page
 - an EventCatalog instance that the user's browser can reach
-- an EventCatalog Scale license for commercial use
 
-## 1. Enable the integration in EventCatalog
+The plugin is open source under the MIT License and doesn't need a license key.
 
-Add your Scale license key to the `.env` file in the EventCatalog project:
-
-```bash title=".env"
-EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
-```
-
-Build and deploy EventCatalog with this environment variable. For license setup and legacy keys, see [Getting a license key for integrations](/docs/development/license-keys/integrations).
-
-## 2. Install the Backstage plugin
+## 1. Install the Backstage plugin
 
 From the root of your Backstage app, install the frontend plugin:
 
@@ -35,7 +26,7 @@ From the root of your Backstage app, install the frontend plugin:
 yarn add @eventcatalog/backstage-plugin-eventcatalog
 ```
 
-## 3. Configure the EventCatalog URL
+## 2. Configure the EventCatalog URL
 
 Add the public base URL of your EventCatalog instance to `app-config.yaml`:
 
@@ -46,7 +37,7 @@ eventcatalog:
 
 Do not add a trailing view path such as `/docs` or `/visualiser`. The plugin builds each embed URL from this base URL.
 
-## 4. Map a Backstage entity
+## 3. Map a Backstage entity
 
 Add EventCatalog annotations to a Backstage catalog entity. This example maps a Backstage component to version `1.0.0` of the `order-service` service in EventCatalog:
 
@@ -68,7 +59,7 @@ spec:
 
 The annotation values must match the resource ID, version, and collection in EventCatalog.
 
-## 5. Add an EventCatalog tab
+## 4. Add an EventCatalog tab
 
 Open the file that defines your catalog entity page, commonly `packages/app/src/components/catalog/EntityPage.tsx`.
 
@@ -86,7 +77,7 @@ Add a route inside the `EntityLayout` used for your service entities:
 </EntityLayout.Route>
 ```
 
-## 6. Check the result
+## 5. Check the result
 
 Start Backstage and open the mapped service. Select **EventCatalog: Docs**.
 

package/dist/docs/plugins/backstage/06-configuration.md

@@ -74,12 +74,6 @@ Component props override annotations. For example, this always displays the `ord
 
 `type` is an alias for `collection` and accepts singular or plural values. Known singular resource types are converted to their plural collection, so `type="service"` resolves to `services`.
 
-## EventCatalog license configuration
+## License
 
-For commercial use, set the Scale license key in the EventCatalog deployment rather than the Backstage app:
-
-```bash title=".env"
-EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
-```
-
-Existing Backstage-specific keys can continue to use `EVENTCATALOG_LICENSE_KEY_BACKSTAGE`, but new deployments should use `EVENTCATALOG_SCALE_LICENSE_KEY`. See [Getting a license key for integrations](/docs/development/license-keys/integrations).
+The Backstage plugin is open source under the MIT License and doesn't need a license key. Any license key setting you used for the plugin before, such as `EVENTCATALOG_LICENSE_KEY_BACKSTAGE`, is ignored and can be removed.

package/dist/docs/plugins/confluent-schema-registry/00-intro.md

@@ -7,11 +7,6 @@ title: Introduction
 description: Getting started with AsyncAPI plugin
 ---
 
-
-<!-- import PluginLicense from '@site/src/components/MDX/PluginLicense'; -->
-
-<!-- <PluginLicense url="#commercial-use" /> -->
-
 <iframe width="100%" height="515" src="https://www.youtube.com/embed/NMZKnPKx-L0?si=og1Nvnr3FfPfAqn4" 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>
 
 ---
@@ -59,32 +54,10 @@ EventCatalog supports [generators](/docs/plugins/generators). These are scripts
 
 The EventCatalog Confluent Schema Registry plugin is a generator. It will import your schemas from your Confluent Schema 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).
-
-After the trial, you can continue using this plugin with EventCatalog Scale.
+### License
 
-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 Confluent Schema 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).

package/dist/docs/plugins/confluent-schema-registry/01-installation.md

@@ -8,13 +8,10 @@ description: Installation of the EventCatalog Confluent Schema 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 Confluent Schema Registry plugin is used to generate a catalog from a Confluent Schema Registry and import your schemas into EventCatalog.
 
 You can map your schemas from your Confluent Schema Registry to commands, events in your catalog, and assign these to services and domains.
@@ -53,7 +50,6 @@ Add the plugin to the `generators` array.
 
   You can also create topics, and assign schemas to producers/consumers and domains. [(see examples)](/docs/plugins/confluent-schema-registry/plugin-configuration#example-configurations).
 
-
   
     ```js title="eventcatalog.config.js"
     // ...
@@ -167,36 +163,18 @@ In this example we configure the plugin twice, the first time we import and crea
 
 ### Configure API keys
 
-The EventCatalog Confluent Schema Registry plugin requires API keys in your environment variables.
+The EventCatalog Confluent Schema 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 Confluent Schema Registry plugin (30-day trial, at [EventCatalog Cloud](https://eventcatalog.cloud))
-2. Confluent Schema Registry API keys (found in the [Confluent Cloud](https://confluent.cloud) console)
+The plugin needs your Confluent Schema Registry API keys (found in the [Confluent Cloud](https://confluent.cloud) console) in your environment variables.
 
 Create a `.env` file in the root, and add your keys to the project.
 
 ```bash title=".env"
-# EventCatalog license key
-EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
-
 # Confluent Schema Registry API Keys
 CONFLUENT_SCHEMA_REGISTRY_KEY=your-confluent-schema-registry-key
 CONFLUENT_SCHEMA_REGISTRY_SECRET=your-confluent-schema-registry-key-secret
 ```
 
-:::tip Using an Older API Key?
-
-If you already have an older Confluent Schema Registry plugin key, you can still use it with the plugin-specific environment variable.
-
-```bash title=".env"
-EVENTCATALOG_LICENSE_KEY_CONFLUENT_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.
@@ -221,8 +199,6 @@ npm run dev
 npm run build
 ```
 
-
-
 ## Any questions or need help?
 
 If you get stuck, find an issue or need help, please raise an issue on [GitHub](https://github.com/event-catalog/eventcatalog/issues) or join our [Discord community](https://eventcatalog.dev/discord).

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

@@ -8,10 +8,8 @@ description: Getting started with Amazon EventBridge plugin
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PluginLicense from '@site/src/components/MDX/PluginLicense';
 
 <AddedIn version="2.6.0"/>
-<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>
 
@@ -29,7 +27,6 @@ Although EventBridge offers managed schema solutions, [there is a still an issue
 
 Using the EventCatalog EventBridge generator you can automate and generate your EventCatalog. Enable your teams to quickly find events from EventBridge, what services they belong too and how to start consuming them.
 
-
 ### Core Features
 
 The EventCatalog Amazon EventBridge plugin can provide you with many features:
@@ -52,4 +49,3 @@ EventCatalog supports [generators](/docs/plugins/generators). These are scripts
 The EventCatalog EventBridge plugin let's you map your events into domains and services. You can use [custom filters (prefix, suffix, detailType and source)](/docs/plugins/eventbridge/features#using-filters-to-map-events-to-your-services) to map which events you want your service to produce and consume.
 
 You can also use the EventCatalog plugin to map ALL events from your registry into your system and not map them into services if you wish to have a direct import.
-

package/dist/docs/plugins/eventbridge/00a-installation.md

@@ -9,7 +9,6 @@ id: installation
 ---
 
 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';
 
@@ -40,7 +39,6 @@ npx @eventcatalog/create-eventcatalog@latest my-catalog --template eventbridge
   </TabItem>
 </Tabs>
 
-
 #### Configuration
 
 Configure the plugin in your `eventcatalog.config.js` file.
@@ -109,7 +107,6 @@ generators: [
         // "myapp.orders" will be assigned to the inventory service. The inventory service will publish these events.
         { id: 'Inventory Service', version: '1.0.0', sends: [{ source: "myapp.orders", eventBusName: 'orders'}], receives:[{ detailType: "UserCheckedOut", eventBusName: 'inventory'}] },
 
-
         // This service sends events that match the SchemaName prefixing myapp, and will receive events that end with Payment
         // this also does not map any event buses to your events
         { id: 'Payment Service', version: '1.0.0', sends: [{ prefix: "myapp"}], receives:[{ suffix: "Payment" }] }
@@ -182,63 +179,7 @@ generators: [
   </TabItem>
 </Tabs>
 
-
-
-### Configure license key
-
-The EventBridge plugin requires an EventCatalog Scale license key to work with EventCatalog.
-
-You can get a 30-day trial Scale license key by going to [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 EventBridge plugin key, you can still use it with the EventBridge-specific environment variable.
-
-```bash title=".env"
-EVENTCATALOG_LICENSE_KEY_EVENTBRIDGE=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 EventBridge plugin.
-
-```js title="eventcatalog.config.js"
-export default {
-  generators: [
-    [
-      '@eventcatalog/generator-eventbridge',
-      {
-        licenseKey: '[INSERT_YOUR_LICENSE_KEY]', // or process.env.EVENTCATALOG_SCALE_LICENSE_KEY
-        region: 'us-east-1',
-        registryName: 'discovered-schemas'
-      },
-    ],
-  ],
-};
-```
-
-#### 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.
+This 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.
 
 #### Run the plugin
 
@@ -285,33 +226,6 @@ It's recommended you create a new IAM user with the following policy.
 }
 ```
 
-
-## 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 OpenAPI 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).
-
 ## Issues
 
 If you have any problems or feature requests please feel free to raise them on GitHub. https://github.com/event-catalog/generators

package/dist/docs/plugins/eventbridge/03-api.md

@@ -138,28 +138,10 @@ The EventBridge registry name for your schemas.
 ],
 ```
 
-### `licenseKey` {#licenseKey}
+:::info No license key needed
 
-- Type: `String`
-
-The license key for the EventBridge generator. You can get a 30-day trial Scale license key by going to [EventCatalog Cloud](https://eventcatalog.cloud).
+The generator 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.
 
-```js title="eventcatalog.config.js"
-[
-  '@eventcatalog/generator-eventbridge',
-  {
-    licenseKey: 'YOUR_LICENSE_KEY'
-  },
-],
-```
-
-:::info Using environment variables
-
-You can also set the license key as an environment variable. If this is set on the machine the `licenseKey` is not required in the generator configuration.
-
-```bash
-EVENTCATALOG_SCALE_LICENSE_KEY=YOUR_SCALE_LICENSE_KEY
-```
 :::
 
 ## Optional fields {#optional-fields}

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

@@ -7,11 +7,6 @@ title: Introduction
 description: Getting started with GitHub plugin
 ---
 
-
-<!-- import PluginLicense from '@site/src/components/MDX/PluginLicense'; -->
-
-<!-- <PluginLicense url="#commercial-use" /> -->
-
 <!-- <iframe width="100%" height="515" src="https://www.youtube.com/embed/NMZKnPKx-L0?si=og1Nvnr3FfPfAqn4" 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> -->
 
 <iframe width="100%" height="515" src="https://www.youtube.com/embed/o2ryPdBa-68?si=2d1cynW_wgzNhbaV" 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>
@@ -62,32 +57,6 @@ Any documentation you add to your schemas in EventCatalog will persist between b
 
 :::
 
-## 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`._
-
 ## 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 GitHub 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).

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

@@ -8,13 +8,10 @@ description: Installation of the EventCatalog GitHub 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 GitHub plugin is used to pull and sync your schemas from your GitHub repository to EventCatalog, these can be public or private repositories.
 
 You can map your schemas from your GitHub repository to commands, events and queries in your catalog, and assign these to services (producers and consumers) and domains.
@@ -122,7 +119,6 @@ In this example we:
 - Create a domain `Retail Domain`
   - Assign the services to the domain
 
-
 ```js title="eventcatalog.config.js"
 // ...
  [
@@ -194,32 +190,9 @@ In this example we:
   </TabItem>
 </Tabs>
 
-### Configure API keys
-
-The EventCatalog GitHub plugin requires API keys in your environment variables.
-
-1. An EventCatalog Scale license key for the GitHub plugin (30-day trial, at [EventCatalog Cloud](https://eventcatalog.cloud))
-
-Create a `.env` file in the root, and add your keys to the project.
+### License
 
-```bash title=".env"
-# EventCatalog license key
-EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
-```
-
-:::tip Using an Older API Key?
-
-If you already have an older GitHub plugin key, you can still use it with the plugin-specific environment variable.
-
-```bash title=".env"
-EVENTCATALOG_LICENSE_KEY_GITHUB=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.
+This 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.
 
 ### Private repository authentication
 
@@ -234,9 +207,6 @@ You can authenticate in two ways:
 Set the `EVENTCATALOG_GITHUB_TOKEN` environment variable in your `.env` file.
 
 ```bash title=".env"
-# EventCatalog license key
-EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
-
 # GitHub token for private repository access
 EVENTCATALOG_GITHUB_TOKEN=ghp_your_token_here
 ```
@@ -291,8 +261,6 @@ npm run dev
 npm run build
 ```
 
-
-
 ## Any questions or need help?
 
 If you get stuck, find an issue or need help, please raise an issue on [GitHub](https://github.com/event-catalog/eventcatalog/issues) or join our [Discord community](https://eventcatalog.dev/discord).