> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rheon.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Integration options

> How you will embed Rheon: hosted iframe, SDK, or redirect, and the trade-offs of each.

There will be a few ways to put Rheon inside your product. The exact integration details
are being finalized - this page describes the planned options and what each is for.

<Note>
  **Planned - details coming soon.** The widget is a live preview today
  ([rheon-app.vercel.app](https://rheon-app.vercel.app)). The embed methods below, their
  code, and configuration will be documented here once they are real and tested.
</Note>

| Option            | What you get                                                    | Best when                                      | Status      |
| ----------------- | --------------------------------------------------------------- | ---------------------------------------------- | ----------- |
| **Hosted iframe** | The full widget embedded in your page. Fastest to ship.         | You want to launch quickly with minimal code.  | Coming soon |
| **SDK**           | The widget as a component, with events and theming in your app. | You want control over UI and lifecycle events. | Coming soon |
| **Redirect**      | You send the user to a hosted Rheon URL and they return after.  | You cannot embed (e.g. some mobile flows).     | Coming soon |

A proposed design for these - embed variants, secure widget URL, chain/token filtering,
and lifecycle events - is in [Proposals → Integration](/proposals/integration) for team
review.

## Secure widget URL

<Note>
  **Coming soon.** For production, your backend will request a **signed** widget URL so the
  configuration cannot be tampered with. This is the recommended pattern for white-label
  deposits.
</Note>

## SDK

<Note>
  **Coming soon.** The SDK will expose the widget as a component with lifecycle events and
  theming hooks, so your app can react to the flow in real time. It is being built
  alongside the routing layer.
</Note>