# 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.
--->
CLI/API/Portal Support
: You can use the CLI and API to access the complete DBaaS features. The Portal
  has partial coverage now, but we are continually working to bring it full
  DBaaS functionality.

Cross DBaaS Service Integration
: Integration between DBaaS services is not currently possible.

Multi-Zone Setup and Geo-Replication
: All services that support replication from their protocol can be deployed
  with geo-redundancy from the CLI with the integration capabilities. Read more
  about this feature in the specifics of each service. However, forks are
  possible across zones, which enables you to start a copy of a service from
  one zone in another zone.

Data Migration
: Migrating from an existing non-Exoscale DBaaS is possible only from the
  Portal and applies to SQL-based services only.

Service Plans Restrictions 
: Access to certain plans (e.g., Business, Premium) requires
  activation by the support team. Requests can be made during service
  creation.
  
<!--- Template Guidance 
If there are additional specific limitations, describe below the table.
--->


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

| Usage                                                  | Quota                  |
|--------------------------------------------------------|------------------------|
| DBaaS services overall                                 | 10                     |


## Availability
DBaaS is available in all zones.

__Data Services__

| Service             | Name         |
|---------------------|--------------|
| Managed PostgreSQL  | `pg`         |
| Managed MySQL       | `mysql`      |
| Managed Kafka       | `kafka`      |
| Managed OpenSearch  | `opensearch` |
| Managed Valkey      | `valkey`     |
| Managed Grafana     | `grafana`    |
| Managed Thanos      | `thanos`     |

<!--- 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" >}} |
--->