Live production alert · Pub/Sub lag 34s

The Pub/Sub connector is experiencing elevated lag. Zipline is retrying at 2× throughput. No messages at risk - exactly-once guarantees active.

v2.4 · Exactly-once for Kafka 3.8

Stream every row,
to anywhere, in
under a second

Zipline connects your production databases to Kafka, PubSub, Snowflake, BigQuery, and S3 with exactly-once delivery and sub-second latency - no data loss, no duplicates. Apply the spec, then bind it to a runtime - no dashboards, no wizard.

Start streaming Book a Session

SOC 2 · Apache 2.0 · self-hosted

View A · section A-AScale 1:1

142 ms

Commit → sink ack · P50

View B · detail2:1

routes:
  - from: orders-db
    to: [kafka-out]

orders.yaml · 22 lines

View C · revisionsCurrent 2.4

2.4 exactly-once, Kafka 3.8
2.3 schema evolution
2.2 replay windows
2.1 Terraform provider

View D · bill of materialsShipping

Item	Part	Dir	Class
01	postgres	src · snk	CDC
02	mssql	src	CDC
03	kafka	snk	Bus
04	file	snk	File
	27 further parts continued on sheet 2

View E · approvalAudited

View F · performanceSingle node · m5.4xlarge

View G · deployScale · seconds

Zipline · delivery guarantee Rev 2.4 Sheet 1 of 2

Trusted by engineering teams at

"Figma's design data model is complex - hundreds of table types, high write volume, very low tolerance for inconsistency. Zipline handles the cardinality and throughput without breaking a sweat. The Terraform provider made our rollout completely automated."

Principal Engineer · Figma · Backend Infrastructure

How it works

Three steps.
One file.

orders.yaml one file · three steps

name: orders
connectors:
  - name: orders-db
    type: source/postgres
    host: "${POSTGRES_HOST}"
    port: "${POSTGRES_PORT}"
    database: "${POSTGRES_DATABASE}"
    user: "${POSTGRES_USER}"
    publication: "${POSTGRES_PUBLICATION}"
    slot_name: "${POSTGRES_SLOT_NAME}"
    secret_refs:
      - { field: password, ref: postgres-password }
  - name: kafka-out
    type: sink/kafka
    brokers: "${KAFKA_BROKERS}"
    topic_prefix: "${KAFKA_TOPIC_PREFIX}"
routes:
  - from: orders-db
    to: [kafka-out]

~ zipline pipeline apply -f orders.yaml✓ applied orders  the spec is recorded. nothing streams yet.~ zipline pipeline bind orders --instance src-7f3abinding src-7f3a to orders...✓ bound orders <- src-7f3a  state: pending  route orders-db → kafka-out · running

Lag P50

142ms

Rows

1.2M

Lost

Observability Pipelines

Performance