Operate
Real-time tracking
Track a repository so every push to its branch is re-analyzed without AI, with alerts when the code needs a new component, when the cost changes or when a security finding appears.
Tracking is available on Pro and above.
What tracking does
Connect a project's repository once. On every push to the tracked branch, Brunel downloads the new commit, re-runs the detectors and the security check (deterministic, no AI) and compares with the baseline:
- New or removed components: the code now needs a queue, a cache, a database, a worker…
- Cost impact: the monthly estimate of the current design after the change.
- Security: new findings, and findings that disappeared.
Each change produces a tracking alert in the project, and in Slack or on your signed webhook when notifications are set up (Business and above).
How Brunel hears about pushes
| Mode | How | When to use |
|---|---|---|
| Repository webhook | Brunel creates a webhook on the repository with a secret | You administer the repository |
| GitHub App | The Brunel GitHub App's single webhook delivers the events | Your organization installed the app; nothing is created on the repository |
| Manual | You add the webhook yourself with the URL and secret Brunel shows | You cannot let Brunel create webhooks |
Webhook deliveries are authenticated with an HMAC signature and a constant-time comparison. The watch shows whether GitHub's first ping arrived, the last event and the last error.
Check now
Check now re-analyzes the tracked branch immediately, without waiting for a push.
Stop tracking
Stopping removes the webhook Brunel created and forgets the watch's baseline.
Related
- Pull request reviews: the same analysis on a pull request, before merge.
- Reliability certificates: a tracked repository is re-evaluated on every push, and a commit that no longer meets its level revokes the certificate.