Overview

DataRelay Control sits in the data path. It does not only configure other relays: the current runtime fetches or receives events, transforms them, evaluates controls, delivers them, and advances checkpoints after the required delivery outcome. The core entities are:

Entity	Responsibility
Connector	Connection family and authentication capability
Credential	Runtime secret-bearing authentication object
Source	Concrete source configuration
Stream	Runtime execution and checkpoint ownership
Route	Destination-specific processing and delivery
Destination	Concrete delivery target
Source Pack	Declarative integration content; not a runtime process

Typical setup flow

Create or install an integration/Connector.
Configure credentials and source access.
Create a Stream.
Collect a sample and confirm the record structure.
Select one or more Destinations.
Configure Route Processing where destinations need different handling.
Deploy.
Monitor Dashboard and Streams, then review delivery records and governance views as needed.

Source types proven in the current product line

The repository implements HTTP API polling and webhook receiver sources, plus a PostgreSQL path for database queries. Other adapters may exist in the codebase, but this site documents only the paths verified in the current source.

Product naming

Public documentation uses DataRelay Control consistently. Some source identifiers still use gdc, including environment-variable prefixes, Docker object names, and database defaults. The documentation keeps those identifiers where they are required for accurate commands.

Last modified on September 28, 2026