> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/automate-protect-and-extend/integrations-and-apis/inuvika.md). # Inuvika Integration with VergeOS Inuvika OVD Enterprise integration with VergeOS delivers virtual desktop infrastructure (VDI) and application delivery, enabling secure remote access to Windows and Linux desktops and applications. ## Overview The Inuvika OVD Enterprise integration with VergeOS provides a comprehensive virtual desktop infrastructure (VDI) and application delivery solution. This integration combines VergeOS's efficient virtualization platform with Inuvika's secure application and desktop delivery capabilities, enabling organizations to deploy virtual workspaces that can be accessed from any device. ## Key Features * Secure delivery of Windows and Linux applications and desktops through Inuvika OVD Enterprise * Simplified management of virtual desktop infrastructure on VergeOS * Multi-tenant architecture supporting various deployment scenarios * Centralized administration through intuitive management consoles * Seamless user experience with integrated single sign-on capabilities * High-performance remote display protocol optimized for various network conditions ## Integration Benefits * **Resource Optimization**: Leverages VergeOS's efficient resource management to maximize virtual desktop density * **Improved Security**: Applications and data remain in the data center while only screen updates are sent to endpoints * **Operational Efficiency**: Centralized management reduces administrative overhead * **Enhanced User Experience**: Consistent application access regardless of device or location * **Cost Reduction**: Lower hardware requirements for end-user devices and reduced management costs * **Simplified Deployment**: Purpose-built integration streamlines implementation process ## Architecture The integration architecture consists of: * **VergeOS Platform**: Provides the virtualization infrastructure for hosting the Inuvika components * **Inuvika OVD Enterprise**: Delivers virtual applications and desktops to end-users * **Application Servers**: Windows or Linux virtual machines hosting published applications * **Session Managers**: Manages user connections and session distribution * **Web Portal**: Provides user access to published applications and desktops ## Documentation and Resources For detailed implementation instructions and configuration guidance, please refer to: * [Inuvika Documentation Portal](https://docs.inuvika.com/) - Complete documentation for Inuvika OVD Enterprise ## Support If you encounter issues with the Inuvika integration or have questions about implementation: * [Inuvika Support](https://www.inuvika.com/support/) - Official support from Inuvika * [VergeOS Support](/support-and-services.md) - Technical assistance for VergeOS environments --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.verge.io/automate-protect-and-extend/integrations-and-apis/inuvika.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.