Rheo documentation

Get started in 15 minutes

Minimal path from an empty workspace to a flow your users can see through a channel or the SDK.

Purpose

This guide walks you from an empty workspace to a flow your users can experience—either through a channel in the dashboard or the SDK in your app. Most teams finish the first pass in about fifteen minutes.

What you will have at the end

A flow (a guided experience you designed) connected to an app in your workspace, ready to assign to a channel for staged delivery or to serve through the SDK in your product.

The model in one diagram

  1. Workspace — Your company's home in Rheo: members, billing, and settings.
  2. App — A product or surface you onboard users into (often one per mobile app or brand).
  3. Flow — The storyboard: screens, branching, visuals, motion, and copy.
  4. Channel — How you roll a flow out to segments (staging, QA, percentages, approvals).
  5. Customer — An end-user record with attributes and eligibility for experiments.

Continue in Core concepts for short definitions of each term.

First fifteen minutes

  1. Sign in to your workspace and finish any Setup prompts (profile and workspace basics).

Rheo dashboard after first sign-in, showing the Setup checklist or empty Apps list with a prominent option to create an app

  1. Create or open an app from Apps so you have a container for flows.

Apps list with the Create app button and at least one app row visible

  1. Create a flow (blank or from a template). You land in the flow builder canvas.

Flow builder canvas with a new or template flow open, showing the screen list and canvas area

  1. Add at least one screen and connect it meaningfully. Keep the flow valid—the editor warns when required fields are missing.
  2. Save frequently; autosave backs you up during longer sessions.
  3. Choose delivery:
  4. Optional integrations — enable RevenueCat or AppsFlyer under App settings → Integrations before using paywall nodes or attribution-driven decisions. See Integrations.

Limits

Validation rules and rollout policies depend on your workspace plan and each member's role. Some features (experiments, approvals, integrations) require Grow or Scale. See Plans & entitlements.