NewWhat CI Actually Looks Like at a 100-Person Team

Your CI fixes itself now.

Mendral investigates every failure, finds the root cause, and opens a pull request with the fix.

SOC 2 Type IIGitHub App, no code accessNo spam

Prefer to talk first? Book a 15-min demo or watch it fix a test in 60 seconds.

YBacked by Y Combinator

Trusted by engineering teams shipping 10,000+ PRs per week

PostHogMetabaseLuminaiInngestClipboard HealthBlaxel
PostHog

Keeping PostHog's CI under control.

“I'm spending a fair amount of time seeing how we can improve our CI/CD reliability and test speed. So my team can ship faster.” That was Tim, co-founder and co-CEO of PostHog, before Mendral. Today, Mendral processes 575,000 CI jobs per week across PostHog's 120-engineer team, autonomously investigating failures and shipping fixes.

Your team stopped flagging CI problems because nothing ever fixed them.

auth.signup1m 52s
auth.signup2m 06s
auth.signup2m 30s
auth.signup1m 44s
auth.signup2m 09s
auth.signup1m 55s
auth.signup2m 01s

Flaky tests

Your team re-runs the suite and hopes it passes. Nobody has time to investigate why. You've normalized a 60% pass rate.

Lint2m 12s
Type check4m 08s
Unit tests8m 34s
E2E tests12m 51s
Build6m 22s
Integration32m 47s
Deployqueued

Slow pipelines

Engineers open a PR and wait 30 minutes to find out if it works. Multiply that by every commit, every engineer, every day.

✗ mainfailing · 2h 14m
CI / testsfailed
CI / buildfailed
CI / deployblocked
CI / stagingblocked
8 PRs blocked · 3 engineers waiting

Broken main

Main is red. 8 PRs are blocked. The person who could fix it is in a meeting. Deployment freeze until someone volunteers.

Other tools quarantine flaky tests.
Mendral actually fixes them.

Most CI tools stop at detection. They flag a flaky test, quarantine it, maybe send a Slack alert. Then it sits in your backlog for months.

Mendral goes further. It investigates the root cause, opens a pull request with the fix, responds to review comments, verifies the fix passes CI, and merges.

Problems that used to live in your backlog forever now get fixed in hours.

Detection toolsMendral
Finds flaky test
Identifies root cause
Opens fix PR
Responds to code review
Verifies fix passes CI
Merges the fix
How it works

From failure to merged fix

1

Investigate

Mendral monitors every CI run in the background across every pipeline. When something fails, it reads the logs, traces the root cause across runs, and figures out why it broke. It correlates patterns across hundreds of CI runs to find issues humans miss.

Analyzing 142 CI runs...
tests / e2e-chrome68% pass rate
→ page.goto timeout in signup flow
Correlated with
parallel suites sharing browser context
Root cause identified
→ test isolation: shared browser session across suites
Fix e2e test isolation#1284
mendral-bot wants to merge into main
tests/e2e/playwright.config.ts
- fullyParallel: true,
+ fullyParallel: false,
tests/e2e/auth.setup.ts
+ await context.close();
+ context = await browser.newContext();
@danielle notified — maintains e2e infra
2

Fix

Mendral notifies the right engineer on Slack, opens a pull request with the fix, and responds to review comments. If the fix doesn't pass CI, it iterates. No fire-and-forget. Your team stays in flow.

3

Merge

Verifies the fix passes CI. Merges. Loop closed.

CI / tests2m 14s
CI / build1m 08s
CI / e2e4m 22s
CI / deploy0m 34s
Merged
main ← fix/e2e-test-isolation

Your team doesn't need another dashboard.
They need problems that fix themselves.

Five minutes to install.
First fix within hours.

Install the GitHub App, connect Slack, and Mendral starts reading your CI logs immediately. First insights within minutes, first fix within hours. No YAML, no infrastructure, month-to-month.

Works with any GitHub Actions workflow. GitLab, Buildkite, and CircleCI support coming soon.

SOC 2 Type IIGitHub App, no code accessNo spam

Prefer to talk first? Book a 15-min demo and we'll connect to a real repo and show you an actual investigation and fix.