Introduction

rollout tells your users what you shipped. You write small snippets, one per feature or fix, bundle them into an announcement, and publish it now or at a set time. rollout then delivers it through up to three channels:

• In-app feed: a “What’s new” bell and panel inside your product, with read state per user. You add it with the @rollout/js SDK, either as the ready-made <rollout-feed> widget or as a headless client that drives your own UI.
• Public changelog: your announcements as a public JSON API, RSS and JSON Feed, to render on your own site.
• Email: a campaign draft in Loops, kept up to date as you publish. You review and send it in Loops.

How the pieces fit

1. In the dashboard, you create a project for your product. It has its own API keys, users and settings.
2. Your product’s frontend loads the feed with a publishable key (pk_live_…) and tells rollout who the user is with a signed identity token.
3. rollout returns the announcements that user may see (see Targeting), and remembers what they have read.
4. Your servers can act for users with a secret key (sk_live_…): create them ahead of time, read their feed or mark announcements read.

Where to start

QuickstartThe widget in your app in a few minutes.

WidgetAttributes, events, theming and texts.

Headless clientBuild your own UI on the same data.

IdentitySigned tokens, your auth provider, or unverified users.