Skip to content

Analytics: the intermediate pieces
you no longer build

Managed analytics services from data centres in Germany: Five services create a pipeline from the event to the dashboard panel, individually from €61.00$70.76 net per month. Billed per class and month; what would otherwise need to be built and operated between the services is part of the service.

Amounts net, without term discount and without region factor. Locations: 3.

Services
5
can be ordered individually, together a pipeline
Entry
€61.00$70.76
per month, net · Dashboards Team
Storage per GB
€0.0070$0.0081
Object Storage, per month
ClickHouse ingestion rate
10:1
Compression for the costs per terabyte of raw data

Daily volume, data type and retention determine the class and amount for each stage — calculated using the same catalogue values as the tables below. Each calculation is shown openly alongside.

stage by stage

Bar: utilisation of the selected class

  1. Ingestion

    Kafka Stream S

    €353.03$409.51

    0.24 of 18 MB/s · keeps 24 days powered

  2. Raw zone

    Object Storage 1.8 TB

    €12.60$14.62

    is 90 days

  3. Processing

    Data Platform Platform S

    €229.70$266.45

    control plane + 2 nodes

  4. Analysis

    ClickHouse Analytics M

    €189.00$219.24

    1.8 of 3.9 TB Raw data

  5. Search

    OpenSearch Search M

    €409.00$474.44

    336 of 900 GB Index

  6. Dashboards

    Dashboards Dashboards Team

    €61.00$70.76

    1 nodes + data endpoint

Daily data volume

1 GB a day5,000 GB a day

= 0.24 MB/s continuous load, averaged over the day. This means everything your sources generate on a normal day — events, logs, change data.

Data type

How densely ClickHouse packs your data. The calculation uses the lower value of the observed range — the pipeline is sized generously rather than tightly.

Retention in ClickHouse

This is how long the data remains queryable. The raw zone keeps the same period — at your volume, there will be 1.8 TB of raw data in Object Storage.

Ingestion

Only the Kafka stream brings its own Kafka cluster into the pipeline. Object Storage, change data and the HTTP endpoint are read by the Data Platform itself.

Processing frequency

The Data Platform checks, shapes and loads the raw data. Your amount is the control plane plus the processing nodes — the frequency determines how many run concurrently.

Full-text search

How far back the search over the raw logs reaches. It is worthwhile where the answer is in the text: error messages, logs, documents.

Dashboards

Grafana-based dashboards that read from ClickHouse, OpenSearch and the metrics of the same environment.

Net monthly · 5 services€1,254.33$1,455.02Go to result

Your pipeline

5 services and the raw zone · 1.8 TB raw data

Kafka Stream S
€353.03$409.51
Raw zone in Object Storage, 1.8 TB
€12.60$14.62
Platform S
€229.70$266.45
ClickHouse Analytics M
€189.00$219.24
OpenSearch Search M
€409.00$474.44
Dashboards Team
€61.00$70.76
Net monthly
€1,254.33$1,455.02
per terabyte of raw data in ClickHouse, at full class
€48.38$56.12

All amounts net, plus 19 % VAT. Without term discount and without region factor.

Calculation basis

  1. Continuous load = daily volume × 1,024 MB ÷ 86,400 s — 84.4 GB a day is 1 MB/s.
  2. The raw zone remains as long as the analysis; it does not end by itself.
  3. ClickHouse holds storage per node × compression rate of the data type (lower value of the observed range); replicas each hold a full copy.
  4. The index occupies 1.2 times the raw logs, each document is stored two times.
  5. Amounts net, without term discount and without region factor; Data Platform, OpenSearch and dashboards are calculated from catalogue values.

A pipeline from source to query

Ingestion, validation, transformation and storage run as a managed pipeline. The raw data remains unchanged in Object Storage, which is billed by occupied space — any subsequent error can be re-rolled from there.

