Databases and cachesAutomatic RootManage tools + our team

Apache Kafka management and support in India

Kafka moves large streams of events between systems, and its operation is about disks, partitions and consumers keeping up. Brokers fill disks if retention is wrong, and a stalled consumer shows up as growing lag. RootManage runs Kafka clusters: sizing, retention, security, monitoring of lag and rolling upgrades.

What our engineers handle on Apache Kafka

This is the hands-on work, done by a person: the jobs the automatic tools cannot do for you.

  1. 1Plan brokers, partitions and replication to match throughput and safety needs
  2. 2Set retention by time and size and watch broker disks
  3. 3Secure the cluster with TLS and authentication, and limit topic access
  4. 4Monitor consumer lag and under-replicated partitions, and perform rolling upgrades

Problems we fix

Problem

A broker disk is full

What we do

We lower retention or add space safely, rebalance partitions and add alerts for disk use.

Problem

Consumer lag keeps growing

What we do

We check consumer health and partition counts, add consumers or fix slow processing.

Problem

Leader elections keep happening

What we do

We check network, JVM pauses and broker load, and tune the settings that cause timeouts.

Automatic tools, and our team for the rest

RootManage is automatic server management with every tool in one place. The tools run by themselves on a schedule and report to one dashboard. Everything they cannot do, and every emergency, is handled by our engineers by hand.

Manual, by our engineers

Everything else, and every emergency

  • Hands-on work. Fixes, tuning, migrations, upgrades and the other jobs listed above on this page.
  • Emergency work. A hacked site, an outage or a failed update is handled by a person who investigates and fixes it, not by a script.
  • Things we do not automate. Anything the tools do not cover is done by hand, over SSH, WHM or RDP, on a login you can remove at any time.

The tools are optional, run on Linux servers and are installed by you with one command each. Every job our team does is recorded as a task in your dashboard with the details, and you get an email when it is updated.

How it works

  1. 1

    Sign up

    Create an account, choose a plan and add the server you want managed.

  2. 2

    Install the tools

    Run one command per tool. They then work by themselves and report to your dashboard. For hands-on work you give us a login you can remove at any time.

  3. 3

    Automatic, with people behind it

    The tools watch, scan and back up automatically and alert you. Our engineers do the rest by hand and handle every emergency, and you follow each task in your dashboard.

Questions about Apache Kafka

Do I need Kafka?

For high-volume event streams, often yes. For ordinary job queues, RabbitMQ or Redis is much simpler. We say so before you commit.

Do you manage Kafka Connect and Schema Registry?

Yes. We run Kafka Connect, Schema Registry and the other components on servers you own, together with the brokers, and keep them on matching versions.

What does it cost to have Apache Kafka managed?

Managed plans start at ₹1,999 a month for one server, and Apache Kafka is managed as part of the server. The pricing page lists what each plan includes. If a server is already infected, the emergency cleanup is a one-time ₹9,000 job.

More in Databases and caches