> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/deploy-to-your-cloud/create-an-environment.md).

# Create an Environment

Register an environment in the DuploCloud Console so your portal gets its license, by hand or through the Cloud Deployment Agent.

An **environment** is one DuploCloud portal running in your cloud account. You register it in the [DuploCloud Console](https://docs.duplocloud.com/docs/concepts/console.md), which issues the environment license bound to the portal's hostname. Per-environment agents are also bought for specific environments.

You can create an environment in two ways:

* **Automatically, with the Cloud Deployment Agent.** When you deploy your portal from the DevKit, the agent registers the environment for you.
* **By hand, in the Console.** Open **Environments** and click **Add environment**.

{% hint style="info" %}
This page is being written. Until it's ready, see [Get an environment license for your own portal](https://docs.duplocloud.com/docs/concepts/console/licensing.md#get-an-environment-license-for-your-own-portal).
{% 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.duplocloud.com/docs/deploy-to-your-cloud/create-an-environment.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.
