Build

Connectors

A connector is how Sirius reaches the outside world. Each family can run as a source (listen or poll) or a destination (send). Settings live in a tenant registry so many integrations can share one endpoint. Probe a connector before you trust it — dry-run checks configuration; live mode exercises the real path.

TLS verification is on by default. For private CAs, pin a CA bundle instead of disabling verification.

Transport

HTTP / REST, webhooks, SOAP, TCP/UDP, email, file, and SFTP cover the majority of application and file-based traffic. HTTP sources expose inbound paths; destinations POST, PUT, or SOAP-call a peer. File and SFTP connectors resolve host paths through a shared data directory so the path you type is the path the runtime can see.

Messaging and data

Kafka, RabbitMQ, Redis, cloud messaging, object storage, MongoDB, and relational databases attach Sirius to the buses and stores you already operate. Database calls from a transform target a connector id — never a raw connection string — and use bound parameters.

Industry standards

Sirius speaks common interchange formats natively:

MLLP for HL7 v2 on the wire
FHIR over HTTP
X12 and EDIFACT for EDI
AS2 for partner interchange
DICOM for imaging
FIX for trading sessions

Codecs for ISO 20022 and related financial messages sit on the same sirius.* and REST surfaces.

Devices and plants

MQTT, CoAP, OPC UA, SIP, SMPP, and BACnet/IP bring device, building, and telecom traffic onto the same canvas as application integrations.

Applications

Generic ERP and SaaS connectors cover the long tail of enterprise apps without a dedicated product for each vendor.

Configure connectors in the console under Connect, or through the REST API (/sources, /destinations, /connectors).