Managed Apache Kafka in Germany

Apache Kafka 4.3 in KRaft mode, run by the Strimzi operator in Falkenstein, Germany. TLS on every connection, SCRAM-SHA-512 authentication and a public endpoint your clients reach directly.

  • EU hosted
  • German data centers
  • TLS encrypted

From €19.99/monthOne broker per cluster. See what is not available yet.

Connection settings

Example values
bootstrap.servers
kafka-orders-acme.queues.danubedata.ro:29092
security.protocol
SASL_SSL
sasl.mechanism
SCRAM-SHA-512
Version
Apache Kafka 4.3 (KRaft)
Brokers
One, also the controller
Encryption
TLS, publicly trusted certificate
Location
Falkenstein, Germany

What your cluster includes

  • KRaft, no ZooKeeper

    Kafka 4.3 keeps its metadata in its own KRaft controller. The Strimzi operator deploys the cluster and keeps it in the configured state.

  • TLS on every connection

    The only listener is TLS, with a Let's Encrypt certificate that standard clients already trust. Plaintext connections are refused.

  • Users and ACLs

    Clients authenticate with SASL/SCRAM-SHA-512. Next to the admin user, a cluster can have up to 20 users, each limited by ACLs to the topics and groups it needs.

  • Kafka Studio

    Browse and send messages, manage topics and their settings, and follow consumer lag in the console, the API and the MCP server. Available on request.

What is not available yet

Kafka starts as a single broker. Check this list against your workload before you move it.

One broker per cluster

The broker is also the controller, so every topic has one copy and the cluster is unavailable while it restarts. A three-broker option with replication is planned.

What this means for availability
  • Deny rules, and ACL rules limited to a client address
  • Kafka Connect, MirrorMaker and tiered storage

Connect with the client you already use

Any Kafka client that supports SASL_SSL and SCRAM-SHA-512 can connect. The certificate is publicly trusted, so no CA file is needed.

Producer configuration for the Apache Kafka Java client. The endpoint and username are examples; use the ones of your cluster.

Java
Properties props = new Properties();
// Example endpoint and user: use your cluster's.
props.put("bootstrap.servers", "kafka-orders-acme.queues.danubedata.ro:29092");
props.put("security.protocol", "SASL_SSL");
props.put("sasl.mechanism", "SCRAM-SHA-512");
props.put("sasl.jaas.config",
    "org.apache.kafka.common.security.scram.ScramLoginModule required "
    + "username=\"kafka-orders-admin\" "
    + "password=\"" + System.getenv("KAFKA_PASSWORD") + "\";");
props.put("key.serializer", StringSerializer.class.getName());
props.put("value.serializer", StringSerializer.class.getName());

try (KafkaProducer<String, String> producer = new KafkaProducer<>(props)) {
    producer.send(new ProducerRecord<>("orders", "order-1042", "{\"status\":\"paid\"}"));
}

Keep the password in your environment, not in your code. Read about SCRAM in the Kafka documentation.

Choose a plan for your broker

Each plan is one broker. Billed hourly, up to the monthly price of the plan.

  • DD Isac

    €19.99/moor €0.0274/hr

    CPU
    1 vCPU
    Memory
    2 GB
    Storage
    25 GB
  • DD Golovita

    €39.99/moor €0.0548/hr

    CPU
    2 vCPU
    Memory
    4 GB
    Storage
    75 GB
  • DD Merhei

    €79.99/moor €0.1096/hr

    CPU
    4 vCPU
    Memory
    8 GB
    Storage
    200 GB

From a plan to connected clients

  1. Create a cluster

    Choose a plan and a name. DanubeData deploys the broker, issues its certificate and publishes its endpoint.

  2. Restrict the firewall

    The default firewall opens only the Kafka port. Narrow it to the addresses your producers and consumers use.

  3. Create your topics and users

    Create topics in Kafka Studio or with kafka-topics.sh, kcat or your client's admin API, and set the replication factor to 1. Give each application its own user.

  4. Connect your applications

    Configure SASL_SSL with SCRAM-SHA-512 and the endpoint of your cluster. No CA file is needed.

What customers say

“As a developer and cloud enthusiast, I’ve tried a lot of infrastructure platforms — but DanubeData genuinely stands out as one of the most intuitive, modern, and reliable cloud services I’ve used. From signup to deployment, everything feels thoughtfully designed and developer-centric. Deploying a VPS, cache, or database instance takes under a minute — and that’s not an exaggeration! Their intuitive dashboard and instant provisioning make launching new services effortless, even if you’re just getting started with cloud infrastructure”

Keoma WrightCEO/Founder at OpenWeb.co.za
Cristian TorzsaCEO at InnovaSoftware SRL
Bo PereiraParis-Brest srl
Read more customer stories

Managed Kafka questions

  • Not yet. Each cluster is a single Kafka node that acts as both controller and broker, so every topic has one copy and the cluster is unavailable while that node restarts. A three-broker option with replication is planned but not available today.

    Link to this answer

Stream your events from Germany

Choose a plan, create a cluster and connect your producers and consumers with the client you already use.