Database

Zenifra offers managed databases with PostgreSQL and MariaDB for teams that want to operate applications without manually managing database infrastructure.

Supported databases

What the platform provides

• failover support
• replication according to each engine's supported topology
• connection credentials and full URI in the console
• persistent storage

Connection details

In the console, you can see:

• host
• port
• username app
• password
• database name app
• a ready-to-copy full URI

When replicas exist, the console can also show master and replica connection details plus a ready URI for each one.

How to connect your application

Zenifra does not automatically inject DATABASE_URL into your HTTP project.

The correct flow is:

1. copy the URI or connection details from the console
2. manually configure DATABASE_URL in the HTTP project

PostgreSQL

• can operate from 1 to 3 total instances
• with 1 instance, only the master exists
• with multiple instances, the master handles writes and reads
• extra instances act as read replicas
• in hourly billing, replica count can be increased or decreased later
• in monthly and yearly billing, replica count is fixed in the contract

MariaDB

• always runs with 3 instances
• does not allow increasing or decreasing the instance count

Database version

At creation time, the user can select any version available in the console.

During edit:

• only forward upgrades are supported
• downgrades are not supported

Warning: version upgrades can cause a few minutes of downtime.

Storage

Every database on Zenifra uses persistent storage.

Storage rules

• storage can increase
• storage can never shrink
• on monthly and yearly contracts, storage changes should only happen after the contract ends
• increasing storage may cause temporary downtime

Failover and replication

PostgreSQL and MariaDB support automatic failover.

Data replication can happen across up to 3 instances for both engines, according to the supported topology of each one.

User access

The user does not have root or superuser access, but does have enough elevated access for normal database usage.

Metrics

The confirmed database metrics today are:

• CPU usage
• RAM usage
• storage usage

These metrics are available on Premium+ plans and can appear both per database project and per instance/replica.

Next steps

1. Database Configuration
2. Database Plans
3. Create an HTTP project and configure ENVs manually