Required permissions

To create this project through the API, the user or organization API Key needs database.create on organization:*. After creation, use the returned project ID:

An owner user session has full access. For assistant or member, grant exactly the corresponding permission; an organization API Key uses the same format in permissions.resources. Creation does not require project.read, but automation that also reads the project needs that scope separately.

Prerequisites

• created and verified account
• signed in to the console

Step 1: Choose the project type

In the console, click Create project and select MariaDB Database.

What is included

• managed MariaDB
• versions 10 and 11
• 3 fixed instances
• automatic failover
• InnoDB engine by default
• connection with mandatory TLS, through a ready URI and individual parameters

Step 2: Select the plan

Choose the plan and billing model that make sense for the database. MariaDB is available starting at db-starter (there is no db-free for MariaDB). Because the database always uses 3 instances, the plan price is charged for each of them, and storage is charged per GB on each instance. See the prices in Database Plans.

Payment models

Important: Database storage is always persistent. Even with the database stopped, the storage still exists and is billed.

Step 3: Configure basic information

Project name

• minimum: 6 characters
• maximum: 32 characters
• only lowercase letters, numbers, and hyphens

Description

Optional field for organization in the console.

Step 4: Configure the database

MariaDB version

Choose the desired version from:

• MariaDB 10
• MariaDB 11

Default user and database

• username: app
• database name: app

Password

The password is generated by the platform and shown only once, at the end of creation. Store it safely because it will be used to connect the application or external clients. If you lose it, generate a new one in the project edit page.

Step 5: Replicas and failover

MariaDB on Zenifra uses a fixed 3-instance topology:

• 1 primary instance, which receives write and read connections
• 2 replicas, which keep a copy of the data and can take over if the primary fails

The connection provided in the console points to the primary instance. This quantity cannot be changed later.

Step 6: Storage

• minimum: 1 GB
• maximum: 250 GB

Important rules:

• storage can increase
• storage can never decrease
• changes are only available in hourly billing; in monthly and yearly billing, capacity is fixed for the contract term
• increasing storage can cause a few minutes of downtime

Step 7: Finish creation

1. review the settings
2. click Create Project
3. wait for the database provisioning

After creation

The console will show:

• project ID
• host (mariadb-<project-id>.managed.zenifra.com)
• port
• username app
• database name app
• ready-to-copy full URI, in the format mariadb://app:<password>@<host>:<port>/app?ssl=true

The password appears only on that screen. Afterward, the console shows the URI with a masked password.

Backups: Zenifra does not currently provide automatic backups or console restore. Export your data periodically with mariadb-dump/mysqldump and store the copies outside the project.

Next steps

• How to Change MariaDB Settings
• Database Plans
• Payment Settings