Pipeline flow

  1. 01IngestionThe raw data lands unchanged in a landing zone in Object Storage. This zone is never overwritten; any subsequent error can be rolled back and reprocessed from here.
  2. 02ValidationEvery record is validated against the stored schema. Anything that does not fit goes into a separate storage with the error reason, instead of aborting the run.
  3. 03TransformationTransformations are described in SQL or stored as a Python task. Both run on the same processing nodes and write to the same target zone.
  4. 04StorageThe result is written column-wise as Parquet and versioned via a table format. Older states remain queryable until the cleanup rule applies.
  5. 05DeliveryClickHouse and OpenSearch read from the target zone. The processing pipeline knows both as targets and reports the loading progress back to the orchestrator.

What the amount includes

Control plane per environment
€65.70$76.21 / month
Scheduler, workflow control and data catalogue, distributed across three fire zones. The same amount as a highly available Kubernetes control plane, because the same foundation runs underneath.
Processing nodes
€82.00$95.12 / month
8 vCPU and 16 GB memory per node. Nodes can be added and removed individually.
Storage in Object Storage
€0.0070$0.0081 / GB
Billed by occupied space. Within the ENTRONYX network, there is no charge for retrieval.
A pulled-out drive drawer from above: row upon row of hard drive carriers are plugged into their slots, no slot is empty.
One terabyte of raw zone costs €7.17$8.32 per month at ENTRONYX CLOUD, on NVMe block storage 12 times as much. That is why it is located in Object Storage and not next to the database — and stays there until a cleanup rule applies.

Ingestion

Kafka topics

The pipeline reads directly from a managed Kafka cluster and remembers the offset per task — the reading position in the stream. Upon restart, reading continues from the last confirmed offset, not from the beginning.

Kafka protocol, SASL/SCRAM

Object Storage

New objects in a bucket — an Object Storage container — trigger a run. The trigger comes from the storage notification, not from a polling interval; this prevents empty runs.

S3 API, event notification

Change data

Changes are captured from managed PostgreSQL and MySQL via the transaction log. The source database receives a read connection for this, not additional query load.

logical replication, binlog

HTTP endpoint

For events from applications that neither speak Kafka nor write to a database. The endpoint accepts JSON lines and stores them in a buffer.

HTTPS, token per pipeline

Formats

What arrives is read. Writing is done column by column — anything else makes the subsequent query more expensive than the one-time transformation costs.

  • Parquet Standard format of the target zone, column-wise, compressed with ZSTD
  • ORC read and written, for datasets from Hadoop environments
  • Avro read and written, with schema from the registry
  • JSON Lines read, typical for application events via HTTP
  • CSV read, with specified delimiter and character set
  • Iceberg Table format over Parquet: schema evolution, time travel
  • Delta Lake Table format over Parquet, for existing Delta datasets

Size classes

The class only determines the number of processing nodes. Control plane and storage are the same in every class; a change alters neither pipelines nor data.

Data Platform size classes with node count and monthly price
ClassNodestotal vCPUPrice / month
Platform S216€229.70$266.45
Platform M648€557.70$646.93
Platform L16128€1,377.70$1,598.13

Net amounts plus 19% VAT. Each row is the sum of control plane and node count: €65.70$76.21 plus nodes times €82.00$95.12. Storage is billed by consumption and is not included.

Request Data Platform

Opens the request, pre-filled with Platform S. The Data Platform does not yet have its own catalogue plan — its amount is calculated from catalogue values.

Events that nobody misses

Three brokers, the machines of the cluster, hold the message stream and manage themselves in KRaft mode — without the previously required additional service ZooKeeper. Schema Registry, the repository for message formats, and Connect, the connection to sources and destinations, run in the same cluster. Consumers read at their own pace; a slow one slows down neither the producer nor the others.

Broker classes and throughput

