Qalytix

The problem

Jenkins tells you whether a build passed or failed. It doesn’t tell you whether a test has been flaky for three weeks, whether a module’s stability is quietly dropping, or which suite is worth fixing first. That data exists — it’s just scattered across build logs nobody re-reads once a build goes green. Qalytix works with any Jenkins job; there’s no dependency on a particular test framework or project.

What it does

Qalytix ingests Jenkins build and test data and turns it into the things a static CI report can’t give you: a live dashboard of what’s building right now, failure trend charts per job over 7/14/30/90-day windows, flaky-test detection with a confidence score rather than a gut feeling, module stability rankings, and historical reports with CSV export for whoever needs the numbers outside the tool. Slack and Microsoft Teams get alerted so failures don’t wait to be noticed.

Built as a real product, not a script

This isn’t a personal dashboard — it’s multi-tenant SaaS from the schema up. Every table carries an org_id, PostgreSQL row-level security enforces isolation as a second line of defense behind the application code, and plans (Free / Pro / Enterprise) gate Jenkins connections, seats, and data retention through Stripe billing. Role-based team management (Owner, Admin, Member) and a super-admin portal for managing tenants come with that territory, not bolted on after.

In use

Qalytix is in active use in production, with customization beyond what’s in the public repo — not just a demo. The base image is also on Docker Hub for anyone who wants to self-host it against their own Jenkins — a docker compose up and a Postgres container is the whole install.

Under the hood

Java 21 and Spring Boot 4 on the backend, PostgreSQL with Flyway migrations, and Spring WebSocket (STOMP) for the live dashboard updates. The frontend is React with TypeScript, Tailwind, and Zustand. MIT-licensed and open source.