How it works

1. 01

   Install

   Install on the repos you pick, up to 50.

2. 02

   Rank

   One run ranks jobs by CI time and prices each one.

3. 03

   Apply

   You take a patch, or we open a draft pull request that you merge. If a later workflow edit changes the projected runner cost, you get emailed.

What you get

• The bill by job

  Which jobs took the time, and what that costs on published rates.

  GitHub's invoice does not name the job.

• A change you can apply

  The measured numbers plus the workflow edit. You can hand that to an AI agent, or we open the pull request.

  A prompt on the file does not count the runs.

Honest limits

• GitHub's install screen asks for write. We only write when you click Apply. We open a draft pull request. If GitHub refuses drafts, we open a ready-for-review pull request. You merge it. Draft and ready pull requests can still run workflows. If we cannot open a pull request, you get a patch.
• We use published GitHub and Blacksmith list rates, not your invoice. Public and self-hosted runners show minutes, not dollars.
• Installation tokens are never stored. They are minted for each step and thrown away.
• No SOC 2, no HIPAA, no trust center.

Data & SecurityPrivacy

FAQ

1. 01Why not paste ci.yml into an AI agent?

   Pasting ci.yml into an AI agent skips the runs. We read ninety days of them, newest 25 per workflow, from start to finish. Then we rank the jobs and price each off the runner.

2. 02What does write do?

   GitHub's install screen asks for write. We only write when you click Apply. We open a draft pull request. If GitHub refuses drafts, we open a ready-for-review pull request. You merge it. Draft and ready pull requests can still run workflows. If we cannot open a pull request, you get a patch.

3. 03Who is behind this?

   Léo Duquesnel, a principal engineer in San Francisco. Personal time. No cofounder. Bravoure is not incorporated and is not affiliated with bravoure.ai.