# Limits and Quotas

## Limits
<!--- Template Guidance 
A table with hard system limits of the service.
The difference with quotas is that these cannot be raised at all.
--->
The following table shows which limits are enforced on Compute usage.
It also highlights some of the characteristics of the product:

Instance Quotas
: Organizations can create up to 20 instances. Quota increases can be requested
  via the Exoscale Portal.

Special Instance Types
: Access to certain instance types (e.g., GPU, Mega, Titan, Jumbo) requires
  activation by the support team. Requests can be made during instance
  creation.

vTPM and Secureboot
: This setting conflicts with netboot profiles as those are not signed and will
  not boot on an instance with Secureboot enabled.

Zone Constraints
: Instances and Instance Pools are confined to a single zone and cannot be
  migrated across zones post-creation.

Elastic Ips
: Organizations are initially limited to 5 Elastic IPs. Instances sharing an
  Elastic IP cannot communicate with each other using that IP.

Block Storage Attachments
: A maximum of 5 block storage volumes can be attached to a single instance by
  default.


## Quotas
<!--- Template Guidance 
A table with the quotas of the service.
Below is an example for SOS. Even a single line in the table is OK.
--->
Compute Instances 
: Are initially limited to 20 per organization. You can ask for a quota increase in the 
[quotas section](https://portal.exoscale.com/organization/quotas/) of the web portal.


GPU Quotas
: GPU instance deployment is controlled through GPU quotas, which are managed per GPU type. By default, newly created organizations receive a quota of 0 for all GPU types. If you require GPU resources, you can request additional quota by opening a Support ticket. You can view your current GPU quotas using the Exoscale CLI:
``` bash 
exo api list-quotas 
```


> [!NOTE]
> GPU quotas are operational limits that authorize your organization to deploy GPU instances. They do not reserve GPU capacity or guarantee hardware availability.
> GPU quotas may be reviewed and adjusted over time based on platform capacity and resource usage.
> Existing running GPU instances are not affected if your GPU quota is reduced. 

> [!NOTE]
> **Need guaranteed GPU capacity?**
> If your workloads require guaranteed GPU availability, contact us via a Support ticket to discuss GPU Capacity Reservations through a Volume Commitment Contract.

Specific Instance
: type families as GPU and bigger instance types as e.g. Mega, Titan, and Jumbo, need to be enabled by our support team. You can ask for their activation directly in the instance creation view.


## Availability
Instances are available in all zones.

<!--- Template Guidance 
Only include a table if the service is NOT available in all zones.
The table should still list all zones and use checkmarks or crosses to indicate availability.
We want to avoid any doubt about whether a service is available in a given zone.
--->

<!--- Example Table 
| Zone                                     | Country      | City      | Availability         |
| :---                                     | :---         | :---      | :---:                |
| {{< icon flag-at-4x3 >}} __`at-vie-1`__  | Austria      | Vienna    | {{< icon "check" >}} |
| {{< icon flag-at-4x3 >}} __`at-vie-2`__  | Austria      | Vienna    | {{< icon "check" >}} |
| {{< icon flag-bg-4x3 >}} __`bg-sof-1`__  | Bulgaria     | Sofia     | {{< icon "check" >}} |
| {{< icon flag-hr-4x3 >}} __`hr-zag-1`__  | Croatia      | Zagreb    | {{< icon "check" >}} |
| {{< icon flag-de-4x3 >}} __`de-fra-1`__  | Germany      | Frankfurt | {{< icon "check" >}} |
| {{< icon flag-de-4x3 >}} __`de-muc-1`__  | Germany      | Munich    | {{< icon "ban" >}}   |
| {{< icon flag-ch-4x3 >}} __`ch-gva-2`__  | Switzerland  | Geneva    | {{< icon "check" >}} |
| {{< icon flag-ch-4x3 >}} __`ch-dk-2`__   | Switzerland  | Zurich    | {{< icon "check" >}} |
--->

