> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/guardian/getting-started.md).

# Getting Started

Choose a path get started with Guardian.

{% hint style="info" %}
**Not sure where to start?**

If you just want to see Guardian in action with minimal setup, we recommend the [**Managed Guardian Service**](https://www.climission.com/mgs?utm_source=guardian-docs), a SaaS offering from [Climission](https://www.climission.com/?utc_source=guardian-docs) who are co-maintainers of this project. If you want to run your own environment quickly, start with **Docker Quickstart**. If you're planning to fork, extend, or contribute to Guardian itself, go with **Build from Source**.
{% endhint %}

## Which path is right for you?

<table><thead><tr><th width="142.4140625">Scenario</th><th>Path</th><th>Best for</th><th>You manage</th><th width="189.2578125">Get started</th></tr></thead><tbody><tr><td><strong>Explore &#x26; evaluate</strong></td><td>Managed Guardian Service</td><td>Trying Guardian, demos, non-technical stakeholders, proof-of-concept</td><td>Nothing, its fully hosted</td><td><a href="https://www.climission.com/?utc_source=guardian">Managed Guardian Service</a></td></tr><tr><td><strong>Turn-key self-hosted</strong></td><td>Docker Quickstart</td><td>Running your own instance fast, technical evaluation, small production deployments</td><td>Your own infrastructure; Guardian handles the rest</td><td><a href="/readme.md">Guardian README#Quickstart</a></td></tr><tr><td><strong>Extend &#x26; contribute</strong></td><td>Build from Source</td><td>Forking the project, custom development, contributing to core, non-standard configurations</td><td>Dependencies, configuration, upgrades, and the running environment</td><td><a href="https://github.com/hashgraph/guardian#readme">Guardian repository README</a></td></tr></tbody></table>

### Try Guardian without operating infrastructure

Check out the [Managed Guardian Service](https://climission.com/?utm_source=guardian) for a hosted environment to request a free trial.

Choose or explore this path if you do not want to install locally or operate infrastructure or are evaluating the product.

### Run open-source Guardian

[Open-source releases](https://github.com/hashgraph/guardian/releases) are available on GitHub.

Choose one of these paths:

* **Docker containers**: Suitable for users comfortable running and configuring services. This is the fastest way to get a self-hosted instance running.
* **Build from source**: Suitable for contributors and teams needing custom changes, forking the project, or hosting a modified instance. Requires more time and operational knowledge. You manage dependencies, configuration, upgrades, and the running environment.

## Ready to install?

Continue to the [Installation Guide](/guardian/getting-started/installation-guide.md).


---

# 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://guardian.hedera.com/guardian/getting-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.