> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/get-started/onboarding-to-ox/prerequisites-and-access/ox-deployment/saas-deployment.md).

# SaaS Deployment

OX SaaS provides the simplest way to deploy and use OX. The OX platform is hosted and managed by OX Security, so there is no OX infrastructure to install, operate, or maintain in your environment.

With OX SaaS, you can quickly get started by accessing the OX web application and connecting your development ecosystem. OX manages the underlying platform, including maintenance and updates, reducing the operational effort required from your organization.

SaaS deployment is recommended for organizations that can connect their development tools and environments to the OX cloud platform and do not require OX to be hosted within their own infrastructure.

### Connectivity

OX SaaS connects to the systems and services in your development ecosystem, such as source control management (SCM) systems and other development tools.

For systems that are publicly accessible, OX can connect directly using the relevant connector.

If you have resources that are hosted in a private network or cannot be accessed directly by OX SaaS, you can deploy OX Broker in your environment. OX Broker enables OX SaaS to communicate with these resources without making them publicly accessible. For more information, see [OX Broker](/get-started/onboarding-to-ox/prerequisites-and-access/ox-deployment/ox-broker.md).

### Get started

There is no OX platform infrastructure to deploy before you begin. Once your OX SaaS environment is available, you can start onboarding your organization and connecting your development ecosystem. For more information, see [Onboarding to OX](/get-started/onboarding-to-ox.md).


---

# 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.ox.security/get-started/onboarding-to-ox/prerequisites-and-access/ox-deployment/saas-deployment.md?ask=<question>&goal=<user_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.