Feature
Postgres by default, Kafka when you need it
Run on Postgres and Redis alone, and switch on a Kafka fast lane above about 2,000 events per second.
Tier A, the default, keeps the inbox and the delivery jobs in Postgres and uses Redis for dedupe and rate limits. It runs on one VPS.
Tier B (PIPELINE_MODE=kafka) carries raw events and first delivery attempts through Kafka. A clean first delivery needs no database write; everything else spills to the Postgres slow lane.
More features
All features →- 01
Segment-style tracking API
One endpoint accepts the Segment-style HTTP tracking protocol, so existing analytics SDKs only need a new host.
- 02
Fan-out with per-connection rules
Each source fans out to every destination it is connected to, with an event filter and dropped fields per connection.
- 03
Retries, dead letters and circuit breakers
Failed deliveries retry with backoff, permanent rejections stop at once, and a failing vendor trips a circuit breaker.