> For the complete documentation index, see [llms.txt](https://docs.glbnxt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glbnxt.com/faq/security-and-data-sovereignity/can-we-deploy-glbnxt-in-our-own-private-cloud-or-on-premise-environment.md).

# Can we deploy GLBNXT in our own private cloud or on-premise environment?

Yes. GLBNXT is cloud agnostic and can be deployed across virtually any cloud environment or on-premise infrastructure. If your organisation has a strong preference for a specific cloud provider or requires installation within your own facilities, that is technically possible.

However, it is worth being straightforward about what that involves. In most situations, a private cloud or on-premise deployment is not the most beneficial option for clients. Replicating the security standards, maintenance levels, redundancy, and operational rigour that GLBNXT delivers within its managed environment requires significant investment. Running a private or on-premise deployment on par with those requirements is in most cases an extremely expensive undertaking, both in terms of infrastructure costs and the internal technical resource needed to operate and maintain it to the same standard.

For the vast majority of organisations, the GLBNXT managed environment offers a higher level of security and operational reliability than a self-managed deployment could practically deliver, at a fraction of the cost and complexity.

If your organisation has specific requirements that you believe make a private or on-premise deployment the right choice, we are happy to have that conversation. Contact the GLBNXT team directly to discuss your situation and explore the options available.


---

# 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.glbnxt.com/faq/security-and-data-sovereignity/can-we-deploy-glbnxt-in-our-own-private-cloud-or-on-premise-environment.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.