Kafka broker classes with specifications, throughput and monthly price
ClassBrokervCPU / RAM per brokerStorage per brokerContinuous loadMB/sPeakMB/sPrice / month
Stream S32 / 4 GB480 GB1845€353.03$409.51
Stream M34 / 15 GB1.9 TB74160€1,329.99$1,542.79

Measurement condition: kafka-producer-perf-test, 1 KB per message, acks=all, replication factor 3, compression lz4, one topic with 24 partitions. net amounts plus 19% VAT.

Retention is a calculation, not a setting

  • Stream S480 GB usable

    5.7 days at 1 MB/s
    13.7 hours at 10 MB/s
  • Stream M1.9 TB usable

    22.8 days at 1 MB/s
    2.3 days at 10 MB/s

The storage of a single broker is usable because each message is stored in 3 copies — one on each broker. A stream of 1 MB/s writes 84.4 GB per day; the retention is the usable storage divided by this amount.

Without offloading. If you want to retain data longer, attach Block Storage NVMe (€0.0860$0.0998 per GB per month) or offload to Object Storage (€0.0070$0.0081 per GB per month). The gap between both rates is the reason why long-term retention ends up in object storage.

A switch in a light-coloured rack: two rows of fibre optic ports with orange cables running bundled to the right side; green lights are illuminated next to the ports.
Stream S assumes a continuous load of 18 MB/s.At 1 MB/s, Stream S keeps every event retrievable for 5.7 days — if you need it longer, read it from the raw zone, not from the stream.

Schema Registry

Avro, Protobuf and JSON Schema are versioned per topic. The registry rejects a new version if it violates the configured compatibility rule — backward compatibility is the default.

The registry runs on the same nodes as the brokers and is accessible via the same private address. A separate external endpoint is not opened.

standard registry interface, included in the price

Retention and offloading

Older segments move to Object Storage and remain queryable there. The broker only keeps the hot part on NVMe; retention is therefore no longer tied to disk size.

The object storage price applies to the offloaded segments, not the block storage price. This difference is the reason why long-term retention remains affordable at all.

older segments in Object Storage

Connect runtime

Source and target connectors run as separate tasks. If one fails, it is restarted on another node without stopping the others.

Connectors for Object Storage, PostgreSQL, MySQL, ClickHouse and OpenSearch are included. Custom connectors can be uploaded as a JAR file (Java package).

distributed, with restart per task

Configure Kafka

Opens the database configurator with Stream S in the size tier — three brokers as in the table above, the same catalogue rate. You select backup and network there; whatever you add will be added to the amount.

Columns instead of rows

A sum over a column reads exactly that column. A row-oriented database reads every row completely and discards the superfluous part. With forty columns, this is not fine-tuning, but an order of magnitude.

What a sum over a column reads

Read row by row

48 cells read — the database reads each row completely and discards the rest.

Read column by column

6 cells read — only the one column that the sum needs.

Both grids answer the same question. The gap grows with every column that the query does not need.

Aggregation across many rows, few columns

If you calculate a few metrics across many operations, you only read the columns specified in the query. The wider the table, the larger the part that the columnar storage doesn't even touch.

Time windows across billions of rows

The data is stored in blocks sorted by time. A one-hour window touches the blocks of that hour; the rest of the table is not touched.

Distributions and quantiles

Approximation methods for quantiles — the threshold below which a certain proportion of all values lies — and for unique values are built in and run across the column blocks. An exact count over a billion rows takes factors longer than the approximation.

What ClickHouse is not meant for

Modifying individual rows, checking foreign keys, many short writes per second. PostgreSQL remains the right choice for this — the section on differentiation explains this.

Compression by data type

  • Time series with key metrics

    Delta + ZSTD · timestamps and counters at regular intervals

    12:1 to 24:1

  • Application events

    ZSTD · recurring field names and identifiers

    8:1 to 14:1

  • Log texts

    ZSTD · free text with low repetition

    4:1 to 6:1

  • Identifiers with few values

    LowCardinality + LZ4 · status values, country codes, device types

    20:1 to 60:1

