# Awell platform overview
URL: https://docs.awellhealth.com/docs/get-started/awell-platform-overview

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



Awell is one platform with five parts, and each role works mainly in one of them.

## What each part is for, and who works in it [#what-each-part-is-for-and-who-works-in-it]

| Part                      | What happens there                                                                           | Who uses it                |
| ------------------------- | -------------------------------------------------------------------------------------------- | -------------------------- |
| **Awell Studio**          | Design, build, and publish care flows. Low-code, no programming.                             | Clinical and product teams |
| **Awell Care**            | Deliver published care flows day to day: see patients, act on what needs doing.              | Care teams                 |
| **Awell Panels**          | Work a whole population at once: live lists of patients and tasks, filtered and prioritized. | Care teams                 |
| **Awell Orchestration**   | The engine that runs published care flows, plus the API for integrations.                    | Engineers                  |
| **Organization settings** | Team members, roles, branding, and developer access.                                         | Whoever owns the account   |

## Studio designs the care flow, Orchestration runs it [#studio-designs-the-care-flow-orchestration-runs-it]

In **Studio**, the care flow author decides what should happen: the steps, who does what, what to
collect, and the rules for what comes next. Design never touches a real patient.

Once the care flow is published, **Orchestration** takes over. It enrolls patients and handles the
variability the author encoded: evaluating conditions, activating and discarding branches, scheduling
activities, and assigning each one to the right person. It runs continuously in the background without
anyone driving it.

## Care shows one patient, Panels shows the population [#care-shows-one-patient-panels-shows-the-population]

Both are places where care gets delivered, and they answer different questions.

**Awell Care** answers "what does this patient need next": one patient at a time, with their activities
and history in front of the person doing the work.

**Awell Panels** answers "who needs attention first": a live list of patients or tasks across a whole
population, filtered, sorted and grouped to suit the team. See
[What Panels is](/docs/run-care-flows/what-is-panels).

## Activities reach people through hosted pages or a custom interface [#activities-reach-people-through-hosted-pages-or-a-custom-interface]

Once a care flow is running, activities need to reach real people. A care flow can use either of these,
or both:

* **Awell-hosted pages.** Awell renders the activity; the organization brands it and shares a link.
* **A custom interface.** Built on the Orchestration API, or with activities embedded through Navi.

See **Embed & host** for that decision.

## Which part to use depends on the job [#which-part-to-use-depends-on-the-job]

* **Designing a care process** → Studio. Continue to **Design care flows**.
* **Working with patients day to day** → Awell Care or Panels. Continue to **Care delivery**.
* **Integrating Awell with other systems** → the Orchestration API. Continue to
  **Connect systems**.

## Next steps [#next-steps]

**Next:** **Key terms** — the vocabulary the rest of these docs assume.