> 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/one-place-for-your-data.md).

# One place for your data

Most organisations don't have a shortage of applications. They have a shortage of connections between them. Every tool keeps its own copy of the data, every dashboard has its own export, and nobody is sure which number is the right one.

GLBNXT Platform takes a different approach: keep your data in one place and connect many applications to it.

### Many applications, one source

When your data lives in your GLBNXT environment, every application you host can work with the same source:

* A **dashboard** shows live figures from the same database your operations team writes to.
* An **internal tool** built with a coding agent reads and updates the same customer records.
* An **AI assistant** answers questions from the same knowledge base your documents are indexed into.
* A **workflow** processes incoming information and stores the result where every other application can use it.

Data is not copied between systems, so it is not duplicated, outdated or lost track of.

### Environment variables: the connection layer

Applications connect to everything around them through **environment variables**: settings you give an application when you deploy it, such as the address of a database, the endpoint of a model or the key of an external service.

This keeps the application itself independent of where it runs. The same application can connect to:

* **Platform services** in your environment, such as databases, vector stores and AI models.
* **Platform applications**, such as workflow automation, as a backend for your own frontend.
* **External tools and APIs** your organisation already uses, such as a CRM, a ticketing system or a payment provider.

To connect an application to a different source, you change its settings. The code stays the same. See [Set environment variables](https://docs.glbnxt.com/configure-glbnxt/platform-configuration/application-management/my-apps/set-environment-variables) for how this works in the portal.


---

# 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/one-place-for-your-data.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.