> 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/what-teams-build-and-host.md). # What teams build and host The applications organisations host on GLBNXT Platform range from small internal tools to client-facing products. A few typical examples: ### A live KPI dashboard An operations manager uses a coding agent to build a dashboard that shows order volumes, delivery times and backlog per region. The dashboard reads directly from the shared database in the GLBNXT environment, so the figures are always current and match what other teams see. ### An internal tool on top of AI models A claims team builds a tool that summarises incoming claims and suggests a category. The tool calls the AI models in the GLBNXT environment, so claim data never leaves the EU and is never sent to a public AI service. ### A custom frontend for an automated workflow A development team has an automation workflow that processes supplier invoices. To let the finance team review exceptions, they build a simple web application on top of it and host it alongside the workflow. ### A client portal An agency builds a portal where its clients can view project status and download reports. The portal runs on GLBNXT Platform with its own secure web address, connected to the agency's project data. ### What they have in common In each example, the application was quick to build. What made it useful was where it ran: next to the data and models it needed, behind the right access, without anyone having to set up or maintain infrastructure. --- # 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/what-teams-build-and-host.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.