# Widget SDK: Coinme App Platform > Every page and skill for the Widget SDK, in one file: the SDK documents and guides, and the Agent Skills that integrate it. The Widget SDK belongs to the Widget / Ramp integration; https://platformdocs.coinme.com/agents/surfaces.md explains the two surfaces. The index of the whole site is https://platformdocs.coinme.com/llms.txt. --- --- title: "Embed Coinme Widget with Framekit." url: "https://platformdocs.coinme.com/#/build/web" markdown: "https://platformdocs.coinme.com/pages/build/web/overview.md" summary: "This page demonstrates how the Coinme Widget can be embedded in a partner web application using the Coinme Framekit SDK." surface: "ramp" platform: "web" package: "@coinme/coinme-bridge-framekit" version: "1.1.2" peerDependencies: {"react":">=18.0.0","react-dom":">=18.0.0"} --- # Embed Coinme Widget with Framekit. This page demonstrates how the Coinme Widget can be embedded in a partner web application using the Coinme Framekit SDK. Framekit (`@coinme/coinme-bridge-framekit`) is the web counterpart to Coinme's iOS and Android bridges, which allow embedding into native apps. All flows run inside the embedded frame. The live demo is not available in [sanctioned or otherwise restricted jurisdictions](https://platformdocs.coinme.com/pages/explainers/faq.md#sanctioned-jurisdictions) due to regulation. On the site, this page runs the live Coinme Widget beside the text: a full Orchestrator deployment in an iframe, mounted with framekit's `CoinmeFrame`. A Markdown file cannot host the embed; [How to use](https://platformdocs.coinme.com/pages/build/web/how-to-use.md) has the code that puts it on a page and [How it works](https://platformdocs.coinme.com/pages/build/web/how-it-works.md) explains the bridge behind it. --- --- title: "One iframe, one SDK, the whole ramp." url: "https://platformdocs.coinme.com/#/build/web/how-it-works" markdown: "https://platformdocs.coinme.com/pages/build/web/how-it-works.md" summary: "The widget in this demo is a full Coinme Orchestrator deployment running in an iframe. Framekit (@coinme/coinme-bridge-framekit) is the TypeScript SDK that puts it there and keeps a secure, typed message channel, the bridge, open between the host app and the widget." surface: "ramp" platform: "web" package: "@coinme/coinme-bridge-framekit" version: "1.1.2" peerDependencies: {"react":">=18.0.0","react-dom":">=18.0.0"} --- # One iframe, one SDK, the whole ramp. The widget in this demo is a full Coinme Orchestrator deployment running in an iframe. **Framekit** (@coinme/coinme-bridge-framekit) is the TypeScript SDK that puts it there and keeps a secure, typed message channel, the **bridge**, open between the host app and the widget. The web isn't the only host. Coinme ships native bridge SDKs for **iOS** (CoinmeViewController, Swift) and **Android** (CoinmeFragment, Kotlin) that embed the same Orchestrator in a WebView using the same bridge mechanics: identical protocol, handshake, rampConfig payload, and events. Integrate once conceptually, and the ramp behaves the same in a web page or a native app. ## Three layers, three responsibilities - **Owns the page** (Your app): Layout, branding, where the widget sits, and the CoinmeConfig it is given. Nothing crypto-related runs here. - **Owns the plumbing** (Framekit): Creates the iframe, opens a locked-down postMessage channel, runs the handshake, ships config in, surfaces events out. No HTTP, no UI. Transport only. - **Owns the experience** (Orchestrator): The entire ramp UI (auth, KYC, payments, receipts) plus its own API calls. A separate hosted deployment per environment. ## The bridge lifecycle 1. **Iframe construction**: Framekit creates an