> 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/general/is-glbnxt-built-on-open-source-technology.md).

# Is GLBNXT built on open-source technology?

Yes. GLBNXT is built on a foundation of proven open-source components, which is a deliberate choice rather than a cost-saving measure. Open-source technology means the underlying code can be independently verified, audited, and scrutinised. For organisations with strict security and compliance requirements, this level of transparency matters. You are not relying on the promises of a closed, proprietary system that you cannot inspect.

Building on open standards also means GLBNXT avoids the vendor lock-in that comes with fully proprietary platforms. Your data, your configurations, and your workflows are not trapped inside a system that only one company controls.

At the same time, GLBNXT is not a self-hosted open-source project that requires your team to manage and maintain it. The platform is delivered as a fully managed enterprise service, with the reliability, support, and security controls that organisations in regulated industries expect. You get the transparency benefits of open source with the operational simplicity of a managed platform.


---

# 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/general/is-glbnxt-built-on-open-source-technology.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.