The rate depends on the data, not the service. The route calculator uses the lower value of the range; the costs per terabyte in the table below use the reference rate 10:1 — the vertical line. The decisive factor is the cardinality of a column, i.e. the number of its distinct values: the fewer there are, the more it can be compressed.

Measured as the ratio of uncompressed to compressed size on disk, across tables from one billion rows.

Size classes and costs per terabyte

ClickHouse classes with storage, price and derived costs per terabyte
ClassNodesvCPU / RAMStorageRaw dataat 10:1per TB of raw dataPrice / month
Analytics M18 / 32 GB500 GB4.9 TB€38.71$44.90€189.00$219.24
Analytics L316 / 64 GB2.0 TB19.5 TB€28.11$32.61€549.00$636.84

Net amounts plus 19% VAT. “per TB raw data” is the monthly price divided by the amount of raw data that fits into storage at 10:1; replicas each hold a full copy. The classes are taken unchanged from the product catalogue and appear with the same amount under Databases.

A screen on a light-coloured table shows a table with eight columns, of which only the “Amount” column is highlighted in purple. Next to it: “1 of 8” columns read and bars for compression per column.
Analytics M holds around 4.9 TB of raw data at 10:1 — for €38.71$44.90 per terabyte and month. It is not the disk size that determines the price, but the compression.
Configure ClickHouse

Opens the database configurator with Analytics M in the size step — the same catalogue plan as in the table above. You select deployment, backup and network there.

Three screens side by side on a light-coloured wall above a table: on the left a dashboard with a curve and bars for the data stream, in the middle an overview with a curve and bars, on the right a list of log lines.

The dashboards read from ClickHouse, OpenSearch and the metrics of the same environment — at ENTRONYX CLOUD as a managed service from €61.00 net per month.

Dashboards Team · up to 25 registered people

Search where the answer is in the text

Logs, documents and events are parsed and indexed as they are written. A search across a hundred million lines therefore answers in milliseconds the same question that a scan through files takes minutes to answer.

Size classes

OpenSearch classes with nodes, index storage, retention and monthly price
ClassNodesvCPU / RAM per nodeIndex per nodeUsable2 copiesRetentionat 20 GB/dayPrice / month
Search S32 / 8 GB200 GB300 GB12.5 days€169.00$196.04
Search M34 / 16 GB600 GB900 GB37.5 days€409.00$474.44
Search L38 / 32 GB2.0 TB2.9 TB125 days€1,019.00$1,182.04

Net amounts plus 19% VAT. Each class runs with 3 nodes because the cluster management needs an odd number for its quorum. Half the gross storage is usable because each document has a replica. The index overhead of 1.2 compared to the raw data is already included in the “Retention” column.

Where the price comes from

OpenSearch is not yet maintained as a separate plan in the product catalogue. The amounts above are therefore calculated, not set: instance price plus block storage for the index, times management markup, times number of nodes. The markup of 1.17 is not a free value itself, but calculated back from the maintained ClickHouse plan: the same raw configuration there, against the price maintained there.

A flat server in a light-coloured rack with eight drive carriers in two rows; the black lever is open on three carriers, a green light is illuminated on each.
Search S goes back 12.5 days at 20 GB of raw logs per day: each day takes up 24 GB of index, and each document is stored in 2 copies on NVMe.

Index lifecycle

Indices are rolled daily: a new index starts for each day. After the set period, they move to slower nodes, then to Object Storage, and finally they are deleted. Each step is stored as a rule, not as a task in the calendar.

The retention period applies per index pattern. Access logs with 14 days and audit logs with 400 days are therefore in the same cluster.

hot, warm, cold, deleted

Full text and structured fields

Analysed text fields and exact keyword fields lie next to each other. A search for an error message can thus be restricted to a tenant and a time window in the same expression.

