> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.3/installation-and-settings/deployment-types/saas-deployment.md). # SaaS Deployment Clients interested in the OvalEdge SaaS offering should work with the OvalEdge GCS Team and complete the SaaS Installation [Questionnaire](https://share.hsforms.com/15BRPOvsvRACrnF5wyTIKjg5a61o). After completing the questionnaire, the client should receive a welcome email from OvalEdge containing the client's environment details within a week. ## Set up SaaS Bridge Client The Bridge Client enables secure communication with the OvalEdge platform, ensuring reliable data integration and smooth operational workflows. Proper setup of the Bridge Client is essential for maintaining consistent connectivity and seamless platform performance. Refer to the following page for detailed instructions: * [Bridge Client Setup](/release8.3/installation-and-settings/deployment-types/saas-deployment/bridge-client-setup.md) For any support required for installing the Bridge Client, please contact the OvalEdge GCS Team. ## SaaS Connectivity Test After setting up the SaaS environment and SaaS Bridge Client, the OvalEdge GCS Team will work with the Client to establish the initial connection. *** Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA. --- # 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.ovaledge.com/release8.3/installation-and-settings/deployment-types/saas-deployment.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.