Analytics
Analytics is Zenifra's category for projects that store and query analytical data. Its first product is managed ClickHouse. Use it for events, time-series data, dashboards, and aggregation across many records. For an application's transactional database, start with PostgreSQL or MariaDB; for sessions and shared state, see Key-Value.
Choose your path
- ClickHouse: from project to first query — create a project, save its credentials, and run a complete SQL example.
- Analytics plans — compare per-instance capacity, instance count, included storage, and billing.
- Connections and clients — configure DBeaver over HTTPS/JDBC or
clickhouse-clientover Native TLS. - Operations and troubleshooting — check status, handle password changes, and diagnose connection errors.
If your project already exists and you only need to connect, go directly to Connections and clients. The ports and password in the examples must come from your own project.
What Zenifra manages
The platform provisions the project, persistent capacity, public endpoints for both client protocols, and credentials. Topology varies by plan: some plans have one instance, while others have three replicas. In the app database, DDL is replicated and the default table engine is ReplicatedMergeTree; a table explicitly created with a non-replicated engine does not inherit the data availability guarantee of a multi-replica plan. See Analytics plans before choosing a topology.
You remain responsible for schema, ingested data, queries, access to credentials, and testing your application after changes. In particular, endpoint availability is not an authenticated query: run SELECT 1 using your credentials to check the connection.
ClickHouse is separate from Database plans
This product's SKUs use the analytics-* prefix, not db-*. The price shown in the Console is the total cluster price, including three-replica plans. Included persistent storage depends on the SKU; logical capacity above the allowance is billed separately. Check the Console catalog for current monetary prices and the capacity explanation for how the allowance works. Do not assume PostgreSQL or MariaDB rules apply unchanged to this product.