Feature
Archive and replay
Every accepted event is archived to S3-API object storage, and any time window can be replayed to a destination.
The archiver writes the raw accepted events to S3-API object storage (AWS S3 or a self-hosted store such as SeaweedFS).
An operator can replay a source’s events from a time window to one destination, with an optional rate cap. Replaying history into a newly added destination is a backfill.
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.