Prerequisites

The prerequisites for running the ADS framework depend on your role in the system.

For ADS Publishers

If you’re an ADS publisher, you’ll need the following infrastructure components:

Access to your data source

This can happen in two ways:

• Scenario 1: External Data Source with separate ADS Publisher service

  • You write your own ADS Publisher service that listens to your data source (like Notion, AirTable, Google Drive, Paddle, etc.) via webhooks, polling, or other event-driven mechanisms.

  This service will then send events to the ADS Bridge for distribution to ADS Subscribers.

• Scenario 2: Data Source with built-in ADS Publisher

  • Your data source has a built-in ADS Publisher that can directly publish events to the ADS Bridge.

  This is often the case with applications you have 1st party control over - e.g. purpose built applications at enterprises or consumer usecases

Redis Instance

ADS Bridge requires a Redis instance for routing WebSocket messages.

RabbitMQ Instance

ADS uses RabbitMQ as the transport mechanism between the Publisher and the Bridge

Deployment Options

• Step 1: Hosting ADS Bridge

  Self-hosted using Docker Compose:

  • ADS Bridge Quick Start  includes instructions to start the ADS Bridge with other dependencies like Redis and RabbitMQ
  • Simply run the compose file to get everything up and running

  Using your own instances:

  • Remove the Redis and RabbitMQ services from the Docker Compose file 
  • Host your own Redis and RabbitMQ instances
  • Modify the environment variables  in the Docker Compose file to point to your instances

  Cloud-managed options:

  • Redis: AWS ElastiCache, Redis Cloud, Azure Cache for Redis
  • RabbitMQ: CloudAMQP (free tier available), AWS, Azure

• Step 2: Pointing your ADS Publisher to your RabbitMQ instance

  • Ensure your ADS Publisher is configured to send events as explained in the ADS Publisher documentation
  • The hosted ADS Bridge will automatically handle the routing of these events to the ADS Subscribers

For ADS Subscribers

All you need is access to an AI agent which would be triggered by the ADS events heard by the ADS Subscriber.

It could be:

• An n8n agent node 

  Refer to the n8n ADS documentation for setup instructions

• An instantiated AI agent object from frameworks like LangChain , LlamaIndex , or similar (in programmatic environments like Python, Node.js, etc.)