- Home
- Destinations
Stream Postgres changes to 19 destinations.
Every destination is included on every plan, and one pipeline can deliver to as many as you like — in order per row, at least once. Pick a destination to see how to connect it and exactly how changes arrive there.
HTTP
Queues & streams
Apache Kafka
Any Kafka-protocol broker
Amazon SQS
Standard and FIFO queues
Amazon SNS
Fan-out to many subscribers
Amazon EventBridge
Rules, targets, event buses
Amazon Kinesis
Data Streams, partitioned by row
Redis Streams
XADD, consumer groups
Google Pub/Sub
Native ordering keys
NATS JetStream
Nats-Msg-Id dedupe
RabbitMQ
Exchanges, confirms
Azure Event Hubs
Kafka endpoint, connection string
Azure Service Bus
Sessions, duplicate detection
Cloudflare Queues
Workers consumers
Search
Elasticsearch
Bulk upsert and delete
OpenSearch
Bulk upsert and delete
Typesense
Upsert import, id from PK
Meilisearch
Documents API, id from PK
Storage & cache
Common questions
Are destinations charged separately?
No. Sinks, pipelines and seats are unlimited on every plan, including Free. The only meter is egress — the gigabytes delivered to your sinks.
Can one pipeline deliver to several destinations?
Yes. A pipeline has one source database and any number of sinks. Every change is delivered to every sink, each with its own batch size, rate limit, retries and replay.
Can I add a destination to a running pipeline?
Yes. A new sink starts receiving changes from the moment it is added, with no interruption to the others. Run a backfill to hand it the rows that already exist.
What if my destination isn't listed?
Anything that accepts an HTTP request works through the webhook sink — that covers Slack, Discord, serverless functions and most SaaS APIs. For a native connector, email us.