PostgreSQL
The relational default
- Data model
- relational + JSONB
- Access
- SQL
- Typical load
- OLTP, mixed
fromโฌ54.46$63.17per month, net

Managed databases from data centres in Germany: Nine engines, 26 plans, from โฌ47.30$54.87 per month net. Billed hourly without a term, or at a discounted monthly rate with a term. ENTRONYX CLOUD handles provisioning, backups, version upgrades and failover, i.e. switching to the running copy.
You choose the project or service, size, deployment, backup and location. Calculations use the same catalogue values as in the configurator, and the database is added directly to the cart.
Without a project, select the service directly below. Each is calculated using the same catalogue values as in the configurator.
The relational default. Managed PostgreSQL with automatic failover, point-in-time recovery and pgvector for embeddings.
The default is PostgreSQL 17; you can set a different major version in the configurator.
โฌ54.46$63.17net / month
+ โฌ9.00$10.44net / month
Daily snapshots, 7 recovery points, stored in the ENTRONYX network.
The discount applies to the monthly net amount; you pay for a term in advance with the first invoice. Hourly billing is only available without a term.
PostgreSQL 17, Essential S, one node: โฌ63.46 net per month.
The wrong engine cannot be cured with more memory. Here are the nine services, ordered by what they store and how they are accessed.
The relational default
fromโฌ54.46$63.17per month, net
For established applications
fromโฌ54.46$63.17per month, net
Memory, not storage
fromโฌ107.75$124.99per month, net
When the schema changes
fromโฌ243.97$283.01per month, net
Sub-second analytics
fromโฌ189.00$219.24per month, net
Events instead of states
fromโฌ353.03$409.51per month, net
Search and analyse logs
fromโฌ59.42$68.93per month, net
A ring without a primary node
fromโฌ96.80$112.29per month, net
Dashboards for everything that provides numbers
fromโฌ47.30$54.87per month, net
Still undecided?
In the finder, you start with your project, such as a web application, sessions, analytics or search, and the appropriate service is preselected.
Two things go wrong: a node fails, or a human deletes something. The replica, a running copy on a second node, helps against the former, while only the backup helps against the latter โ the distance between the two is the most important number on this page.
The primary node writes; the replica, a running copy on a second node, follows the write stream. The journal, the log of every write operation, runs continuously.
Net per month, in addition to the database.
The recovery point is the distance between the last backup state and the failure. It does not depend on the plan, but on the engine.
Three of the nine services keep a journal between two full backups, i.e. the log of every change, and recover to a freely chosen second: PostgreSQL, MySQL and MongoDB. Only what the journal had not yet recorded at the time of the failure is lost there.
The remaining six do not recover to the second; where they back up in snapshots, the worst case is a full day, 1,440 minutes. If you cannot afford this, choose an engine with a journal or a second write path in the application.
Retention does not determine how accurately you hit the mark, but how far back you can go. The accuracy comes from the journal, the range from the tier.

Primary and replica ยท failover under 30 s
A replica keeps the same state as the primary node โ including the accidentally deleted one. ENTRONYX CLOUD therefore keeps the backup separate from it in Object Storage, a dedicated storage service; from tier Managed Backup, it is located in a second region.
A managed database takes operations off your hands, not data modelling โ the two columns show which part lies on which side.
Without additional agreement. The only separate items are retention and the backup journal.
Everything that depends on your application โ and therefore nobody can decide for you.

