Getting started
Create your account, verify your email, and set up your organization — every new workspace starts on a full-featured free trial.
TrimCI analyzes your CI/CD pipelines — failures, wasted time, and their estimated cost — without ever asking for access to your repository. Setting up takes a few minutes: create an account, verify your email, and you land in a workspace that already has every feature unlocked.
Simplified illustration — the real screens hold more detail, but the labels and steps match the app.
Step by step
-
Create your account
Open the registration page and fill in an organization name (your workspace — usually your company or team name), your email address, and a password. Accept the Terms of Service and Privacy Policy, then press "Create account".
-
Verify your email
TrimCI emails you a verification link; your account stays inactive until you click it. The link is valid for 72 hours — if it expires or the email never arrives, use "Resend verification link" on the sign-in page.
-
Sign in
After verification you can sign in with your email and password. You land on the dashboard of your new organization — empty for now, because no pipeline data has been connected yet.
-
Know your trial
Every new organization starts a 14-day trial with Business-plan limits: the 60-day history window, hourly sync, and automatic spike detection. No credit card is required, and nothing is deleted when the trial ends — the workspace simply continues on the Free plan until you upgrade.
-
Connect your first provider
TrimCI needs pipeline metadata to analyze. Continue with the chapter that matches your CI provider: Connect GitHub Actions · Connect GitLab CI
Invited by a teammate? Open the invitation email and follow its link instead — you will join their existing organization, and the organization-name field becomes optional during sign-up.
Zero code access, by design: TrimCI never requests repository contents, and a runtime allowlist inside its HTTP clients rejects any provider call outside pipeline endpoints — so source code, workflow files and diffs are unreachable. What it does read is pipeline metadata (runs, jobs, timing, statuses) plus log excerpts of unsuccessful jobs, which carry whatever your build prints.