MultiConnectMultiConnectDocs Website home
MultiConnectCloud › Database Deployments

2. Create a database

Open your project on the dashboard and create a Database deployment. The form has eight steps. Next checks each step before you move on, and any problem is shown on the step itself. The Deployment guide button on every step opens connection examples for the engine you have picked.

Step 1: Basic Info

Field What to enter
Deployment Name How the database is listed in your project, such as orders-db. 3 to 60 characters: letters, numbers, spaces, hyphens and underscores, starting with a letter or number. It must be unique in the project. This is a label only
Engine & Version MySQL 8.0, MySQL 8.4, PostgreSQL 16 or PostgreSQL 17. It cannot be changed later. To move to a new major version, take a backup, create a new database and load your data into it
Region Where both copies run. Pick the region your application runs in. It cannot be changed later. A region that cannot host the chosen plan is shown but cannot be picked
Hosting Plan How many connections the database accepts and how much storage it has. The list shows each plan's price

A project holds at most 20 deployments of all types.

Step 2: Database

This step names the database and the user that are created inside the engine.

Field What to enter
Database Name The name that goes in your connection string, such as appdb
Username The user your application connects as, such as appuser
Password Leave it blank and a strong password is generated for you. If you type your own, use at least 12 characters
Charset How text is stored. Leave it on Default unless your application needs another
Collation How text is compared and sorted. Leave it on Default unless your application needs another
Timezone The default time zone for date and time functions. UTC is recommended

The database name and username must follow the engine's rules:

Rule MySQL PostgreSQL
Allowed characters Letters, digits and underscores, starting with a letter The same, after lower-casing
Case Kept as you typed it Folded to lower case, so MyApp becomes myapp
Database name length Up to 64 characters Up to 63 bytes
Username length Up to 32 characters Up to 63 bytes
Reserved database names mysql, information_schema, performance_schema, sys postgres, template0, template1
Reserved username starts mc_ mc_ and pg_

When the name you typed is not exactly what will be created, a notice appears under the fields before you continue:

Your database will be created as myapp / user appuser (identifiers are lower-cased and limited to 63 bytes).

Use the names in that notice in your connection strings.

The charsets and collations offered are:

Engine Charsets Collations Default
MySQL utf8mb4, latin1 utf8mb4_0900_ai_ci, utf8mb4_unicode_ci, utf8mb4_bin, latin1_swedish_ci utf8mb4 with utf8mb4_0900_ai_ci
PostgreSQL UTF8, LATIN1 en_US.UTF-8, C UTF8 with en_US.UTF-8

Charset and collation are fixed once the database exists.

Step 3: Topology & Failover

Choose Standalone or Master-Read Replica, and a Failover Policy. Section 4 explains them.

Step 4: Backups

Field Choices
Automated backups On by default. Keep it on unless you back up another way
Interval Every 1h, 2h, 4h, 6h, 12h or 24h. The interval does not change the price
Retain 3, 7, 14 or 30 backups. When a new scheduled backup is taken, the oldest is removed

Backup storage beyond the free allowance is charged per GB-month, and the step shows the rate. Section 10 covers backups in full.

Step 5: Access

Field What it does
Allowed Networks The public IP addresses or ranges that may connect. Type one and select Add. A single address is saved as /32 for IPv4 or /128 for IPv6, which means just that machine
Your API deployments on this platform may connect On by default. Lets in any API deployment you link to this database, without listing its addresses (Section 7)

An empty list blocks every connection from outside the platform. Add your servers' addresses now, or the database will be healthy and refuse every connection. Section 5 explains the list.

Step 6: Cache Add-on

Turn on Redis cache add-on to add a Redis cache beside your database, then pick a Cache Plan and optionally a Cache Password (optional). You can also add it later. Section 11 covers the cache.

Step 7: Webhook

Turn on Webhook and enter an https:// URL to receive signed notices when your database changes state, such as when a failover starts. You can also set this up later. See Section 12.

Step 8: Review

Check the summary and the Estimated monthly cost, which is the database plan plus the cache add-on if you chose one. Select Create database.

The database is ready when it reaches Running. Provisioning places both copies on different machines, starts the engines, creates your user and brings the second copy up to date, which takes a few minutes.