diff --git a/connector/doc/AJA_Bridge_Live.md b/connector/doc/AJA_Bridge_Live.md
new file mode 100644
index 00000000..e154e3a5
--- /dev/null
+++ b/connector/doc/AJA_Bridge_Live.md
@@ -0,0 +1,56 @@
+---
+uid: Connector_help_AJA_Bridge_Live
+---
+
+# AJA Bridge Live
+
+## About
+
+The AJA Bridge Live connector enables seamless integration with AJA Bridge Live, a high-performance turnkey solution for SDI video encoding, decoding, transcoding, and streaming. Designed for remote production, live contribution, and content delivery, this connector allows users to monitor and configure critical workflows while ensuring reliable, cost-effective video transport across networks.
+
+## Key Features
+
+**System monitoring**: Retrieve system details such as software versions and real-time GPU/CPU utilization for performance monitoring.
+
+**Network interface management**: Monitor network interfaces and bandwidth utilization, and ensure optimal connectivity for uninterrupted streaming.
+
+**Pipeline control & configuration**: Start, stop, and modify pipelines dynamically, adjusting video, audio, and caption settings as needed.
+
+**Input & output stream management**: Configure input and output streams with flexible encoding and transport options, including NDI, SRT, and RTMP.
+
+## Use Cases
+
+### Use Case 1: Replacing Satellite Uplink with IP Streaming
+
+**Challenge**: Traditional satellite uplink solutions are expensive and require extensive infrastructure, making them inefficient for modern live broadcasts.
+
+**Solution**: AJA Bridge Live allows broadcasters to replace satellite transponders with a simple ISP connection, leveraging bidirectional IP transport for reliable video streaming.
+
+**Benefit**: Significant cost savings, reduced complexity, and improved flexibility for remote productions and live events.
+
+### Use Case 2: Dynamic Multi-Codec Transcoding
+
+**Challenge**: Live production environments require real-time transcoding across multiple formats to ensure compatibility with different platforms.
+
+**Solution**: Bridge Live supports multiple codecs (H.264, HEVC, JPEG XS, MPEG-2) and can dynamically transcode streams to meet delivery requirements.
+
+**Benefit**: Enhanced compatibility with CDNs like YouTube, Twitch, and Facebook Live, enabling seamless content distribution.
+
+### Use Case 3: High-Redundancy Live Streaming
+
+**Challenge**: Live video streams are vulnerable to network issues such as packet loss, jitter, and latency fluctuations.
+
+**Solution**: With SMPTE 2022-7 hitless redundancy, AJA Bridge Live ensures seamless failover by transmitting identical streams across independent network paths.
+
+**Benefit**: Increased reliability, reduced risk of video interruptions, and optimized quality of experience for viewers.
+
+## Technical Reference
+
+### Prerequisites
+
+- Network access: AJA Bridge Live must be accessible over the network for API communication.
+- Authentication configuration: Basic authentication credentials (username and password) must be set up.
+- Pipeline configuration: Users should pre-define input and output settings for efficient stream management.
+
+> [!NOTE]
+> For detailed technical information, refer to our [technical documentation](xref:Connector_help_AJA_Bridge_Live_Technical).
diff --git a/connector/doc/AJA_Bridge_Live_Technical.md b/connector/doc/AJA_Bridge_Live_Technical.md
new file mode 100644
index 00000000..767e88fd
--- /dev/null
+++ b/connector/doc/AJA_Bridge_Live_Technical.md
@@ -0,0 +1,37 @@
+---
+uid: Connector_help_AJA_Bridge_Live_Technical
+---
+
+# AJA Bridge Live
+
+## About
+
+BRIDGE LIVE is the broadcast-quality, low-latency turnkey system for REMI, synchronous multi-channel video contribution, remote collaboration, direct-to-audience streaming, and multi bit rate/multi format delivery.
+
+## Configuration
+
+### Connections
+
+#### HTTP Connection - Main Connection
+
+This connector uses an HTTP connection and requires the following input during element creation:
+
+HTTP CONNECTION:
+
+- **IP address/host**: The polling IP or URL of the destination.
+- **IP port**: The IP port of the destination.
+- **Device address**: The bus address of the device. If the proxy server has to be bypassed, specify *BypassProxy*.
+
+### Initialization
+
+The **Configuration** subpage contains the **Username** and **Password** fields. These fields are used to authenticate the user to the device. These fields must be filled in for the connector to be able to retrieve information.
+
+## How to use
+
+REST API is used to retrieve the device information. The connector can be used to retrieve the device information and monitor the device status.
+
+The **Pipelines** page shows information about all available pipelines. You can also start and stop pipelines from this page.
+
+Pipelines can be edited from the **Inputs** and **Outputs** pages.
+
+All sets to the device can be found on the **Pipeline Sets** page.
diff --git a/connector/toc.yml b/connector/toc.yml
index 5e71b662..60aa65a2 100644
--- a/connector/toc.yml
+++ b/connector/toc.yml
@@ -256,6 +256,11 @@
     topicUid: Connector_help_AIRSYS_UNICOOL_ASMUC
 - name: AJA
   items:
+  - name: AJA Bridge Live
+    topicUid: Connector_help_AJA_Bridge_Live
+    items:
+      - name: AJA Bridge Live Technical
+        topicUid: Connector_help_AJA_Bridge_Live_Technical
   - name: AJA IPR-10G2-HDMI
     topicUid: Connector_help_AJA_IPR-10G2-HDMI
   - name: AJA IPT-10G2-HDMI