Invest in shipping speed, not in rerunning CI

Industry data shows flaky tests waste 4+ hours per developer per week on retries, triage, and waiting for CI. Teams using Drape typically see 90% fewer false-red CI runs within the first month, which translates directly into faster merge cycles and more time writing features.

Drape doesn’t just report flaky tests — it suppresses them so they stop blocking your pipeline immediately. Suppressed tests are tracked with expiration dates and linked fix tickets so they get resolved, not forgotten.

No SDK and no code changes. Drape ingests standard formats your tools already produce: JUnit XML for test results, SARIF for security scans and lint results, and Cobertura, LCOV, or Go coverage for code coverage. Use the Drape CLI (available via Homebrew, Docker, or Nix) or the GitHub Action to upload results and get rich PR comments, wait-for-processing, and exit codes. You can also use any HTTP client if you prefer.

Codecov and Coveralls track coverage percentages. Drape is the CI Brain: it reviews every pull request, detects flaky tests, suppresses false negatives with SLAs, enforces line-level coverage guardrails (not percentages), tracks container CVEs, surfaces code quality issues, classifies failures with AI, and feeds structured context to AI coding agents. Coverage tracking is one feature — not the whole product.

You pay for people who were active that month: anyone in your GitHub org who opens, commits to, reviews, or comments on a pull request in a connected repo, or uses Drape. Bots and outside contributors are free, and members who did none of that aren’t billed — so nobody has to remove users.

Yes. 14 days of full features, no credit card required. AI code review during the trial uses your organization’s 5 free review units — the monthly allowance starts when you subscribe to Pro. Free units are granted once and don’t expire.

Yes. Pro is month to month, billed monthly, with no minimums. Annual contracts are available on Enterprise.

Burn-in runs a test many times on the same commit to confirm whether it’s genuinely flaky or if the failure was a one-off. Bisect uses binary search across your commit history to find exactly which commit introduced a regression. Both can be triggered from the Drape UI, via API, or automatically.

Pro includes 20 review units per active user each month, pooled across your organization — a busy repo can use what a quiet one doesn’t. Unused units don’t carry over. Past the allowance, owners buy prepaid credit packs: 100 units for $200, 500 units for $900, 2,000 units for $3,200. Credits last 12 months and are used only after the month’s included units. No overage billing: when the allowance and credits run out, Drape skips the review and says so on the pull request, with a link for an owner to buy more. Reviews pick up again next month, or as soon as credits are bought.

A review unit is one completed review of up to 1,000 changed lines. A bigger change counts once per started 1,000 lines, so a 2,400-line pull request is 3 units. Lockfiles, generated, and vendored files don’t count, and a review of a later push counts only the lines that push changed, so most follow-up reviews are 1 unit. Replies to findings are free, and a review that fails or is skipped is never billed.

No. Failure classification, auto-suppression, and MCP access are included in Pro. Code review is the only AI feature billed by usage.

Enterprise plans include private cloud and on-premises options. Contact sales for details.