Flow observability for data pipelines and services
Know which part broke, and why, in minutes.
Draw your system: databases, proxies, Kafka, queues, APIs. MDJaada checks every part, and when something fails it tells you the likely cause, what changed upstream, and shows the evidence.
Already a customer? Log in
- 14-day free trial, no card needed
- The agent runs in your network and only connects out
- Running in about 10 minutes
- No code changes needed to start
“orders-api is down.”
Is it the API? The connection pool? The database? The migration someone ran at 05:16? Kafka? Most alerts tell you where it hurts. Your team then spends the first half hour of every incident working out where it started. MDJaada does that part for you.
See it in action
Watch MDJaada find a real failure
Short videos on a real system: what MDJaada does, how to go from sign-up to your first incident, and what's new.
MDJaada in 90 seconds
The problem, how MDJaada follows a failure back to where it started, and why teams use it.
Getting started: from sign-up to your first incident
Create an account, install the agent on Linux, draw your system, and watch MDJaada catch a database failure.
What's new: templates, team invites and status pages
Start from a template, tidy the map, invite your team as editors or viewers, and share a public status page.
The videos play from YouTube once you press play.
How it works
Three steps from install to answers
-
1
Install on one server
Unpack the package on a Linux server with Docker and run
./setup.sh. A small agent checks your systems from inside your network. It only connects outwards. Nothing needs to reach in. -
2
Draw your flow
Drag your databases, proxies, queues and services onto the canvas and connect them in the direction data flows. Kafka topics, consumer groups, RabbitMQ queues and Kubernetes services are discovered for you.
-
3
Get the cause, not just the alert
When a part fails, MDJaada opens one incident, ranks the likely causes with the reasons behind each, marks the symptoms, and alerts you in Slack, PagerDuty or email.
Incidents
One incident, ranked causes, the evidence
- Likely causes, ranked. Each with its reasons: first to fail, most upstream, changed just before. Downstream failures are marked as symptoms, so you get one alert instead of ten.
- What changed. Deploys, migrations and Kubernetes rollouts recorded next to the failure: “schema change at 05:16: migration 0042”.
- Evidence from your telemetry. Error spans and log lines from the failure window, grouped, with the full trace one click away. Queried inside your network at the moment it is needed.
- Metrics around the failure. Charts of the suspects from 15 minutes before, with the moment of failure marked.
Queues, streams and metrics
Producer side or consumer side? It says which.
- Kafka as layers. Cluster, topics and consumer groups as separate nodes. A lost broker is reported on the cluster, “no new messages” on the topic (the producer), lag and stalls on the group (the consumer). RabbitMQ and Pub/Sub work the same way.
- Charts on every node. Lag, data age, latency, queue depth: every number is charted for 7 days with your warn and fail lines, and a small trend line sits on each node on the map.
- Your apps' own metrics. Send OpenTelemetry metrics and judge any node on them: p95 latency, error rate in %, pool usage, orders per minute.
- Works with Grafana. A Prometheus endpoint exposes node states, numbers and incidents for your existing dashboards.
Integrations
Checks for the parts your data flows through
Every node type has checks that know what “broken” means for it, from replication lag to consumer lag to a DAG that stopped running.
Databases and stores
- Postgres
- MySQL / MariaDB
- ClickHouse
- Snowflake
- MongoDB
- Redis
- Elasticsearch / OpenSearch
Streams and queues
- Kafka clusters
- Kafka topics
- Kafka consumer groups
- RabbitMQ
- AWS SQS
- Google Pub/Sub
Services and platforms
- HTTP services and APIs
- Proxies (nginx, PgBouncer, Envoy)
- Kubernetes workloads
- AWS CloudWatch
- Azure Monitor
Pipelines, telemetry, alerts
- Airflow (2 and 3)
- MLflow models
- OpenTelemetry traces, logs, metrics
- Prometheus metrics
- Slack, PagerDuty, email
Install
Up and running in under an hour
Sign up and your private MDJaada is ready at once, with your agent key and install command (watch the 3-minute walkthrough). Only a small agent runs on your own servers; nothing is installed on your laptops or inside your applications.
Create your account
Email and password · 14 days free · no card
Confirm your email and MDJaada creates your agent key straight away and shows the install command, already filled in for your account. Then draw your system: databases, Kafka, queues, APIs.
Install the agent, no Docker or Python needed
Linux with systemd (x86-64 or ARM64) · outbound HTTPS only
curl -fsSLO https://github.com/madhubolla2205/mdjaada-releases/releases/latest/download/install.sh
sudo bash install.sh --api https://app.mdjaada.com/api \
--agent-id dc1-agent --flow-name "My system"- Downloads a single-file agent (about 28 MB, database and Kafka drivers inside) and verifies its checksum and signature before installing.
- Asks for your agent key, so it never lands in your shell history.
- Starts on boot and restarts on failure, as its own user with a read-only view of the system.
- Passwords for your databases stay in
/etc/mdjaada-agent/secrets.envon that server.
journalctl -u mdjaada-agent -f # agent logs
sudo bash install.sh --upgrade # newer version (with the newer install.sh), settings kept
sudo bash install.sh --uninstall # remove (--purge also deletes its data)Runs on RHEL/Alma/Rocky 8+, Ubuntu 20.04+ and Debian 10+. Prefer containers? The agent also runs as a Docker container, or inside Kubernetes with read-only permissions. Need everything on your own servers? A self-hosted edition is available. Apps can send OpenTelemetry to any agent on port 4318. Releases: github.com/madhubolla2205/mdjaada-releases. The agent is open source: github.com/madhubolla2205/mdjaada-agent.
Security and data
Built to run inside your network
Self-hosted
MDJaada runs on your own server. Status, incidents, traces and logs stay there. Nothing is sent to us.
Outbound-only agent
Agents in other networks or Kubernetes clusters connect out to your MDJaada server. No inbound ports to open.
Secrets stay on the host
Passwords live in a file on the agent's server and are referenced as env:NAME. They never
enter MDJaada's database.
Read-only
Checks only read: a monitoring user on the database, describe rights on Kafka, read-only RBAC in Kubernetes.
Free trial
Try it on your own system, free for 14 days
- Create an account. Your name, company, email and a password. No card, no call.
- Confirm your email. Your agent key and install command appear straight away.
- Install the agent and draw your system. Every part shows its status within minutes. If MDJaada is not for you, remove the agent with one command.
Start your free trial
- Your own private MDJaada, ready the moment you sign up
- Up to 3 agents and 50 nodes during the trial
- Incidents with the likely cause, alerts to Slack, PagerDuty or email
- Database passwords stay on your server, never with us
Early testers
Help shape MDJaada
MDJaada is new. We are looking for engineers who look after databases, Kafka, queues or data pipelines to try it on a real system and tell us honestly what works and what does not.
- Start the free trial, install one agent and draw a small part of your system.
- Break something on purpose, such as stopping a test database or pausing a consumer, and see whether MDJaada points at the right part.
- Tell us what happened: what confused you, what broke and what is missing. A short email or a 20-minute call both help a lot.
Send us feedback
- Every message is read and answered by the people building MDJaada
- Bugs and ideas for the agent are welcome as GitHub issues
- Testers get help setting up, directly from us
Or write to hello@mdjaada.com
FAQ
Questions teams ask
Do we need to change our code?
No. Health checks, database queries, Kafka lag and the rest work without touching your applications. If your apps already send OpenTelemetry, point them at MDJaada to add traces, log lines and app metrics to incidents.
What does it need to run?
An account, and one Linux server or VM that can reach the systems you want to watch. The agent installs there as a systemd service from a single signed file, with no Docker or Python needed, and only makes outbound HTTPS connections. Systems in other networks get an agent of their own. See Install.
Does it replace Grafana, Datadog or our APM?
No. Those show you everything; MDJaada follows the path between your systems and points at where a failure started. It sits next to them, and exposes a Prometheus endpoint so its findings can appear in Grafana.
Where is our data stored?
Your system map, check results and incidents are kept in your own private MDJaada account, separate from every other customer. Passwords for your databases and queues stay on the agent's server and are never sent to us. Need everything inside your own network? Ask for the self-hosted edition.
How do alerts reach us?
Slack, PagerDuty or email. Incidents can be acknowledged, nodes muted for an hour or a day, and maintenance windows scheduled so planned work does not page anyone.
Is MDJaada open source?
The agent, the part that runs inside your network, is open source under the Apache 2.0 licence, so you can read exactly what it checks and what it sends: github.com/madhubolla2205/mdjaada-agent. The MDJaada web app and service are not open source.
What does it cost?
The first 14 days are free, with no card. To keep using it afterwards, choose a plan based on the size of your system; your flows and settings stay as they are.