> For the complete documentation index, see [llms.txt](https://mariadb.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariadb.com/docs/mariadb-cloud/cloud-usage/launch-page.md). # Launch Page The MariaDB Cloud Provision Cloud Database page creates a new database service from a single page: topology, high availability, add-ons, provider and region, instance resources, connectivity, and adva The **Provision Cloud Database** page creates a new MariaDB Cloud service from a single page. As you build the configuration, a sticky footer shows a live estimate of the hourly and monthly cost before you deploy. Open it with **Create New Service** from the Portal Dashboard.

MariaDB Cloud Dashboard with the Create New Service button. — Create New Service on the Dashboard

Provision Cloud Database page with MariaDB Serverless selected, showing topology cards, cloud provider and region, instance resources, and a live cost estimate in the footer. — Provision Cloud Database page (Serverless)

## Topology Choose the service topology: * **MariaDB Serverless** (Pay-Per-Use) — a fully managed database that scales on demand. Best for variable traffic and cost optimization. * **MariaDB Provisioned** (Production Ready) — predictable performance with customizable resources. Best for production workloads that need consistent performance.

Topology cards for MariaDB Serverless (pay-per-use) and MariaDB Provisioned (production ready), each with a starting hourly price. — Topology selection

## High Availability For provisioned services, select a high-availability mode: * **Semi-sync** — a MaxScale proxy with automatic failover and read/write splitting. Recommended for most production workloads. * **Insync** — Galera synchronous replication across all nodes for zero-data-loss failover. Suited to compliance-critical workloads. * **None** — a single node with no replication. Not recommended for production.

High Availability tiles: Semi-sync with a MaxScale proxy, Insync with Galera-based synchronous replication, and None. — High Availability modes

## Add-ons * **Analytics (HTAP)** — adds the MariaDB Exa engine for real-time analytical queries alongside your transactional workload. Requires Semi-sync HA. Available on request: the card is labeled **On Request** until the MariaDB Cloud team enables it for your organization. See [HTAP using MariaDB Exa](/docs/mariadb-cloud/quickstart/htap-mariadb-exa.md#requesting-access-to-mariadb-exa). * **Query Result Cache** — adds an in-memory query result cache alongside your transactional workload. See [Query Result Cache](/docs/mariadb-cloud/quickstart/query-cache-gridgain-8.md). Both add-ons are currently available as a *Tech Preview*.

Add-on cards for Analytics (HTAP) and Query Result Cache, both marked Tech Preview with starting prices. — Add-ons

## Cloud provider & region Select the cloud provider (Google Cloud, AWS, or Azure), then the region and — for provisioned services — an availability zone. Each region has a scheduled maintenance window. Available regions vary by account.

Cloud provider tiles for Google Cloud, AWS, and Azure, with region and availability zone selectors. — Cloud provider, region, and availability zone

## Instance resources For **provisioned** services, choose the node size (for example, `Sky-2x8` — 2 vCPU × 8 GB RAM), the number of replicas, and, if needed, horizontal or vertical auto-scaling.

Instance Resources for a Provisioned service: node size, replicas, auto-scale nodes, storage capacity, and auto-scale storage. — Instance resources (Provisioned)

For **serverless** services, set the MCU thresholds. One MCU (MariaDB Compute Unit) equals 0.5 vCPU + 2 GB memory. Setting **Min MCUs** to 0 lets the service scale to zero when idle to reduce cost, with a brief startup delay on the next connection.

Serverless scale thresholds with Min MCUs set to 0 and Max MCUs set to 12, noting the instance scales to zero when idle. — Scale thresholds (Serverless)

Set the storage capacity and, if needed, enable storage auto-scaling. ## Secure connectivity Choose how the service accepts connections: * **IP Allowlist** — open to all, or restrict access to specific IP addresses or CIDR ranges (use **Add my IP** to add your current address). * **Private Link** — connect privately from your own VPC using AWS Private Link, Google Cloud Private Service Connect, or Azure Private Link.

Secure Connectivity options: IP Allowlist with Open to all or Restrict to specific IPs, or AWS Private Link. — Secure connectivity

## Basic attributes Select the **MariaDB Version** (with a link to its release notes) and enter a **Service Name**. The version list is the same for serverless and provisioned services, and the default version is preselected. For **serverless** services, the default version launches from a ready instance and starts in milliseconds. Choosing any other version builds the database on demand, so it takes longer to launch — the page notes this below the picker when you select one. The service is serverless either way; only the launch differs. Choosing a version other than the default requires a paid plan; on a trial with no payment method on file, only the default version is listed. ## Advanced options Optionally configure storage type, provisioned IOPS and throughput, MaxScale redundancy, NoSQL (MongoDB®-compatible) support, an SSL/TLS toggle, and the maintenance window. The available **Storage Type** depends on the cloud provider. On Azure, choose from **Premium SSD v2**, **Standard SSD**, and **Premium SSD**. Premium SSD v2 is designed for production and performance-sensitive workloads that consistently require low latency, high IOPS, and high throughput. For Premium SSD v2, you can set: * **Provisioned IOPS**: 3,000 to 80,000. The maximum depends on the storage size you selected: 500 IOPS per GB, never above 80,000. * **Throughput (MB/s)**: 125 to 2,000. The maximum depends on the IOPS you selected: 0.25 MB/s per IOPS, never above 2,000. Every service includes 3,000 IOPS and 125 MB/s at no extra cost. IOPS and throughput above those amounts increase the estimated cost shown in the footer. Existing Azure services keep their current storage type.

Advanced Options panel for Azure: storage type (Premium SSD v2, Standard SSD, or Premium SSD), provisioned IOPS, throughput, MaxScale redundancy, NoSQL support, disable SSL/TLS, and maintenance window. — Advanced options (Azure)

{% hint style="info" %} Some options — Insync high availability, the Analytics (HTAP) add-on, auto-scaling, Private Link, MaxScale redundancy, and a custom maintenance window — require the **Power** or **Power Plus** service tier. {% endhint %} ## Create the service Click **Create Service**. The new service appears on the Portal Dashboard, and a [notification](/docs/mariadb-cloud/cloud-usage/notifications.md) is sent when launch begins and when it completes.