Turn failing CI/CD pipelines into 30-second explanations.
Exlogare reads your pipeline logs, finds the root cause, and posts a fix-ready analysis straight to your merge request. Connect GitLab in under 5 minutes.
No credit card · GitLab · Setup in under 5 minutes
$ pytest -q
FAILED tests/test_billing.py::test_charge_retry
E sqlalchemy.exc.OperationalError: (psycopg2.OperationalError)
E connection to server at "db" (10.0.0.7), port 5432 failed
E FATAL: password authentication failed for user "exlogare"
...47 more lines truncated...
Postgres auth rejected — `DB_PASSWORD` changed, secret not rotated in CI.
The job test connects as exlogare using $DB_PASSWORD. The CI variable was last updated 3 weeks ago; the database password was rotated yesterday (commit a74f3e0).
Pipeline failures steal more time than the bugs themselves.
Every team loses hours every week scrolling through logs to explain the same categories of failures over and over.
Hours lost to "why did this fail again?"
Your senior engineers are the default on-call for every red pipeline. That's the wrong bottleneck.
50,000 lines of logs, one real culprit
Stack traces, retries, flaky tests, broken images — the signal is buried. Searching is slow, guessing is expensive.
Midnight pings on the same class of error
Nobody writes a postmortem for the 11th "cache layer missed" — it just wakes someone up again.
Three steps. Under five minutes.
Connect once. From then on, every red pipeline gets a human-readable RCA inside the merge request it broke.
- 01
Connect GitLab
Webhook, OAuth app, or personal access token — whichever matches your governance. Works with gitlab.com out of the box.
- 02
A pipeline fails
Exlogare fetches the failed job logs, strips noise, and runs our automated analysis on the relevant window.
- 03
The fix lands in MRs, Issues, or chat
Structured RCA — likely cause, file/line, suggested patch, and confidence — delivered to a GitLab MR note, Issue, or your messenger in under 60 seconds.
Built for the real flow of a DevOps team.
Nothing decorative. Every feature below exists because a DevOps team asked for it on day one.
AI root-cause analysis
Logs are chunked, deduplicated, and scored before they hit our analysis layer — you only pay for the signal that actually matters.
GitLab webhook + OAuth
OAuth with polling, webhook-only, or both — same analysis pipeline. Pick whichever matches your governance.
Jenkins support
Drop a small post-build step and Exlogare ingests the build log the same way it ingests GitLab jobs.
Slack · Telegram · Matrix
Route RCAs to the channel or group that actually owns the failing service — not to a generic #ci-alerts firehose.
Pipeline trends
See which failure classes are getting more frequent, which jobs are flakiest, and which fixes actually stuck.
Self-hosted — coming soon
A self-hosted distribution is on the roadmap for teams that need Exlogare inside their own VPC. For now the managed SaaS is the only supported deployment.
Answers to the questions every DevOps lead asks first.
Can we self-host Exlogare?
Not yet. Today Exlogare is available as a managed SaaS at api.exlogare.net only. A self-hosted distribution is planned for a future release — drop us a line at hello@exlogare.net if you need early access.
Do you store our logs?
No. Incoming logs are processed in memory by our analysis layer and discarded as soon as the RCA is produced. We persist only the generated RCA text and the minimal metadata we need to route it (project, pipeline URL, MR ID, severity, confidence).
Where does our data live?
On the infrastructure you connect. The pipeline logs themselves stay inside your CI system. What we keep on our side is just the generated RCA text and the routing metadata — no raw log ever lands in our database.
Does it work with Jenkins?
Yes. A small post-build script POSTs the build log to Exlogare; from there the pipeline is identical to the GitLab flow.
Is there a free tier?
Yes — 20 RCA analyses total (lifetime) on the Free plan, no credit card. After that you can buy a pack or upgrade to Startup.
How do you handle secrets in logs?
Log chunks are passed through a redaction layer (tokens, JWTs, AWS keys, GitLab tokens, basic-auth URLs) before our analysis layer sees them. The raw log is held in memory only for the duration of the analysis and is never written to our database.
Set up in 5 minutes. Free for the first 20 analyses.
Connect your first GitLab project, break a pipeline on purpose, watch the RCA land in the MR. That's the entire demo.