Nodes ยท ECC memory, local NVMe drives
Every database node runs with registered ECC memory, which detects and corrects flipped bits before they end up in a table, and on local NVMe drives โ fast, directly attached SSDs. Replicas are located in separate fire zones.
26 plans across nine engines, from โฌ47.30$54.87 to โฌ1,666.59$1,933.24 per month. The choice depends on three factors: the working set, the dataset and whether an outage can last minutes or seconds.
| Engine | Plan | vCPU | RAM | Storage | Nodes | Configure | Month |
|---|---|---|---|---|---|---|---|
| PostgreSQL | Essential S | 2 | 4 GB | 80 GB | 1no failover | In the finder โ PostgreSQL Essential S | โฌ54.46$63.17 |
| PostgreSQL | Business M | 2 | 7 GB | 160 GB | 2 | In the finder โ PostgreSQL Business M | โฌ277.25$321.61 |
| PostgreSQL | Business L | 4 | 15 GB | 320 GB | 2 | In the finder โ PostgreSQL Business L | โฌ554.36$643.06 |
| PostgreSQL | Enterprise XL | 8 | 30 GB | 640 GB | 3 | In the finder โ PostgreSQL Enterprise XL | โฌ1,666.59$1,933.24 |
| MySQL | Essential S | 2 | 4 GB | 80 GB | 1no failover | In the finder โ MySQL Essential S | โฌ54.46$63.17 |
| MySQL | Business M | 4 | 15 GB | 320 GB | 2 | In the finder โ MySQL Business M | โฌ554.36$643.06 |
| MySQL | Enterprise L | 8 | 30 GB | 640 GB | 3 | In the finder โ MySQL Enterprise L | โฌ1,666.59$1,933.24 |
| Valkey | Cache S | 2 | 8 GB | RAM only | 1no failover | In the finder โ Valkey Cache S | โฌ107.75$124.99 |
| Valkey | Cache M | 4 | 16 GB | RAM only | 2 | In the finder โ Valkey Cache M | โฌ481.36$558.38 |
| Valkey | Cache L | 8 | 32 GB | RAM only | 2 | In the finder โ Valkey Cache L | โฌ962.87$1,116.93 |
| MongoDB | Business S | 2 | 8 GB | 40 GB | 3 | In the finder โ MongoDB Business S | โฌ243.97$283.01 |
| MongoDB | Business M | 4 | 16 GB | 80 GB | 3 | In the finder โ MongoDB Business M | โฌ483.77$561.17 |
| MongoDB | Business L | 8 | 32 GB | 160 GB | 3 | In the finder โ MongoDB Business L | โฌ941.92$1,092.63 |
| ClickHouse | Analytics M | 8 | 32 GB | 500 GB | 1no failover | In the finder โ ClickHouse Analytics M | โฌ189.00$219.24 |
| ClickHouse | Analytics L | 16 | 64 GB | 2.0 TB | 3 | In the finder โ ClickHouse Analytics L | โฌ549.00$636.84 |
| Apache Kafka | Stream S | 2 | 4 GB | 480 GB | 3 | In the finder โ Apache Kafka Stream S | โฌ353.03$409.51 |
| Apache Kafka | Stream M | 4 | 15 GB | 1.9 TB | 3 | In the finder โ Apache Kafka Stream M | โฌ1,329.99$1,542.79 |
| OpenSearch | Essential S | 2 | 4 GB | 40 GB | 1no failover | โฌ59.42$68.93 | |
| OpenSearch | Business M | 2 | 7 GB | 240 GB | 3 | โฌ386.10$447.88 | |
| OpenSearch | Business L | 4 | 15 GB | 480 GB | 3 | โฌ772.19$895.74 | |
| OpenSearch | Enterprise XL | 4 | 15 GB | 960 GB | 6 | โฌ1,564.10$1,814.36 | |
| Apache Cassandra | Essential S | 2 | 4 GB | 40 GB | 1no failover | In the finder โ Apache Cassandra Essential S | โฌ96.80$112.29 |
| Apache Cassandra | Business M | 4 | 15 GB | 480 GB | 3 | In the finder โ Apache Cassandra Business M | โฌ867.90$1,006.76 |
| Apache Cassandra | Business L | 8 | 30 GB | 960 GB | 3 | In the finder โ Apache Cassandra Business L | โฌ1,597.17$1,852.72 |
| Grafana | Essential S | 2 | 4 GB | Data in the sources | 1no failover | In the finder โ Grafana Essential S | โฌ47.30$54.87 |
| Grafana | Essential M | 2 | 7 GB | Data in the sources | 1no failover | In the finder โ Grafana Essential M | โฌ95.70$111.01 |
The node count is not a performance metric: a second node does not double the throughput, but shortens the outage. The largest plan features 64 GB memory โ enough to keep the working set of most applications entirely in memory.
Strict schemas, true transactions, JSONB for everything that doesn't fit into columns โ and extensions that make a second database obsolete.
The relational default
Managed PostgreSQL with automatic failover, point-in-time recovery and pgvector for embeddings.
fromโฌ54.46$63.17per month, net
| Plan | vCPU | RAM | Storage | Nodes | Month |
|---|---|---|---|---|---|
| Essential S | 2 | 4 GB | 80 GB | 1no failover | โฌ54.46$63.17 |
| Business M | 2 | 7 GB | 160 GB | 2 | โฌ277.25$321.61 |
| Business L | 4 | 15 GB | 320 GB | 2 | โฌ554.36$643.06 |
| Enterprise XL | 8 | 30 GB | 640 GB | 3 | โฌ1,666.59$1,933.24 |
Six services without their own section, but with the same data sheet: major versions, plans with features and price, and an honest differentiation โ what they were built for and what expressly not.
Relational. Fixed schema, foreign keys and transactions โ here in the version for legacy applications that speak MySQL and should continue to do so.
For established applications
Managed MySQL with InnoDB cluster, read replicas and automatic backups.
fromโฌ54.46$63.17per month, net
| Plan | vCPU | RAM | Storage | Nodes | Month |
|---|---|---|---|---|---|
| Essential S | 2 | 4 GB | 80 GB | 1no failover | โฌ54.46$63.17 |
| Business M | 4 | 15 GB | 320 GB | 2 | โฌ554.36$643.06 |
| Enterprise L | 8 | 30 GB | 640 GB | 3 | โฌ1,666.59$1,933.24 |
Schemaless. Structure per record instead of per table. For data where fields can differ between two entries.
When the schema changes
Document database with replica set, aggregation pipeline and Atlas-compatible driver API.
fromโฌ243.97$283.01per month, net
| Plan | vCPU | RAM | Storage | Nodes | Month |
|---|---|---|---|---|---|
| Business S | 2 | 8 GB | 40 GB | 3 | โฌ243.97$283.01 |
| Business M | 4 | 16 GB | 80 GB | 3 | โฌ483.77$561.17 |
| Business L | 8 | 32 GB | 160 GB | 3 | โฌ941.92$1,092.63 |
Analytics. Not built for the individual record, but for throughput across billions of them.
Sub-second analytics
Column-oriented analytics database for billions of rows with sub-second response times.
fromโฌ189.00$219.24per month, net
| Plan | vCPU | RAM | Storage | Nodes | Month |
|---|---|---|---|---|---|
| Analytics M | 8 | 32 GB | 500 GB | 1no failover | โฌ189.00$219.24 |
| Analytics L | 16 | 64 GB | 2.0 TB | 3 | โฌ549.00$636.84 |
Search. An inverted index instead of tables: matches are found via words and relevance, not via keys.
Search and analyse logs
Distributed search and analytics engine with full-text index, aggregations and dashboards.
fromโฌ59.42$68.93per month, net
| Plan | vCPU | RAM | Storage | Nodes | Month |
|---|---|---|---|---|---|
| Essential S | 2 | 4 GB | 40 GB | 1no failover | โฌ59.42$68.93 |
| Business M | 2 | 7 GB | 240 GB | 3 | โฌ386.10$447.88 |
| Business L | 4 | 15 GB | 480 GB | 3 | โฌ772.19$895.74 |
| Enterprise XL | 4 | 15 GB | 960 GB | 6 | โฌ1,564.10$1,814.36 |
Distributed. No primary node, but a ring: every node accepts writes, the copies are distributed across all of them.
A ring without a primary node
Wide-column storage without primary nodes. Every node accepts writes, and copies are distributed across the ring.
fromโฌ96.80$112.29per month, net
| Plan | vCPU | RAM | Storage | Nodes | Month |
|---|---|---|---|---|---|
| Essential S | 2 | 4 GB | 40 GB | 1no failover | โฌ96.80$112.29 |
| Business M | 4 | 15 GB | 480 GB | 3 | โฌ867.90$1,006.76 |
| Business L | 8 | 30 GB | 960 GB | 3 | โฌ1,597.17$1,852.72 |
Monitoring. No storage, but the interface on top โ dashboards across the sources you connect.
Dashboards for everything that provides numbers
Managed Grafana instance for dashboards across metrics, logs and databases.
fromโฌ47.30$54.87per month, net
| Plan | vCPU | RAM | Storage | Nodes | Month |
|---|---|---|---|---|---|
| Essential S | 2 | 4 GB | Data in the sources | 1no failover | โฌ47.30$54.87 |
| Essential M | 2 | 7 GB | Data in the sources | 1no failover | โฌ95.70$111.01 |
Valkey is the open continuation of Redis: the same protocol, the same drivers, the same data structures โ under a licence that explicitly allows it to be run as a managed service. Existing Redis clients connect without modification.
There is no block storage to add: the memory of the plan is the capacity. If the dataset does not fit, the plan is not too small, but the wrong engine was chosen.
| Plan | vCPU | Memory | Nodes | Typical use | Month |
|---|---|---|---|---|---|
| Cache S | 2 | 8 GB | 1no failover | Sessions and object cache of a single application | โฌ107.75$124.99 |
| Cache M | 4 | 16 GB | 2 | Shared cache of multiple services, rate limiting, locks | โฌ481.36$558.38 |
| Cache L | 8 | 32 GB | 2 | Leaderboards and counters with very high request rates | โฌ962.87$1,116.93 |
Two processes run simultaneously: the append-only file (AOF) logs every modifying command and is forced to the drive once per second. The snapshot (RDB) captures a complete image of the memory every hour.
When a node restarts, Valkey reads the append-only file again; at most, the last second is lost. A recovery from the backup, on the other hand, relies on the last complete snapshot โ Valkey does not keep a continuous journal.
The practical rule from this: everything Valkey contains must be rebuildable from another source. If this is not the case, the data belongs in PostgreSQL and only its copy here.
A distributed log instead of a table: every entry remains until the retention period ends, and every consumer reads it at their own pace. From โฌ353.03$409.51 per month, always with three nodes, because a single broker does not secure a log.
Events instead of states
Managed event streaming with KRaft mode, schema registry and Connect runtime.
fromโฌ353.03$409.51per month, net
| Plan | vCPU | RAM | Storage | Nodes | Month |
|---|---|---|---|---|---|
| Stream S | 2 | 4 GB | 480 GB | 3 | โฌ353.03$409.51 |
| Stream M | 4 | 15 GB | 1.9 TB | 3 | โฌ1,329.99$1,542.79 |
Operational characteristics differ less between services than the data models do. Where there are differences, they are in the table โ not in the small print.
For multi-node plans, a sentinel monitors the primary role. If it fails, a replica takes over; the failover typically takes less than 30 seconds. The connection string points to a name, not an address โ your application only needs reconnection logic.
Data at rest is AES-256 encrypted on NVMe, backups are additionally encrypted in Object Storage. In transit, TLS 1.3 with certificate validation applies; a connection attempt without TLS is rejected, not silently permitted.
Each instance gets an endpoint in the vRack, the private network between your servers, and no public address by default. If you need external access, you can enable the public endpoint and provide an allowlist โ empty means blocked, not open.
A Prometheus-compatible endpoint provides connections, buffer hit ratio, replication lag and lock wait times. Slow queries end up in the log and in the console, with an execution plan.
| Feature | PostgreSQL | MySQL | Valkey | MongoDB | ClickHouse | Apache Kafka | OpenSearch | Apache Cassandra | Grafana |
|---|---|---|---|---|---|---|---|---|---|
| Failoverfrom two nodes | Patroni, < 30 s | Group replication, < 30 s | Sentinel or cluster mode | Replica set, election in < 15 s | Replica takes over shard | Partition leader switches automatically | Cluster manager re-elects, < 30 s | no primary node โ ring continues running | Storage recovery |
| Distribute read loadacross additional nodes | up to 5, cross-region | up to 5 | in cluster mode | in replica set | via shard replicas | via consumer groups | additional data nodes | Ring node | โ |
| Storage in plan | up to 640 GB | up to 640 GB | RAM only | up to 160 GB | up to 2.0 TB | up to 1.9 TB | up to 960 GB | up to 960 GB | Data in the sources |
| Major version upgrade | in maintenance window, with pre-check | in maintenance window, with pre-check | rolling, without downtime | rolling, without downtime | rolling, without downtime | rolling, without downtime | rolling, without downtime | rolling, without downtime | in the maintenance window |
| Connection limitGuideline 4 ร vCPU + 100 | Pooler upstream | Pooler upstream | 10,000 concurrent | Driver pool per application | designed for throughput, not concurrency | unlimited, partition count is the limit | Driver pool per application | designed for throughput | Web interface |

