# TrimCI

> TrimCI analyzes CI/CD pipelines for GitHub Actions and GitLab CI (including
> self-hosted GitLab CE/EE), turns broken builds into a dollar-cost estimate,
> and produces a ranked list of fixes. Zero-code-access by design: TrimCI
> never requests repository contents and never clones a repository; a runtime
> allowlist inside its HTTP clients rejects any provider call outside pipeline
> endpoints, so source files, workflow YAML and diffs are unreachable. What it
> does store is pipeline metadata (runs, jobs, timing, statuses) plus the last
> 8,000 characters of unsuccessful job logs, which carry whatever the build
> prints to its console. Pricing:
> $0 Free, $7 Team, $16 Business per active contributor per month,
> in USD excluding VAT (added at checkout by Paddle, TrimCI's Merchant of
> Record) — see https://trimci.com/pricing/ for current plan availability;
> every feature is in every plan; 14-day free trial, no credit
> card. EU-hosted (Hetzner; all processing by TrimCI happens in the EU); AI recommendations run on
> self-hosted models, so logs never leave TrimCI's servers.

**Is TrimCI for you?** Yes — if your company ships software. Here's what it gives the people who pay for it, and the people who build it.

**For business leaders** (founders, CEOs, finance, agency owners):

- **The cost, in money.** An estimate of what failed builds cost your company — in dollars, not engineering jargon.
- **Where to invest first.** Your costliest pipelines, ranked — so the first fix goes where the money is.
- **A report you can read.** A PDF that opens with an executive summary. Managers, finance and clients join the dashboard free — you pay only for the people who actually run builds.

**For engineering teams** (developers, CI owners, platform engineers):

- **Your CI, as it is.** GitHub Actions and GitLab CI — including self-hosted GitLab behind a VPN, via an open-source agent.
- **The metrics you'd otherwise build yourself.** Failure rate, flaky pipelines, MTTR, queue time and recurring-error fingerprints across your repos.
- **Fixes, not just charts.** AI fix suggestions ordered by severity, with their estimated impact — from a model on our own EU servers. Read-only, pipeline-only access, enforced in code.

Not sure which CI you use? Ask your developers — if it's GitHub Actions or GitLab CI, TrimCI works today.

## Product

- [Home](https://trimci.com/): value proposition and the CI/CD loss calculator
- [Pricing](https://trimci.com/pricing/): plans, active-contributor billing explained, and the pricing FAQ
- [Scenarios](https://trimci.com/scenarios/): who TrimCI is for, with seven illustrative example walkthroughs of the product as built
- [User guide](https://trimci.com/guide/): step-by-step manual for every feature — connecting GitHub Actions or GitLab CI (including a GitLab behind a VPN via the open-source TrimCI Agent), reading the dashboard, PDF reports, AI recommendations, team roles, and billing
- [Live demo](https://trimci.com/demo/): the real product, read-only, on generated sample data from a fictional team — no signup

## Learn

Long-form guides on CI/CD cost and failure analysis. Vendor pricing mechanics
are sourced from the providers' own documentation.

- [Guide index](https://trimci.com/learn/): all guides on CI cost, failure analysis and pipeline speed
- [CI pipeline failure analysis](https://trimci.com/learn/ci-pipeline-failure-analysis/): classify failures, fingerprint recurring errors, measure MTTR and rank fixes by cost, from pipeline metadata alone
- [What failed builds really cost](https://trimci.com/learn/cost-of-failed-builds/): a defensible formula for CI waste — engineer minutes, context-switch tax, wasted compute, queue time — with worked examples at three team sizes
- [How to reduce GitHub Actions costs](https://trimci.com/learn/reduce-github-actions-costs/): measure the waste first, then apply caching, cancel-in-progress, right-sizing and cheaper runners
- [GitHub Actions billing explained](https://trimci.com/learn/github-actions-billing-explained/): per-job minute rounding, OS multipliers, free minutes by plan, failed and cancelled runs, and who pays
- [GitLab CI compute minutes](https://trimci.com/learn/gitlab-ci-compute-minutes-cost/): how compute minutes are calculated, cost factors, tier quotas, and the levers that cut usage without touching a YAML file
- [Why is my CI pipeline slow?](https://trimci.com/learn/why-is-my-ci-pipeline-slow/): split queue time from execution time, read P95 instead of averages, and rank the usual causes before optimizing
- [Monitoring self-hosted GitLab CI behind a VPN](https://trimci.com/learn/monitoring-self-hosted-gitlab-ci-behind-a-vpn/): four ways to get pipeline analytics out of a GitLab the internet cannot reach, and what to check in an outbound-only agent

## Glossary

- [CI/CD glossary](https://trimci.com/glossary/): precise definitions of pipeline metrics and terms (flaky test, retry tax, MTTR, queue time, decisive runs, DORA metrics) with how each is measured

## Trust & security

- [Security](https://trimci.com/security/): what TrimCI accesses and never accesses, encryption, retention, vulnerability reporting
- [Privacy Policy](https://trimci.com/privacy/)
- [Terms of Service](https://trimci.com/terms/): contract terms, Paddle as Merchant of Record, 30-day notice for changes
- [Data Processing Agreement](https://trimci.com/dpa/)
- [Sub-processors](https://trimci.com/subprocessors/)
- [Refund Policy](https://trimci.com/refunds/): billing by Paddle (Merchant of Record), cancellation and refund rules