> For the complete documentation index, see [llms.txt](https://docs.cosmocloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cosmocloud.io/resources/environments/environment-tier-types.md).

# Environment Tier Types

An Environment's **Tier** tells Cosmocloud the expected scale and resources needed for that environment. A combination of Vertical Scaling or Horizontal scaling can be used to get your required tier.

{% hint style="info" %}
Autoscaling is currently a per-request feature, please reach out to [<mark style="color:blue;">**Cosmocloud Support**</mark>](mailto:support@cosmocloud.io) if you need it.
{% endhint %}

## Vertical Scaling

You can vertically scale your applications from switching from one Tier type to another where you have more CPU and RAM resources available -

| Tier Type | Resources              | Description                                                                      |
| --------- | ---------------------- | -------------------------------------------------------------------------------- |
| Shared    | Shared CPU & RAM       | Meant for trials, POCs and testing environments.                                 |
| Low       | Dedicated vCPU and RAM | Meant for low traffic web apps with small scale or staging environments.         |
| Power     | 2x resources than Low  | Meant for medium to high traffic applications for production ready envrionments. |
| Boost     | 4x resources than Low  | Meant for High CPU and RAM utilisation for heavy resources and heavy load.       |

## Horizontal Scaling

You can increase the number of instances per tier type when you need to horizontally scale your application environment. The configurations available are -

{% hint style="info" %}
For actual pricing based on Cloud Provider and Region, please [<mark style="color:blue;">**check this page**</mark>](https://cosmocloud.io/pricing).
{% endhint %}

<table data-full-width="true"><thead><tr><th>Tier Type</th><th>Tier</th><th>Instances Scale</th><th>Max # of API calls (per day)</th><th data-type="checkbox">High Availability</th></tr></thead><tbody><tr><td>Shared</td><td>(S0) Shared-0</td><td>Shared, 1x</td><td>1000</td><td>false</td></tr><tr><td>Shared</td><td>(S1) Shared-1</td><td>Shared, 3x</td><td>3000</td><td>false</td></tr><tr><td>Shared</td><td>(S2) Shared-2</td><td>Shared, 5x</td><td>5000</td><td>false</td></tr><tr><td>Low</td><td>(L0) Low-0</td><td>1x</td><td>No cap</td><td>false</td></tr><tr><td>Low</td><td>(L1) Low-1</td><td>3x</td><td>No cap</td><td>true</td></tr><tr><td>Low</td><td>(L2) Low-2</td><td>5x</td><td>No cap</td><td>true</td></tr><tr><td>Low</td><td>(L3) Low-3</td><td>7x</td><td>No cap</td><td>true</td></tr><tr><td>Power</td><td>(P0) Power-0</td><td>1x</td><td>No cap</td><td>false</td></tr><tr><td>Power</td><td>(P1) Power-1</td><td>3x</td><td>No cap</td><td>true</td></tr><tr><td>Power</td><td>(P2) Power-2</td><td>5x</td><td>No cap</td><td>true</td></tr><tr><td>Power</td><td>(P3) Power-3</td><td>7x</td><td>No cap</td><td>true</td></tr><tr><td>Boost</td><td>(B0) Boost-0</td><td>1x</td><td>No cap</td><td>false</td></tr><tr><td>Boost</td><td>(B1) Boost-1</td><td>3x</td><td>No cap</td><td>true</td></tr><tr><td>Boost</td><td>(B2) Boost-2</td><td>5x</td><td>No cap</td><td>true</td></tr><tr><td>Boost</td><td>(B3) Boost-3</td><td>7x</td><td>No cap</td><td>true</td></tr></tbody></table>


---

# 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:

```
GET https://docs.cosmocloud.io/resources/environments/environment-tier-types.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.