> 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-hosting-matters-now.md). # Why hosting matters now Building software has changed. With AI coding agents such as Claude Code, Codex, Cursor, Lovable and GitHub Copilot, a working application is no longer the result of months of development. A product owner can describe a dashboard and have it running the same afternoon. An analyst can turn a spreadsheet process into an internal tool. A development team can deliver in a week what used to take a quarter. As a result, organisations are building more software than ever, and much of it is built by people outside the traditional development team. ### Building is no longer the hard part When code is cheap to write, the challenge moves to everything that comes after it: * **Where does the application run?** A prototype on a laptop helps nobody else. To be useful, an application needs a stable address that colleagues or customers can reach. * **Who can reach it?** Internal tools need to stay internal. Client-facing applications need to be secure and reliable. * **What data does it touch?** Most useful applications work with company data: customer records, documents, metrics, knowledge bases. * **Who keeps it running?** Certificates, networking, restarts and updates don't stop once the application is live. ### The risk of scattered applications Without a clear place to run them, applications end up wherever is quickest: a personal cloud account, a free hosting tier, a server under someone's desk. Each one quietly takes a copy of company data with it. Over time this creates a landscape of applications that nobody has a complete view of, running in places the organisation doesn't control, often outside the EU. The faster your teams build, the faster this landscape grows. That is why the question is no longer *whether* your organisation hosts its own applications, but *where*. --- # 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-hosting-matters-now.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.