> 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/platform/hosting-applications/why-host-on-glbnxt-platform.md). # Why host on GLBNXT Platform GLBNXT Platform gives the applications your teams build a home: the same managed, sovereign environment that already runs your data, your AI models and your platform services. You bring the application. GLBNXT runs it. ### Next to your data and models An application is only as useful as what it can connect to. On GLBNXT Platform, your applications run in the same environment as your databases, vector stores, AI models and workflow automation. They work with your data where it already lives, instead of copying it to wherever the application happens to be hosted. ### Inside the same guardrails Your own applications sit alongside the applications GLBNXT manages for you, under the same governance: * **European data sovereignty**: everything runs on EU infrastructure, under EU jurisdiction. * **One audit trail**: activity around your applications is recorded in the same audit log as the rest of your environment. * **Controlled access**: only administrators of your organisation deploy and change applications. ### No infrastructure to manage Your team focuses on the application. GLBNXT provides the web address, the certificate, the networking and the monitoring, and keeps the application running. There are no servers to configure, no clusters to maintain and no on-call rota for infrastructure. ### From prototype to production without moving A prototype built with a coding agent and a production application used by hundreds of people can run in the same place. When an experiment proves its value, there is no migration project. You deploy a new version and keep going. --- # 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/platform/hosting-applications/why-host-on-glbnxt-platform.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.