Signals Gateway enables businesses to receive and send events on their own infrastructure, created using the components and structure described in the documentation below. It does not require any dedicated developer resources, so no third-party partners or coding is necessary for setup.
Additionally, the Signals Gateway offers incremental efficiencies, such as:
The Signals Gateway is configured by self-provisioning a server instance in your cloud environment, which is used to send events through a reliable server to server connection to specific destinations.
Below is a high level diagram of the major components involved in Signals Gateway:
The Signals Gateway supports multiple domains. For example, you can have multiple domains such as “domain.com” , “domain.co.uk”, “anotherdomain.com”. All of these domains could be configured within a single instance of the Signals Gateway during deployment. Please review the Setup Guide for more details.
The Signals Gateway requires a public cloud provider (for example, AWS) account to allow users to automatically deploy the underlying infrastructure without the need of a developer as well as to have a predictable cost.
The Signals Gateway provides a user interface with the product. You can access this UI from https://<Signals Gateway Endpoint>/hub/capig
(that is, the Signals Gateway endpoint that you have configured in DNS).
From this UI, you can see: