Data on Zenifra

    Databases for your applications

    Explore PostgreSQL, MariaDB, ClickHouse and Valkey on Zenifra. Compare use cases, check plans and configure your application data through the Console.

    PostgreSQL and MariaDB

    For applications that use relational databases and SQL queries. Choose the database your application supports and check capacity, storage and plan conditions before creating it.

    ClickHouse Analytics

    For event data, reporting and OLAP workloads. Analytics plans include persistent storage, and the Production and Enterprise plans have 3 replicas with high availability. Configure the connection through the Console.

    Valkey Key-value

    For applications that access data by key using Redis-compatible clients. Check the persistence and capacity characteristics of your chosen plan.

    Cache

    For reducing repeated queries and speeding up access to data your application can retrieve again. Choose the Cache profile and check its plan limits.

    Queue

    For applications that organize tasks and messages with Valkey. Your application defines how messages are produced and consumed; consult the documentation before integrating.

    Automatic backups

    PostgreSQL, MariaDB, ClickHouse Analytics, Key-value and Queue include automatic backups in the plan at no extra cost, kept for 3 to 30 days depending on the plan. Restores are handled by support. Cache has no backups because its data lives only in memory.

    Watch a database being configuredConsole walkthrough: a PostgreSQL database on the DB-Free plan, from choosing the type to the cost summary.

    Before choosing a plan

    1. Confirm the database or profile your application expects.
    2. Compare capacity, included storage and prices in the current catalog.
    3. Read the documentation to configure your application connection.

    New · Private connections

    Apps, databases and cache on the same private network, nothing exposed to the internet

    Connect your applications and Jobs to the database and cache without exposing them to the internet. Link resources in the same organization over a private network: the source calls the target through an internal address, even when the target has no public URL.

    Internal address

    An A → B link lets A call B at <project>.<organization-id>.zenifra.local, even when B is private. Targets: applications, PostgreSQL, MariaDB, ClickHouse, and Valkey.

    Only in the direction you create

    Without a link, nothing changes. Sources are applications and scheduled Jobs; databases and cache only receive. Other organizations cannot reach the address.

    Control right away

    Turning a link off blocks new connections immediately. Turning it on or off may restart the source application; Jobs use the new address on their next runs.

    Map in the Console

    Drag the application cards, create the links, and save the layout.

    Application connections in the consoleRecorded in the real console: application map, linking a source to a target, and the internal address.
    How private connections work

    We respect your privacy

    We use essential cookies to run this site. Measurement and marketing cookies, such as Google Ads, are only enabled when you accept all cookies. Read our cookie policy.