> 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/pricing-and-access/how-do-we-get-started.md).

# How do we get started?

Getting started with GLBNXT is straightforward. The first step is a conversation with our team to understand your organisation's needs, identify the right plan, and map out what your deployment will look like. From there, onboarding moves quickly. Workspace deployments are typically up and running within five days, including SSO integration, user access configuration, and initial setup.

If you are not yet ready to commit and want to explore the platform first, ask about our pilot programme. It is the best way to see GLBNXT working against your actual use cases, with our team alongside you throughout.

To get started, visit [glbnxt.com](https://www.glbnxt.com) and get in touch with our team directly. We will take it from there.


---

# 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/pricing-and-access/how-do-we-get-started.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.
