Skip to content

Connectors

A connector is a pipeline that runs on the server. A sink subscribes to the log and pushes records out to an external system. A source does the reverse: it receives from an external system and appends to a stream. Nothing runs in your application.

DiagramProducer systemKurrentDBConsumer systemSource connectorStreamsSink connectorReceiveAppendSubscriptionFilterSink

That placement is the whole point. A subscription service you write yourself has to be hosted, observed and checkpointed. A catch-up subscription must also run as a single instance to preserve order, which makes that instance a single point of failure. The connector runtime is the server’s problem instead of yours.

instanceTypeName picks the implementation. Because the implementations ship with the server, this list tracks the server version, not the SDK. It is current for KurrentDB 26.1.

instanceTypeName Writes to Since
http-sink Any HTTP endpoint 24.10
serilog-sink A Serilog sink: console, file or Seq 24.10
kafka-sink A Kafka topic 24.10
mongo-db-sink A MongoDB collection 24.10
rabbit-mq-sink A RabbitMQ exchange 24.10
elasticsearch-sink An Elasticsearch index 25.0
pulsar-sink A Pulsar topic 25.1
sql-sink SQL Server or PostgreSQL 26.0
instanceTypeName Reads from Since
kafka-source A Kafka topic 26.0
webhook-source POST /webhook/{connectorId} 26.1

Each page carries that connector’s settings and says whether it needs a license. Three connectors run without a license key: http-sink, serilog-sink and webhook-source. The server refuses to start a licensed feature without a key. Reach for serilog-sink when you want to watch a connector work before buying anything.

A source is not a sink with the arrow reversed. It receives and appends, and there is no filter or transformer in the path:

DiagramKafka, a webhook callerSource connectorKurrentDBReceiveAppendStreamsCheckpoints messagesrecordsposition

client.Connectors creates and controls connectors. It manages their lifecycle; it does not implement them and it does not validate their settings.

await client.Connectors.Create("orders-to-kafka", settings);

Managing connectors is the full lifecycle, How Sinks Work covers filters, transformations and delivery, How Sources Work covers the ingest side, Data Protection covers encrypted settings, and Observability is what a running connector reports.