Primary nodes and replicas are located in separate fire zones: if an entire room fails, the failover finds the node in the next one. From tier Managed Backup, the backup is stored in a second region.
Nodes ยท separate fire zones
A backup that no one has restored is an assumption. That is why recovery here runs not only in an emergency, but monthly as a random sample โ and always into a new instance, never over the running one.
Once a day, the complete dataset is backed up and stored encrypted โ in tier Snapshots within the ENTRONYX network, from Managed Backup in a second region.
With PostgreSQL, MySQL and MongoDB, the journal runs between two full backups, i.e. the log of every change. It closes the gap between the last full image and the point in time you select later.
You select the tier in the finder or in the configurator. It determines how far back you can go โ not how precisely.
You choose a point in time, we create a second instance from it. The running one remains untouched โ comparing both states is thus part of the process and not its risk.
Every month, a sample is actually restored and checked against the source. Anything noticed during this is an operational procedure and not a discovery in an emergency.
| Engine | Recovery point | Method |
|---|---|---|
| PostgreSQL | per second | Base backup and continuous WAL journal |
| MySQL | per second | Full backup and binlog in ROW format, 7 days |
| Valkey | last full dump | from RDB and AOF, without continuous journal |
| MongoDB | per second | Full backup and oplog |
| ClickHouse | last backup | Full backup per partition |
| Apache Kafka | Retention instead of recovery | Events remain readable in the topic |
| OpenSearch | last snapshot | snapshots of entire indices |
| Apache Cassandra | last snapshot | snapshot and commit log per node |
| Grafana | last export | Dashboards, data sources and users as export |

