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

# Getting started

This is an extremely compressed guide to new users who would like to give cloud-hosted dyrector.io a look as quick as possible.

{% hint style="info" %}
Having access to a target environment (Docker or Kubernetes) is a requirement. More details [**here**](/basics/components.md#node).
{% endhint %}

1. Go to [**sign up**](https://app.dyrectorio.com/auth/register) or [**login**](https://app.dyrectorio.com).
   * If you just signed up, check the inbox of the e-mail address you added for confirmation e-mail and verify your account with the link.
2. Create a team.
3. On the nodes page [**add**](/tutorials/register-your-node.md) a new Docker or Kubernetes orchestrated node.
4. [**Add a registry**](/tutorials/add-your-registry.md) to the platform. Docker Hub is available by default. Bypass this step and step 5 by saving one of the [**Templates**](/features/templates.md) as a project.
5. [**Create a project**](/tutorials/create-your-product.md).
6. [**Add a deployment**](/tutorials/deploy-your-product.md) to your project.
7. [**Configure**](/features/configuration-management.md) the images if needed.
8. Deploy. 🎬


---

# 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.dyrector.io/tutorials/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.