> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/supported-integrations.md). # Supported Integrations ### POS Integrations We currently support integrations with these major Ski Industry POS types: * RTP|One * Siriusware versions 4 & 5 * InTouch * Resort suite flaik also has limited integrations with custom providers - if yours isn't listed please connect with us to discuss options. ### Servers/ MS SQL versions As part of our onboarding discovery we will work with you on this if needed. Expectation is that your current infrastructure is still within active support from your provider. ### New versions of POS Integrations As POS Providers like Active and Accesso release updates to their products, flaik endeavors to maintain compatibility. We will actively develop of our most recent release to maintain compatibility. Before taking a POS upgrade from your provider in your production environment flaik recommends testing our latest release in a test/staging environment and working with us to identify any deficiencies. --- # 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://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/supported-integrations.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.