Backup ยท daily, testing monthly
Daily full, in between the journal. The copy in a second region is included from Managed Backup; for the Snapshots it costs โฌ20.00$23.20 net per month. Every month, a sample is actually restored and checked against the source.
A managed database is only managed if the route to it is also defined. The default is therefore: private, encrypted, with separate roles โ and none of this can be switched off accidentally.
Each instance receives a name in the internal DNS and an endpoint in the vRack, the private network between your servers โ no public A record, no accessible address on the internet. Anyone who needs to access it from the outside must explicitly enable the public endpoint and provide an allowlist; an empty list means blocked, not open.
Included is vRack 1 Gbit/s. More bandwidth costs per month, net: vRack 10 Gbit/s โฌ39.00$45.24, vRack 25 Gbit/s โฌ119.00$138.04, vRack 50 Gbit/s โฌ219.83$255.00 and vRack 100 Gbit/s โฌ421.49$488.93.
Each role has its own password, which can be renewed individually. An application that connects with admin is a finding, not an operating state.

Endpoint ยท private in the vRack, TLS 1.3
The data path runs via the private endpoint in the vRack, TLS 1.3 is enforced. Management has its own connection โ it does not share the line with your queries.
# Get connection string โ TLS is mandatory, not an option
entronyx db uri shop-pg --role app
# postgresql://app:โฆ@shop-pg.fra1.db.entronyx.internal:5432/app?sslmode=verify-full
# Recovery to a point in time within the retention
entronyx db restore shop-pg \
--point-in-time "2026-08-27T21:14:05Z" \
--target shop-pg-restore
# Attach read replica in a second region
entronyx db replica create shop-pg --region hel1 --plan pg-m
The path is the same for every engine: transfer completely once, then continuously catch up until the lag is zero, and only then switch over. A midnight dump is not a migration, it's a gamble.
Size per table, used extensions, character set and collation, roles and permissions, number of concurrent connections, longest running query. Everything that is special on the source becomes visible here โ not just during import.
Memory at least as large as the frequently read part of the data, storage about one and a half times the inventory, number of nodes according to failure requirements. You can upgrade later, but downgrading is not always possible.
Dump or base backup, imported in parallel. Owners and permissions of the source are deliberately omitted and reassigned in the target โ otherwise you drag along roles that do not exist here.
Logical replication, GTID replication or change streams keep the target up to date while the source continues to work. In this phase, you already test the application against the target โ read-only.
Stop write access on the source, wait until the lag is zero, swap connection string, check sequences, enable write access. If you do not measure the lag, you lose records.
The source remains unchanged for a week. This costs little and is the only reliable rollback plan there is for a migration.
# 1. Create target instance, private endpoint in the vRack
entronyx db instance create shop-pg \
--engine postgresql --version 17 --plan pg-m \
--region fra1 --vrack prod --no-public-endpoint
# 2. Transfer schema and data, without owner and permissions of the source
pg_dump --no-owner --no-privileges --format=directory --jobs=4 \
--dbname="$SOURCE_URL" --file=/tmp/dump
pg_restore --no-owner --jobs=4 \
--dbname="$(entronyx db uri shop-pg --role admin)" /tmp/dump
# 3. Continuously catch up until the lag is zero
psql "$SOURCE_URL" -c "CREATE PUBLICATION migration FOR ALL TABLES;"
psql "$(entronyx db uri shop-pg)" -c \
"CREATE SUBSCRIPTION migration CONNECTION '$SOURCE_URL' PUBLICATION migration;"
# 4. Measure lag โ only switch over at 0 bytes
psql "$(entronyx db uri shop-pg)" -c \
SELECT application_name,
pg_wal_lsn_diff(sent_lsn, replay_lsn) AS lag_bytes
FROM pg_stat_replication;"
# 5. Clean up after the switchover
psql "$(entronyx db uri shop-pg)" -c "DROP SUBSCRIPTION migration;"
| Engine | Initial transfer | Continuous | Outage |
|---|---|---|---|
| PostgreSQL | pg_dump / pg_basebackup | logical replication | < 5 min |
| MySQL | MySQL Shell, util.copyInstance | GTID replication | < 5 min |
| Valkey | Import RDB file | REPLICAOF against the source | < 1 min |
| MongoDB | mongodump / mongorestore | mongosync, Change Streams | < 10 min |
| ClickHouse | INSERT โฆ SELECT via remoteSecure() | lag per partition | minutes to hours |
| Apache Kafka | MirrorMaker 2 | MirrorMaker 2 with offset translation | without downtime |
There is no standard path in the table for OpenSearch, Apache Cassandra and Grafana; we will coordinate the migration with you. Discuss migration
Eleven questions that regularly come up before ordering. The answers use the same catalogue values as the sections above.
Can't find your question? Contact us.
Managed PostgreSQL runs in data centres in Germany and costs per plan and month: The smallest plan Essential S runs on one node with 4 GB memory, the largest Enterprise XL on three nodes with 30 GB. The amounts below this answer are net plus 19% VAT and without a contract term; for 12 or 24 months in advance, they decrease by 5% and 8% respectively.
PostgreSQL Essential S, per month netโฌ54.46$63.17
PostgreSQL Enterprise XL, per month netโฌ1,666.59$1,933.24
We provision the node, operating system and engine, perform the backup, monitor operations, fail over in the event of an outage and apply version updates. Schema, queries, size and access rights remain with you.
Usually in under 10 minutes after the order, with a private endpoint and forced TLS. You get a connection string, not a machine to set up.
From two nodes, a sentinel detects the failure, and a replica takes over the write role, typically in under 30 seconds. The connection name remains, the address changes โ your application must be able to reconnect.
As far back as the selected retention period goes: 7 to 365 days. A journal is kept by 3 of the 9 engines; they restore to the second within this time, the others to the last backup โ the table under Backup shows which ones.
Yes. vCPU, memory and storage can be increased during operations, on a rolling basis for multi-node plans; the connection string remains the same.
Not without your action: each instance gets an endpoint in the vRack, the private network between your servers, and no public address. You explicitly enable the public endpoint and provide an allowlist; an empty list means blocked.
The smallest plan is Grafana Essential S with one node, i.e. without failover. With failover, the list starts at MongoDB Business S with three nodes.
Grafana Essential S, net per monthโฌ47.30$54.87
MongoDB Business S, net per monthโฌ243.97$283.01
The databases run at two locations in Germany; you choose the location in the finder or in the configurator. Primary nodes and replicas are located in separate fire zones of the same location, the backup is additionally stored in a second region from level Managed Backup.
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.
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.
In the finder, the price of your database is fixed after a few decisions, and the cart takes it directly. For the migration of existing systems, there is a guide and, upon request, support from our technicians.