> 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.

# Go-live

Before moving your branded white-label safety application from staging to
production, work through the checks below with your AURA contact.

## White-label checklist

* **Store accounts** - Apple Developer and Google Play account setup is complete
  and accessible to the release team. The per-store version, listing status,
  countries, approval owner, and rollout plan are recorded.
* **Brand assets** - app name, icons, splash screens, and required
  store assets are final.
* **Payment setup** - merchant, gateway, and subscription configuration have
  been verified in staging.
* **Customer onboarding** - signup, login, subscription activation, and support
  journeys are tested, including each enabled language and individual/family
  plan variant.
* **Coverage** - the response types sold in each market have been checked at
  representative customer locations, and unsupported locations have a clear
  journey.
* **Configured channels** - phone, panic button, wearable, notifications,
  deep links, and test mode are validated where enabled.
* **Panic journey** - live callout creation, callout tracking, and cancellation
  are validated. Use the **Responder Simulator** in the staging portal to drive
  test callouts through the full responder lifecycle; resolution reports are
  reviewed in the AURA portal.
* **Production release** - production credentials, base URLs, store listings,
  and support contacts are confirmed.

See [Configuration workbook](/white-label/configuration-workbook) for the
decision register and
[Release & store operations](/white-label/deploy/release-operations) for the
ongoing release process.