1. Scope

1.1 These Event Streaming Specific Terms apply to the managed message brokers that ON DIVERSITY CLOUD EUROPE, S.L. ("DIVERSITY") provides under an Order Form.

1.2 The work of building integrations and pipelines on the brokers is governed by the Professional Services Specific Terms (/contracts/professional-services/). These Specific Terms supplement the General Terms (/general-terms/) and the Acceptable Use Policy (/acceptable-use-policy/). They do not repeat what those documents settle. In particular, fees, invoicing and late payment (General Terms, Section 7), suspension (Section 8), personal data (Section 9 and the DPA), confidentiality (Section 10), liability (Section 14), notices (Section 18), and governing law and courts (Section 23) apply as written there.

1.3 Where these Specific Terms depart from the General Terms, they say so and prevail, as Section 3.2 of the General Terms provides. Capitalised terms not defined here have the meaning given in the General Terms.

2. Definitions

  • "Broker": a managed message broker provided under these Specific Terms.
  • "Single Instance": a Broker running on one node.
  • "Cluster": a Broker running on several nodes in one site.

3. Description of the service

3.1 Brokers. DIVERSITY provides the following Brokers, each as a Single Instance or a Cluster:

(a) Apache Kafka, running in KRaft mode;

(b) NATS, core and with JetStream;

(c) RabbitMQ;

(d) MQTT, with Eclipse Mosquitto;

(e) ActiveMQ.

Debezium and Kafka Connect are available for integration with other systems. They are not Brokers.

3.2 Fully managed. "Fully managed" means exactly four things:

(a) patching and version upgrades;

(b) monitoring and alerting;

(c) backup and restore (Section 4);

(d) high availability and failover within one site, on a Cluster only.

A Single Instance has no failover. Failover between sites is not included: it is designed and bought separately.

3.3 External databases. Debezium reads a database outside DIVERSITY's network only if the database reaches DIVERSITY over direct peering or Private Link (/contracts/private-link/), and only over TLS. DIVERSITY does not read databases over the public internet.

3.4 Location. Each Broker runs in the site the Customer selects in the Order Form (General Terms, Section 9.4).

4. Backups

4.1 Each Broker is backed up every hour. DIVERSITY keeps 24 hourly, 7 daily, 4 weekly, 12 monthly and 3 yearly backups.

4.2 This schedule applies to Event Streaming only.

5. Service levels and support

5.1 Brokers are covered by the 99.9% availability commitment (General Terms, Section 5.2). DIVERSITY makes no commitment on latency.

5.2 DIVERSITY's response to a monitoring alert follows the Customer's support level under the Support Specific Terms (/contracts/support/).

6. Discovery Call

Before an engagement, DIVERSITY offers a free 60-minute discovery call with an engineer, followed by a written diagnosis within one week. The call and the diagnosis do not oblige either party to enter into an Agreement.

7. Term and billing

7.1 The size of each Broker and its term are stated in the Order Form. Section 16 of the General Terms applies unless the Order Form provides otherwise.

7.2 Brokers are billed as the Order Form sets out. Prices appear only in the Order Form.

8. End of service

Section 17 of the General Terms applies to Brokers. The exportable data and formats are those listed in the Order Form or, where it does not list them, in the register on the Data Act page (/data-act/, Section 6.2).

9. Exclusions

Unless the Order Form provides otherwise, Event Streaming does not include:

(a) failover between sites;

(b) failover on a Single Instance;

(c) a latency commitment;

(d) reading databases over the public internet;

(e) the build work on the Brokers, which is a professional service.