> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.aurasos.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.aurasos.com/_mcp/server.

# Choose your integration path

AURA can power a safety experience inside your product, connect a property or
alarm platform to emergency response, or provide a complete branded app. Choose
the path based on who is being protected and how much of the customer experience
you want to build.

| Path                                     | Best for                                                                                  | You build                                                                 | AURA provides                                                               |
| ---------------------------------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| [People Protect](/people-protect)        | Mobile apps, employee safety, roadside assistance, and wearables                          | Your customer experience and backend integration                          | Customer, subscription, callout, tracking, and response APIs                |
| [Property Protect](/property-protect)    | Alarm platforms, monitoring companies, smart-home products, stores, and distributed sites | Site provisioning and the event-to-callout integration                    | Fixed Locations, dispatch, tracking, and responder coordination             |
| [White-label App](/white-label/overview) | Teams that want to launch a branded safety app without building the mobile experience     | Brand inputs, commercial model, store accounts, and selected integrations | The customer app, onboarding, panic journey, tracking, and release pipeline |

## Delivery channels

The product path describes what is protected. The delivery channel describes
where customers and operators interact with AURA.

| Channel         | Use it when                                                                 | Important boundary                                                          |
| --------------- | --------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| Direct API      | Your backend and user experience own the journey                            | Credentials stay on your server                                             |
| Hosted flows    | You want AURA to host selected signup, tracking, or subscription screens    | Your backend creates short-lived, purpose-specific sessions                 |
| White-label app | You need a branded iOS or Android customer app                              | Features, countries, stores, payment, and releases are configured per brand |
| AURA portal     | Operations teams need management, dispatch, or reporting tools              | Portal access and modules are provisioned separately from API access        |
| Phone or IoT    | A phone call, panic button, wearable, alarm, or other device initiates help | Numbers, device suppliers, templates, and test behaviour require onboarding |

These channels can be combined. For example, an alarm platform can create
callouts through the API while operators use the portal, or a white-label app
can support a configured panic button.

> **Note**
>
> Portal modules, phone numbers, device templates, and white-label features are
> not enabled automatically by API credentials. Confirm the required channels,
> countries, response types, and test mode with AURA during solution design.

## Direct API or hosted flow?

People Protect and Property Protect can use either approach:

* **Direct API integration** gives you control of customer registration,
  subscriptions, and callout creation inside your own backend and product.
* **Hosted flows** let AURA present selected customer-facing steps such as
  [signup](/overview/embedded-flows/customer-signup),
  [callout tracking](/overview/embedded-flows/callout-tracking), or
  [subscription management](/overview/embedded-flows/subscription-management-flow).
* **White-label** combines a pre-built app with the same Panic API. Your backend
  can still provision customers and subscriptions programmatically.

> **Note**
>
> These paths compose. A property platform can link IoT devices, a People Protect
> integration can use hosted signup, and a white-label app can use your own payment
> gateway.

## A quick decision

Choose **People Protect** when the protected subject is a person whose location
can change. Choose **Property Protect** when the protected subject is a known
site. Choose **White-label** when you need AURA to supply the end-user
application as well as the response service.

If you need both mobile and fixed-location protection, start with the dominant
customer journey and add the second callout model to the same integration.

## Next steps

1. Read the relevant product overview.
2. Follow the [end-to-end integration journey](/overview/integration-journey).
3. Build and test in staging.
4. Complete [production readiness](/overview/deploy/production-readiness) and
   the product-specific go-live checklist.