Required permissions

Use the database project ID as project-id and grant only the scope for the requested action:

An owner has full access in a user session. assistant, member, and organization API Keys need the specific grant. The linked-applications lookup currently uses database.password.rotate in the API contract.

Accessing the Settings

1. In the sidebar menu, click Projects
2. Find and click the desired database project name
3. On the project page, click the "Edit" button in the top-right corner

Available Settings

Project Name

The project name can be changed at any time.

Rules:

• Minimum: 6 characters
• Maximum: 32 characters
• Only lowercase letters, numbers, and hyphens

Note: Changing the name does not affect the connection address, which uses the project ID.

Project Description

The project description can be changed at any time.

Characteristics:

• Optional field to describe the project purpose
• Helps identify and organize your projects
• Can include information such as environment, customer, or purpose

Database Password

You can renew the password of the PostgreSQL app user at any time. You do not choose the new password: Zenifra generates a random one.

How to change it:

1. In the password section, request a new password
2. Confirm the action
3. Copy the new password shown and store it safely; it is shown only once

Warning: The database may be unavailable during the process.

Important: Linked applications are not updated automatically. The console lists those applications; manually update the connection variable (for example, DATABASE_URL) in each one.

PostgreSQL Version

The PostgreSQL version can be updated.

Available versions:

• PostgreSQL 15
• PostgreSQL 16
• PostgreSQL 17
• PostgreSQL 18

The console only offers versions newer than the current one.

How to update:

1. Select the desired new version
2. Click Save

Warning: Version upgrades can cause brief periods of downtime. We recommend making the change during low-traffic hours.

Important: PostgreSQL version downgrade is not supported. Export your data with pg_dump before upgrading and test the application with the new version.

Connection String

The connection string is generated automatically and can be viewed at any time, with the password masked.

Format:

postgres://app:<password>@postgresql-<project-id>.managed.zenifra.com:<port>/app?sslmode=verify-full&sslrootcert=system

With 2 or 3 instances, the console also shows a read-only string that routes queries to the replicas.

To copy: Click the copy button next to the connection string.

Tip: Use this string in your application's DATABASE_URL environment variable to connect to the database.

Scalability (Instances)

In hourly billing, you can increase or decrease the total number of database instances while the database is running. On monthly or yearly contracts and on the db-free plan, the count cannot be changed.

Limits:

• Minimum: 1 instance
• Maximum: 3 instances

Impact:

• More instances = higher availability
• More instances = higher cost
• Additional instances offer automatic failover
• Secondary instances can be used through the read-only string, reducing load on the primary instance

Note: For projects with more than 1 instance, automatic failover is enabled. If the primary instance fails, a secondary instance takes over automatically.

Storage

Database storage can be adjusted.

Limits:

• Minimum: 1 GB
• Maximum: 250 GB

Impact:

• For hourly projects: storage can be increased
• For monthly/yearly contracts: storage is set at purchase and cannot be changed during the contract
• On the db-free plan: fixed at 1 GB

Warning: Storage reduction is not supported, and increases may cause temporary downtime. Make sure to allocate enough space for your data.

Plan

In hourly billing, you can change the database plan in the project edit page. On monthly or yearly contracts, the plan cannot be changed during the contract, and db-free cannot be switched to another plan. The change may cause temporary downtime.

Automatic renewal

On monthly and yearly contracts, the project edit page lets you enable or disable automatic contract renewal.

Project Actions

Stop the Project

When you stop the project:

• The database is stopped
• Database instances are shut down
• The project becomes inaccessible
• For hourly projects, plan billing stops, but storage costs continue

When to use it:

• When you do not need the database temporarily
• To save costs on hourly projects

Start the Project

To start a stopped project:

• The database starts again
• Database instances are initialized
• The project becomes accessible again
• For hourly projects, billing resumes

Delete the Project

Deletion is permanent and irreversible.

What happens:

• All database instances are removed
• All data is deleted

Warning: Zenifra does not keep database backups. Export your data with pg_dump before deleting. This action cannot be undone.

Next Steps

• Create a PostgreSQL Database
• Project Metrics and Insights
• Payment Settings

FAQ

Can I change the database password?

Yes. At any time through the project settings; Zenifra generates the new password and shows it only once. Remember to update the connection variable in the applications that use the database.

Does changing settings cause downtime?

It depends on the change:

• Password: May cause downtime during the process
• PostgreSQL version: May cause brief downtime
• Instances: May cause temporary downtime
• Storage: May cause temporary downtime
• Plan: May cause temporary downtime

Can I restore a deleted database?

No. Deletion is permanent and there is no platform backup. Data cannot be recovered. Export your data before deleting.

What happens if the primary instance fails?

For projects with more than 1 instance, automatic failover occurs:

• A replica is promoted to primary
• The connection keeps the same host and port
• Open connections can be closed during the switch; configure your application to reconnect automatically

How do I back up my database?

Zenifra does not currently provide automatic backups or console restore. Export your data periodically with pg_dump, store the copies outside the project, and test restores.

Can I connect external applications to the database?

Yes. Use the connection string provided in the settings; the connection requires TLS. Database projects do not provide whitelist or blacklist controls, so restrict access at the application, client network, or credential-management layer when needed.