Built by the team behind Docker & Dagger.
Automating the DevOps work your engineers shouldn't be doing by hand. Supply chain security, flaky CI, slow builds, and anything else specific to your stack.
Every engineering team has the same problem: shipping faster than they can review, deploy, and debug. The bottleneck moved from typing the code to everything around it: review, CI, deploys, incidents, the eng-ops backlog.
Ramp built an AI agent for it internally. Cloudflare did. Coinbase did. Most teams can't justify a year of platform engineers building agent infrastructure from scratch.
Mendral is that, without the 12-month build. Built by the engineers who scaled Docker's CI, now deployed at PostHog, Metabase, Luminai, and several other teams.
One agent. One memory. What it learns from your incidents and past PRs sharpens every review, CI fix, and triage.
Weighs the diff against your test history and your past incidents.
bug (P1): This refactor to payments/charge-create reintroduces the async race that caused INC-412 (Jan '26 — 3.2% refund failures). Same handler, same pattern.
View suggested change
Knows when a dep is unmaintained, freshly published, or shipping postinstall malware.
security (P1): expr-eval@2.0.2 — two unpatched HIGH-severity CVEs, and the package is unmaintained (last publish 2020). Suggested alternative: mathjs or expr-eval-fork@2.0.2+ (prototype-pollution fix).
View advisories · Prompt for AI agents
Investigates the failure. Opens the fix PR.
VisualReviewClient.request() for 5xx and 429 errors #60391addSnapshots had no retry protection. Transient 504/500 errors failed ~1 CI shard per week since May 8.
Exponential backoff (1s, 2s, 4s) for 5xx. Respects Retry-After on 429. 4xx fails fast.
Deploy timeline, suspect commit, rollback PR. Ready when on-call arrives.
PaymentError in payments-api · refund.chargev2026.5.27.1payments/refactor-chargeIterate in chat. Promote to schedule. Ship what you saw work.
checkout-api +34% on /refund. user-svc +12% timeouts.Mendral connects to the tools where engineering work happens. Signals flow in. Memory holds your team's context. Mendral writes back through the same surfaces: PRs, Slack threads, Linear tickets. The longer it runs, the more useful it gets.
“Mendral saved our a** during the Trivy supply chain attack. The agent had pinned the secure version two weeks before, so we avoided rotating every key across our infra.”
Read the full story →“Mendral has been super impressive for us so far!”
Read the full story →“Mendral has been super helpful for us. It keeps our CI efficient and manageable at scale.”
We spent over a decade shaping DevOps and CI/CD. We built Docker from the ground up, then co-founded Dagger to modernize CI. Now we're putting agents on the parts of CI/CD everyone dreads.
Claude Code, Cursor, Codex, Devin, Copilot — they're great at turning intent into pull requests. But a PR is the start of the work, not the end. Someone still has to review the diff, babysit CI, get paged at 2am, and wire up the deploys. Mendral handles everything after they hit submit.