> For the complete documentation index, see [llms.txt](https://docs.motar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motar.com/hardware-requirements/compatible-devices.md). # Compatible Devices Our platform is designed with flexibility in mind, supporting a wide range of hosting environments and XR hardware. While the content management system can run on virtually any server setup, **XR functionality** is delivered through a dedicated companion app (**MOTAR 3D**) compatible with select headsets. Additionally, support for **peripherals** can be customized to fit your application's needs. **Hosting Environment** * The CMS can be self-hosted on nearly any system, from lightweight single-board computers like the Raspberry Pi to enterprise-scale cloud servers. * No platform-specific dependencies—compatible with Linux, Windows, macOS, and containerized environments (e.g., Docker). *** **MOTAR 3D Compatibility** Our companion XR app currently supports the following standalone headsets: * **Meta Quest 2** * **Meta Quest 3 / 3s** * **Meta Quest Pro** * **HTC Vive Focus 3** * **HTC Vive Focus Vision** *** **Optional Peripheral Support** You can optionally configure support for external peripherals based on your hosted experience's needs. Examples include: * Joysticks / Gamepads * Bluetooth controllers * Custom XR input devices *(manually integrated)* > ⚙️ Note: Peripheral integration must be implemented at the application level during development or deployment of your hosted XR experience. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.motar.com/hardware-requirements/compatible-devices.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.