> 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/create-your-product.md).

# Create your Project

**Projects are the deployable units made up of images and their configuration you're going to manage through the platform.**

|                  | Versioned Project            | Versioned Project                   | Versionless Project              |
| ---------------- | ---------------------------- | ----------------------------------- | -------------------------------- |
| **Version Type** | Rolling                      | Incremental                         | ❌                                |
| **Rollbacks**    | ❌                            | ✅                                   | ❌                                |
| **History**      | Previous version overwritten | Image and configuration inheritance | ❌                                |
| **Ideal for**    | Nightly Versions             | Production                          | Testing, Single-container stacks |

The different project types have different deployment capabilities. For more details about the differences, check out the [**Components**](/basics/components.md#deployment) section.

### **Versionless project**

Versionless projects have one abstracted-away version and cannot be rolled back. These are mostly useful for testing purposes.

### **Versioned project**

Versioned projects have two types of versions: rolling and incremental. You can define one version per versioned project as default. That'll be the version future versioned projects will inherit images and configurations later until you set another one as default.

#### **Rolling Version**

Rolling versions are similar to simple projects except they’re perfect for continuous delivery. They’re always mutable but contrary to incremental projects they aren’t hierarchic and lack a version number.

#### **Incremental Version**

Incremental versions are hierarchical. They can have a child version and once a deployment is successful, the deployed versions, the environment variables, and the deployed images can never be modified. This guarantees you’re able to roll back the deployed version and reinstate the last functional one if any error occurs to avoid downtime.

{% hint style="info" %}
**Versioned projects can have both rolling and incremental versions.**
{% endhint %}


---

# 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/create-your-product.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.