diff --git a/.changeset/angry-views-win.md b/.changeset/angry-views-win.md
new file mode 100644
index 0000000000..bf45881d25
--- /dev/null
+++ b/.changeset/angry-views-win.md
@@ -0,0 +1,23 @@
+---
+'@backstage/plugin-events-backend-module-kafka': minor
+---
+
+**BREAKING**: Updated `kafkaConsumingEventPublisher` configuration to support multiple named instances
+
+The Kafka configuration now requires named instances instead of a single configuration object for `kafkaConsumingEventPublisher`, this allows for multiple Kafka configurations.
+
+These changes are **required** to your `app-config.yaml`:
+
+```diff
+events:
+  modules:
+    kafka:
+      kafkaConsumingEventPublisher:
+-       clientId: your-client-id
+-       brokers: [...]
+-       topics: [...]
++       default:  # Or any name like 'prod', 'dev', etc.
++         clientId: your-client-id
++         brokers: [...]
++         topics: [...]
+```
diff --git a/.changeset/stale-poets-battle.md b/.changeset/stale-poets-battle.md
new file mode 100644
index 0000000000..1725fd2885
--- /dev/null
+++ b/.changeset/stale-poets-battle.md
@@ -0,0 +1,7 @@
+---
+'@backstage/plugin-events-backend-module-kafka': minor
+---
+
+Added `KafkaPublishingEventConsumer` to support sending Backstage events to Kafka topics.
+
+This addition enables Backstage to publish events to external Kafka systems, complementing the existing ability to receive events from Kafka. This allows for better integration with external systems that rely on Kafka for event streaming.