Skip to main content

Release Readiness

Telemus AI uses security, reliability, and platform checks when assessing a release candidate. A passing local check is not a guarantee of compatibility with every device, provider, file, or network. Account signup and Stripe subscriptions are public. Application availability is specific to each platform and release channel; see Get the app and Release Depth and Public Readiness.

What release checks cover​

  • Security and privacy: Review of application packages for unintended credentials, sensitive diagnostic data, and unsupported network settings.
  • Installation and updates: Checks of package contents, signing, installation, first-run behavior, and supported update paths for the target platform.
  • Performance and comfort: Testing against the relevant device's performance expectations, including extended use where appropriate.
  • Workspace reliability: Recovery, export, permissions, and failure handling for supported workflows.
  • Documentation: Comparison of documented behavior with the capabilities available in the build.

Simulated tests and local checks provide useful evidence, but they do not replace real device, account, service, and installation testing. Availability is announced for a specific release and platform rather than inferred from these docs.

Installing an invited Quest testing build​

Use the release-channel invitation and installation instructions supplied by Telemus. Join with the same Meta account used on your headset, confirm that your Quest model is supported, then look in the headset's Store or Library → My Preview Apps.

The mobile Meta Horizon app may help accept an invitation or inspect account state. Installation and launch of the Quest build take place on the headset. If an invited build is unavailable, contact Telemus support with your Quest model and release channel. Do not substitute an unverified package from another source. A Quest channel invitation is separate from public Telemus account signup and billing.

Windows builds​

Start with Get the app and use the Windows installer published for your account and release channel. If no Windows download is listed, contact support for availability before subscribing for that platform. A direct-download installer does not by itself indicate Microsoft Store availability or certification. See the installation guide.

Reporting a problem​

Use the supported support-bundle or email-draft workflow where available. Review the material before sharing and remove passwords, tokens, pairing URLs, and private content. Include the application version, platform, visible error, and steps needed to reproduce the issue.

If a workspace fails to resume, preserve existing recovery data and follow the reported guidance. Avoid repeated broad repairs or manual storage changes merely to clear a warning. See Troubleshooting and Continuity and Recovery.