CIQuiet — Only run the affected CI pipelines

Incremental CI for solo devs and small teams who hate full pipelines for tiny diffs.

Problem

Indie CI often triggers the entire pipeline for a one-line change, burning runner minutes that hurt most when self-hosted or billed by the minute. A developer already shipped an open-source tool just to fix this, which proves the pain is real enough to spend personal hours on.

Solution

A lightweight pipeline slicer: parses monorepo dependency graphs or file paths, then tells CI which jobs are actually affected and reports the minutes saved. Integrates with GitHub Actions / GitLab CI as a thin layer rather than a full CI rewrite.

Users

Indie devs, 2-10 person teams, and startups running self-hosted runners.

MVP

Generate GitHub Actions path/dependency filters; a one-liner that outputs the affected-job list; a report of skipped jobs and minutes saved; a CLI to preview impact locally on a diff; a simple config schema without rewriting YAML.

Revenue

Open-source CLI plus a paid dashboard for historical savings, team quotas, and optimization suggestions; charged per repo or per seat.

Why now

AI raises commit frequency, which amplifies CI cost, while big-vendor solutions are too heavy. Solo devs need a thin 'plug it in and save' middle layer.