# What is Navi?
URL: https://docs.awellhealth.com/docs/embed-and-host/what-is-navi

> For the complete documentation index, see [llms.txt](https://docs.awellhealth.com/llms.txt).



**Navi** is a drop-in experience layer, embedded in a host product to take patients and care teams
through care flow activities. It carries the organization's branding, and Awell maintains it.

## Navi renders inside an app; Hosted Pages is a page of its own [#navi-renders-inside-an-app-hosted-pages-is-a-page-of-its-own]

Both are prebuilt UI for care flows, and they differ in placement:

* **[Hosted Pages](/docs/embed-and-host/overview-hosted-pages)** is a page a stakeholder is sent to,
  or an iframe, and the fastest to launch.
* **Navi** is a component rendered **inside the host app**, so the activity appears as part of that
  product rather than a page within it.

Use Navi where patients already use the host product, and Hosted Pages where they are sent a link.

## What Navi covers so the host app doesn't [#what-navi-covers-so-the-host-app-doesnt]

* **Faster to launch** than building the UI: minutes rather than weeks of bespoke work.
* **Better completion rates**, because the flows are opinionated and reduce friction.
* **Less delivery risk.** Security, compliance and edge-case handling come with it and stay maintained.
* **Change without shipping.** Configure steps, copy and rules in Studio without redeploying the app.
* **Extensible.** SDKs and hooks for monitoring, responsive behavior and analytics.

If care flow logic lives in the app, every clinical change is a release; with Navi it's a Studio change.

## Design in Studio, embed with a publishable key [#design-in-studio-embed-with-a-publishable-key]

1. Design the care flow in Studio.
2. Embed Navi in the host product with a publishable key.
3. Navi renders whatever activities the care flow produces for that person.

## Next steps [#next-steps]

**Next:** [Quickstart](/docs/embed-and-host/quickstart) to get something rendering.