> ## Documentation Index
> Fetch the complete documentation index at: https://ventstream.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connectors

> The sources VentStream reads from and the sinks it writes to — and what's supported today.

A **connector** is how VentStream talks to a system. The table below is the
implemented connector surface for the current release.

* **Source connectors** read a system's native change stream and feed
  it into the engine (the capture pipeline).
* **Sink connectors** write the engine's output documents to a target
  store.
* The **real-time bus** carries published events for the delivery
  pipeline.

## Supported today

| Kind                 | Connector                                                  | Notes                                                      |
| -------------------- | ---------------------------------------------------------- | ---------------------------------------------------------- |
| **Source**           | [PostgreSQL](/docs/connectors/sources/postgres)                 | logical replication (`pgoutput`)                           |
| **Source**           | [Neo4j](/docs/connectors/sources/neo4j)                         | `db.cdc.*` on Enterprise or supported AuraDB tiers         |
| **Source**           | [MongoDB](/docs/connectors/sources/mongodb)                     | change streams from a replica set or sharded cluster       |
| **Source**           | [MySQL / MariaDB](/docs/connectors/sources/mysql)               | row-based binlog replication                               |
| **Source**           | [Kafka / Redpanda](/docs/connectors/sources/kafka)              | Debezium envelopes or raw JSON topics                      |
| **Sink**             | [OpenSearch / Elasticsearch](/docs/connectors/sinks/opensearch) | shared `_bulk` API                                         |
| **Sink**             | [Meilisearch](/docs/connectors/sinks/meilisearch)               | task-based document sync with delete propagation           |
| **Sink**             | [Redis](/docs/connectors/sinks/redis)                           | deterministic materialized views or expiring cache entries |
| **Real-time broker** | NATS Core / JetStream                                      | live or replayable delivery                                |
| **Real-time broker** | Redis Streams                                              | replayable delivery with shared tenant tailers             |

<Info>
  This matrix is the implemented surface for the current release. The architecture
  is pluggable, but a connector is supported only when it appears here and in the
  release test matrix.
</Info>

## Source connectors

<CardGroup cols={2}>
  <Card title="PostgreSQL" icon="elephant" href="/docs/connectors/sources/postgres">
    Logical replication → embed related rows into each document, with
    field selection and 1:1 / 1:many joins.
  </Card>

  <Card title="Neo4j" icon="circle-nodes" href="/docs/connectors/sources/neo4j">
    CDC → fold a node's neighborhood into one document with multi-hop,
    bounded fan-out.
  </Card>

  <Card title="MongoDB" icon="leaf" href="/docs/connectors/sources/mongodb">
    Change streams and resumable bootstrap for collections in replica sets or
    sharded clusters.
  </Card>

  <Card title="MySQL / MariaDB" icon="database" href="/docs/connectors/sources/mysql">
    Row-binlog CDC with snapshot bootstrap and memory or SQL projection modes.
  </Card>

  <Card title="Kafka / Redpanda" icon="arrows-left-right" href="/docs/connectors/sources/kafka">
    Consume Debezium change envelopes or raw JSON with sink-gated offset commits.
  </Card>
</CardGroup>

## Realtime brokers

<CardGroup cols={2}>
  <Card title="NATS" icon="tower-broadcast" href="/docs/concepts/realtime-brokers">
    Use NATS Core for live-only delivery or JetStream for acknowledged,
    cursor-based replay.
  </Card>

  <Card title="Redis Streams" icon="database" href="/docs/concepts/realtime-brokers">
    Use Redis Streams for cursor-based replay when Redis is already part of the
    operating environment.
  </Card>
</CardGroup>

## Sink connectors

<CardGroup cols={2}>
  <Card title="OpenSearch / Elasticsearch" icon="magnifying-glass" href="/docs/connectors/sinks/opensearch">
    Bulk upserts with deterministic document IDs. The same engine handles
    both (shared `_bulk` API).
  </Card>

  <Card title="Meilisearch" icon="magnifying-glass" href="/docs/connectors/sinks/meilisearch">
    Continuous search-index sync with joined documents, deterministic
    primary keys, and delete propagation.
  </Card>

  <Card title="Redis" icon="database" href="/docs/connectors/sinks/redis">
    Ordered, idempotent key materialization with string or RedisJSON values,
    optional TTLs, and replica acknowledgement.
  </Card>
</CardGroup>