PostgreSQL, MariaDB, and Key-Value Databases on Zenifra

Zenifra provides managed PostgreSQL, MariaDB, and Valkey Key-Value for teams that want to run applications without manually administering database infrastructure. For event analytics and aggregated queries with ClickHouse, start at the Analytics section.

Required permissions

An owner has full access in a user session. assistant, member, and organization API Keys need the specific grants. Creation requires the organization scope; later operations use the database project ID.

Available Databases

PostgreSQL

• available versions: 15, 16, 17, and 18
• topology from 1 to 3 total instances (db-free: 1 instance)
• the primary instance handles writes and reads
• extra replicas handle reads
• automatic failover with 2 or 3 instances

MariaDB

• available versions: 10 and 11
• fixed 3-instance topology (one primary and two replicas), starting at the db-starter plan
• automatic failover
• InnoDB engine by default

Valkey Key‑Value

This option is intended for sessions, shared state, counters, locks, and atomic operations. It uses db-* plans, keeps persistent storage, and connects through VALKEY_URL with TLS and the default user. See the Key‑Value guide for examples and product limits.

What the platform manages

• automatic failover when replicas exist
• replication according to the engine
• credentials and connection URI in the console
• mandatory TLS for connections
• persistent storage

The platform does not currently provide automatic backups or console restore. Keep your own exports with pg_dump or mariadb-dump/mysqldump.

Connection Data

After creation, the Console shows the host, port, username, database, and connection URI. A usable password is shown only at creation or rotation; the URI shown afterward has a masked password. ClickHouse has two ports per project, documented in the Analytics connections guide.

For PostgreSQL with 2 or 3 instances, the console also shows a read-only URI that routes queries to the replicas. For MariaDB, the provided connection points to the primary instance.

Application Integration

Zenifra does not automatically inject DATABASE_URL into the HTTP project. The correct flow is to copy the URI in the console and manually configure the application's ENV.

Later Changes

• it is possible to upgrade the version forward
• downgrade is not supported
• the password can be changed, and the platform generates a new password; linked applications are not updated automatically
• instances (PostgreSQL), storage, and plan can only be changed in hourly billing and outside the db-free plan
• increasing storage can cause temporary downtime

Next Steps

• Database Plans
• Database Configuration
• Key‑Value Database with Valkey
• Analytics and ClickHouse
• Create an HTTP project