> 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.md). # Deployment Types OvalEdge supports multiple deployment options, including on-premises, within the customer’s cloud infrastructure (AWS, Azure, GCP), or as a SaaS solution. In both on-premises and cloud deployments, OvalEdge is typically installed on virtual machines or in containerized environments. For cloud deployments, OvalEdge recommends using managed databases such as Amazon RDS. For on-premises deployments, customers are responsible for managing the database. Hardware specifications are determined based on the selected OvalEdge package. The Enterprise package supports a higher number of users, requiring corresponding adjustments to hardware capacity. ## OvalEdge Packages From the infrastructure perspective, listed below are the different packages available in OvalEdge. 1. **ESSENTIAL:** Up to 10 Connectors and 50 Business Users 2. **PROFESSIONAL:** Up to 25 Connectors and 500 Business Users 3. **ENTERPRISE:** 25+ Connectors, 500+ Business Users ## Deployment Types OvalEdge supports various deployment types. * Virtual Machines based deployment * Container based deployment * SaaS based deployment *** 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.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.