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	Mobile apps, employee safety, roadside assistance, and wearables	Your customer experience and backend integration	Customer, subscription, callout, tracking, and response APIs
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	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.

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, callout tracking, or subscription management.
White-label combines a pre-built app with the same Panic API. Your backend can still provision customers and subscriptions programmatically.

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

Read the relevant product overview.
Follow the end-to-end integration journey.
Build and test in staging.
Complete production readiness and the product-specific go-live checklist.