Features
Features
Everything Pipeo does, one page per feature, with the limits that apply.
- 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.
- 04
Dedupe of client retries
A client that retries the same event does not cause a second delivery: events are keyed by source and message id.
- 05
Archive and replay
Every accepted event is archived to S3-API object storage, and any time window can be replayed to a destination.
- 06
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.
- 07
Workspaces, roles and audit
Each workspace is isolated in the database, members hold one role each, and every change is recorded.
- 08
Connection tests
Check a destination’s settings before you send live traffic: the worker sends test messages and reports back.
- 09
Rate limits per source and workspace
Ingest limits events per second per source and per workspace, so one noisy client cannot crowd out the rest.
- 10
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.
Send once, deliver everywhere
Sign in, create a source, connect your destinations and change one host setting in your SDK.