German stemming and compound decomposition are preconfigured. Custom dictionaries and synonym lists can be uploaded.

one query across both

Custom dashboards

The cluster comes with its own interface for search and log analysis — discover, saved queries, visualisations across index patterns.

The service in the next section is intended for metrics from multiple sources. OpenSearch Dashboards only sees its own indices.

OpenSearch Dashboards, included in the price

Request OpenSearch

Opens the request, pre-filled with Search S. OpenSearch does not yet have its own catalogue plan — the amount is calculated from catalogue values.

One interface across all sources

Grafana, the popular open interface for metrics dashboards, runs as a managed service — with the platform's data sources already configured. We handle updates, backup of the dashboards and recovery. The dashboards themselves remain exportable as JSON, an open text format, and can therefore be versioned.

Data sources

Configured and provided with access credentials as soon as the respective service runs in the same account. A view may show panels from multiple sources.

  • Prometheus endpoint metrics from monitoring, query language PromQL
  • Loki logs from monitoring, query language LogQL
  • ClickHouse analyses via the columnar database, in SQL
  • OpenSearch search and logs via index patterns
  • PostgreSQL and MySQL business data from managed databases, in SQL
  • Tempo distributed tracing, only in the upper tier

Alarms

Rule
Query, threshold and hold time — the state is only considered reached after the hold time has elapsed
States
normal, pending, triggered, no data — every transition is logged
Contact points
E-mail, webhook and Matrix; on-call and chat services via their webhook
On-call
Schedules per team, escalation to the next level after a deadline
Muting
planned maintenance windows suppress notifications without disabling the rule
Evidence
History per rule over 90 days, with trigger time and acknowledgement

Sharing

Four ways to share a dashboard. Each has a different limit — the limit is stated, not just the method.

Within the organisation

Folders carry the permissions, not the individual view. Anyone with folder permissions sees all views within it — this keeps permission management manageable even with three-digit view numbers.

Public link with expiry

A view can be shared without logging in. The link carries an expiry date and a random component, and the underlying data source remains hidden. Shared views are listed in a separate overview.

Embedding

Individual panels can be embedded into your own application. Sharing is restricted to specified origins; without an entry in this list, the panel will not load.

Report as file

Views can be generated as PDFs on a schedule and sent via email. For reports to parties that do not have access to the service.

Size classes

Dashboard tiers with node, data endpoint and monthly price
TierNodesvCPU / RAM per nodeScopePrice / month
Dashboards Team14 / 8 GBOne node, up to 25 registered users, alerts via email.€61.00$70.76
Dashboards Operations28 / 16 GBTwo nodes behind a Load Balancer, on-call schedules.€183.00$212.28
Dashboards Enterprise34 / 16 GBThree nodes, tenant separation, tracing data source.€332.00$385.12

Net amounts plus 19% VAT. Each tier is the sum of the nodes and the data endpoint it reads: €19.00$22.04 for metrics and logs, €59.00$68.44 for the tier with tracing. Both amounts come unchanged from the monitoring options of the product catalogue — the dashboard service reads from the same endpoint and does not bill it a second time.

Request dashboards

Opens the request, pre-filled with Dashboards Team. The tiers are calculated from catalogue values — node and data endpoint, as in the footnote above.

All classes side by side

13 classes across 5 services. The last column indicates for each row where the amount comes from — from the maintained product catalogue or from a disclosed calculation based on catalogue values.

  • from the product catalogue
  • calculated from catalogue values
