> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/skyone-autosky/skyone-autosky/skyone-autosky-platform/environments.md).

# Environments

While the Account serves as the organizational foundation of the business, the Environment is the platform's strictly operational layer. This is the structure configured within the admin dashboard where you manage how users access your company's applications and servers.

To meet different infrastructure needs, Skyone Autosky provides two main types of environments:

* [Micro environment](/english/skyone-autosky/skyone-autosky/skyone-autosky-platform/environments/micro-environment.md): Designed for more predictable operations. It uses a server with fixed resources and simplifies management, as it does not require publishing images to create templates.
* [Scaling environment](/english/skyone-autosky/skyone-autosky/skyone-autosky-platform/environments/scaling-environment.md):  Focused on elasticity and cost optimization. It operates entirely on demand, meaning the infrastructure (such as the number of active machines) and licenses vary dynamically, scaling up or down based on the number of concurrent users.

{% hint style="info" %}
The following pages detail the actions and configurations you can perform within each environment.
{% endhint %}

In addition to the architecture type, each **environment** has customizable operating rules, such as the selected virtualizer, the number of access licenses, the network domain, and the authentication method (you can configure access with or without mandatory Active Directory validation). Operating hours are also flexible; the environment can run continuously (**24/7**) or be automatically managed by a **scheduling bot**.

With this in mind, accessing the Environments page gives you a real-time management view of your entire operation. On this screen, information and tools are organized as follows:

* **Environment Name:** The clear identification of each configured structure.
* **Type:** A visual indicator showing whether the environment is Micro or Scaling.
* **Status:** Displays the current state of the environment (e.g., active, in maintenance, or shut down by the scheduling bot).
* **Virtualizer and Domain:** Displays the technical delivery and security components configured for that structure.
* **Licenses and Schedules:** Shows the contracted concurrent access limit and the defined operating hours for that environment.
* **Actions / Management:** Interactive shortcuts that allow you to edit environment settings, manage associated users, track resource consumption, and apply updates directly.

<figure><img src="/files/01hG1V9UeellWVym4r8W" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.skyone.cloud/english/skyone-autosky/skyone-autosky/skyone-autosky-platform/environments.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.