Rollouts are delivered in the SDK config payload alongside feature flags, so you can stage a release to a percentage of users and expand it over time.
Releases & Rollouts
Control staged rollouts and watch release health from one place — rollouts are delivered in the same SDK config payload as flags and experiments, so you can ship a release to a percentage of users and widen it over time.
What releases & rollouts gives you
Staged rollouts delivered via the SDK config payload, with release health.
Stage a release to a percentage, then widen it
A rollout ships to a slice of users first and expands over time. Because the rollout rides in the same config payload as flags, a single SDK fetch decides who is on the new release — no separate rollout SDK.
Watch release health as it widens
Rollouts sit next to app health, so the crash, error, and performance read for the release is on the same timeline as the rollout — you widen or hold based on how the slice already on it is doing.
Built as one lightweight SDK, not five disconnected tools.
One install brings the whole platform online, with the plumbing — queueing, batching, retries, and masking — handled for you.
- One installation
- OTA bundle updates
- One identity layer
- One event schema
- Offline queueing
- Batching & retrying
- Privacy controls
- Masking by default
- iOS · Android · RN
- Server-side APIs
- Webhooks
- Data export
Releases & Rollouts — common questions
See every journey. Fix every issue. Grow every user.
One SDK, one timeline, and one dashboard for marketing, product, and engineering.