Size classes of all analytics services with configuration, monthly price and origin of the amount
Service and classNodesvCPU / RAM per nodeStorage per nodePrice / monthOrigin of the amount
Data Platform · Platform S28 / 16 GBzustandslos€229.70$266.45Control plane €65.70$76.21 + 2 × €82$95.12 per node
Data Platform · Platform M68 / 16 GBzustandslos€557.70$646.93Control plane €65.70$76.21 + 6 × €82$95.12 per node
Data Platform · Platform L168 / 16 GBzustandslos€1,377.70$1,598.13Control plane €65.70$76.21 + 16 × €82$95.12 per node
Kafka · Stream S32 / 4 GB480 GB€353.03$409.51unchanged from the product catalogue
Kafka · Stream M34 / 15 GB1.9 TB€1,329.99$1,542.79unchanged from the product catalogue
ClickHouse · Analytics M18 / 32 GB500 GB€189.00$219.24unchanged from the product catalogue
ClickHouse · Analytics L316 / 64 GB2.0 TB€549.00$636.84unchanged from the product catalogue
OpenSearch · Search S32 / 8 GB200 GB€169.00$196.04ND2 + 120 GB Block NVMe, × 3 nodes, × management surcharge
OpenSearch · Search M34 / 16 GB600 GB€409.00$474.44ND3 + 440 GB Block NVMe, × 3 nodes, × management surcharge
OpenSearch · Search L38 / 32 GB2.0 TB€1,019.00$1,182.04ND4 + 1760 GB Block NVMe, × 3 nodes, × management surcharge
Dashboards · Dashboards Team14 / 8 GBzustandslos€61.00$70.761 × €42$48.72 per node + €19$22.04 data endpoint
Dashboards · Dashboards operation28 / 16 GBzustandslos€183.00$212.282 × €82$95.12 per node + €19$22.04 data endpoint
Dashboards · Dashboards group34 / 16 GBzustandslos€332.00$385.123 × €91$105.56 per node + €59$68.44 data endpoint

Net amounts plus 19% VAT., excluding term discount and region factor. Storage billed by consumption — Object Storage in the Data Platform, offloaded Kafka segments — is not included. The management markup of 1.1714 in the calculated rows is reverse-engineered from the maintained "ClickHouse Analytics M" plan: the price maintained there against a raw configuration of €161.35$187.17 consisting of instance and block storage.

When to use analytics, when to use databases

Both categories are next to each other in the menu and share two services. The dividing line runs between questions: analytics answer questions about many operations, databases answer those about a single one.

Comparison of use cases for analytics and managed databases
Question to the data
AnalyticsHow does a metric behave across millions of operations?
Managed databasesWhat is the status of this single operation?
Access pattern
Analyticsfew columns across very many rows
Managed databasesone row via the primary key
Write operations
Analyticsbatched, in large blocks, rarely changed
Managed databasesindividual, immediately visible, frequently changed
Consistency
Analyticsresult may be seconds old
Managed databasestransaction, immediately binding
Changes
Analyticsappend, rarely correct
Managed databasesmodify and delete as the norm
Who reads
AnalyticsAnalytics, reports, dashboards
Managed databasesthe application itself, in every call
Retention
Analyticsmonths to years, compressed
Managed databasesas long as the operation lives
If the service fails
Analyticsanalytics are missing, the application continues to run
Managed databasesthe application stops

The rows are decision criteria, not features. If you land on the right for more than half of them, you belong under Managed databases.

ClickHouse and Kafka are in both categories

Under databases, both are listed as an engine with a plan; under analytics, in their role in the pipeline. It is one service with one price, not two offerings.

If you only need ClickHouse, without a processing pipeline and dashboards, you book it under databases — with the same scope.

the same service, the same price

The separation lies in the access pattern

A table that is read a thousand times per second via the primary key belongs in PostgreSQL, even if it is only a few megabytes in size. One that is fully computed every hour belongs in ClickHouse, even if it is small.

The data volume determines the size class, not the category.

not in the data volume

Where both are used together

Coexistence is the norm. Three divisions that have proven successful in operations.

Business data in PostgreSQL, analytics in ClickHouse

The application writes to PostgreSQL; the changes go via the transaction log into the columnar database. Analytics therefore no longer load the application's database.

Events via Kafka, state in PostgreSQL

