Database Plans
Zenifra database plans vary in capacity and resources, but some product rules remain the same across plans.
What changes between plans
Plans mainly affect:
- compute capacity
- available storage
- observability features
- contract flexibility
Plans and prices
Values from the public catalog (GET /v1/project/database/plans), in Brazilian reais (BRL) and per instance. Persistent storage is billed separately, per GB on each instance, except on db-free. The console shows the total before you confirm.
| Plan | vCPU | RAM | Hourly | Monthly | Yearly | Engines |
|---|---|---|---|---|---|---|
db-free | 0.1 | 128 MB | Free | Free | Free | PostgreSQL or Valkey Key‑Value |
db-starter | 0.3 | 256 MB | R$ 0.018 | R$ 11.90 | R$ 130.90 | PostgreSQL, MariaDB, or Valkey |
db-basic | 1 | 1 GB | R$ 0.076 | R$ 49.90 | R$ 548.90 | PostgreSQL, MariaDB, or Valkey |
db-premium | 2 | 2 GB | R$ 0.18 | R$ 129.90 | R$ 1,428.90 | PostgreSQL, MariaDB, or Valkey |
db-enterprise | 8 | 8 GB | R$ 0.75 | R$ 489.00 | R$ 5,388.90 | PostgreSQL, MariaDB, or Valkey |
db-freeincludes a fixed 1 GB of persistent storage and 1 instance. Each organization can have up to 2 activedb-freeprojects, counting PostgreSQL and Valkey Key‑Value together.- MariaDB is not available on
db-freeand always uses 3 instances, so the plan price is multiplied by 3. - Available versions: PostgreSQL 15, 16, 17, and 18 (default 18); MariaDB 10 and 11 (default 11).
Metrics
PostgreSQL and MariaDB metrics are available on the db-premium and db-enterprise plans. They include resources (CPU, memory, and storage), connections, activity, read cache, locks, latency, health, and replication, per instance, as a snapshot refreshed every 60 seconds without history.
Instances and topology
PostgreSQL
- can operate from 1 to 3 total instances (
db-free: always 1) - in hourly billing, instance count can change later
- in monthly and yearly billing, instance count is fixed in the contract
MariaDB
- always runs with 3 fixed instances
- does not allow increasing or decreasing the instance count
Storage
- storage can increase
- storage can never shrink
- changes are only available in hourly billing; on monthly and yearly contracts, capacity is fixed for the contract term
- on
db-free, storage is fixed at 1 GB - increasing storage may cause temporary downtime
For ClickHouse, plans, topology, and storage allowances belong in the separate Analytics plans section, not the PostgreSQL or MariaDB plans.
Contracts
For monthly and yearly databases:
- stopping the database makes it inaccessible
- this does not change the final contract charge during the contracted period
- disabling automatic renewal lets the contract end without renewal
FAQ
Can I upgrade the plan?
Yes, in hourly billing. On monthly and yearly contracts, the plan cannot be changed during the contract. db-free cannot be switched to another plan, and no plan can be switched to db-free. The change may cause temporary downtime.
Can I shrink storage later?
No. Storage can increase, but it can never shrink.
Can I change the number of replicas in MariaDB?
No. MariaDB uses 3 fixed instances.
Can I change the number of instances in PostgreSQL?
Yes, in hourly billing, between 1 and 3 instances. In monthly and yearly billing, the configuration is fixed in the contract. On db-free, the database always uses 1 instance.
Do I have root access to the database?
No. The user does not have root or superuser access, but does have enough elevated access to operate the database normally.
Do plans include automatic backups?
No. Zenifra does not currently provide automatic backups or console restore for PostgreSQL and MariaDB. Keep your own exports with pg_dump or mariadb-dump/mysqldump.
Last updated on