A price tag on every merge request

Every merge request shows what its AI will cost to run. Over budget, a person signs off before it merges.

How the gate works

  1. The merge request pipeline counts the AI calls the change adds or removes and prices the difference per month.
  2. It decides go, downgrade or block against the team's budget in .slash/policy.yml.
  3. A GitLab Duo flow posts the receipt on the merge request. On block it marks the merge request as Draft and asks a person to approve.

Try it

Paste a file that calls an AI SDK. This runs the same scan and the same decision as the pipeline. No AI calls, nothing stored.

Stage-Gate

Every main pipeline proves all nine DevSecOps stages, each with a check that can fail and a link to the evidence.

Loading…

Live from the project

The gate's latest decisions on real merge requests, read from the project's public pipelines.

Loading…