Kafka carries the stream of events and decouples producers from consumers. The derived state remains in the business database; Kafka does not replace it, but feeds it.

Valkey as cache, ClickHouse as source

Recurring analyses are stored in Valkey, an in-memory key-value store. The response time drops to milliseconds without the analysis itself being duplicated.

What is asked before the first route

9 questions that regularly come up before an enquiry. The answers use the same catalogue values as the sections above.

Can't find your question? Write to us about your route.

Which of the five services do I really need?

The raw zone in Object Storage belongs in every pipeline — only from there can an incorrect transformation be rolled out again. Kafka is only needed if you ingest an event stream that multiple consumers read at their own pace; files, change data and the HTTP endpoint can do without it. OpenSearch is worthwhile if the answer is in the text, such as in logs.

Calculate your pipeline

How much does a terabyte of raw data cost in ClickHouse?

In Analytics M, the smallest class, at 10:1 around 4.9 TB of raw data fits into 500 GB of storage. The monthly price divided by this amount gives the amount per terabyte; it decreases for more compressible data.

per terabyte of raw data and month, net€38.71$44.90

Compression by data type

How long does an event remain retrievable in the stream?

In Stream S at 1 MB/s continuous load around 5.7  days: The storage of one broker is usable because every message is stored in 3 copies. If you want to retain data longer, you can offload older segments to Object Storage — where the object storage price applies instead of the block storage price.

Retention per broker class

Why are ClickHouse and Kafka also listed under databases?

Under databases, both are listed as an engine with a plan, under analytics in their role in the pipeline. It is one service with one price: the Kafka and ClickHouse classes on this page are taken unchanged from the product catalogue.

Managed databases

Where do the amounts for OpenSearch, Data Platform and Dashboards come from?

These services do not yet have their own catalogue plan; their amounts are calculated from catalogue values. Instances and storage are included with a management markup of 1.1714, which is reverse-calculated from the maintained ClickHouse plan. The calculation of each class is open in the size classes table.

All classes with origin of the amount

Can I start the pipeline small at first?

Yes. You book Kafka and ClickHouse individually in the configurator, the other three services are available as a quote; the cheapest entry is Dashboards Team. A class can be upgraded later; the raw zone in Object Storage remains in place with every change.

Entry per month, net€61.00$70.76

Calculate pipeline

Where do the analytics services run, and where is the data stored?

Kafka and ClickHouse run as managed services at two locations in Germany; you choose the location in the database configurator. The raw zone is located in the Object Storage of the same location, and no service in the pipeline leaves the EU.

Raw zone and storage

How fast does support respond, and how do I reach them?

Via ticket in the account: The price includes the basic support of the SLA with an initial response in 8 hours for critical incidents (P1), available Monday to Friday from 08:00 to 18:00. Initial response means: A human has accepted the report, classified it and reported back the processing status — the SLA does not guarantee a resolution time. In addition to basic support, it offers three further support levels; the highest responds to P1 in 15 minutes.

Is there a minimum term, and how do I cancel?

Not without a term commitment: You can delete services billed by the hour at any time without notice in the console or via the API, and billing ends at the time of deletion (Section 11 paragraph 3 of the Terms and Conditions). You can cancel monthly contracts with one day's notice to the end of the term, contracts for 12 or 24 months with 30 calendar days — otherwise they renew for twelve months (Section 11 paragraph 2 of the Terms and Conditions). You pay the term in advance and receive a 5% or 8% term discount in return.

Calculate pipeline

Pipeline in the configurator or as a request

You book Kafka and ClickHouse in the database configurator, with the same catalogue rates as on this page. We confirm Data Platform, OpenSearch and Dashboards as a quote — pre-filled with the pipeline you calculate above. Every calculation behind it is openly available on this page.

Services
5
Size classes
13
Entry
€61.00$70.76
Storage per GB
€0.0070$0.0081