Feature
Sealed secrets and rotating write keys
Destination secrets are sealed so only the worker can open them, and write keys rotate without cutting off clients.
Secret destination settings, such as an API secret or a webhook URL, are sealed by the admin API to the worker’s public key. Only the worker, which sends the events, can open them, and the console never shows them again.
A source’s write key is shown once and only its hash and prefix are stored. Rotating it keeps the previous key valid for a grace period so deployed clients keep working, and previous keys can be revoked early.
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.