Grace works where your team already works.
Not another dashboard to remember to open. Grace sits on the webhooks, the error tracker, and the channel your team already watches, and it shows up as a pull request when there's something to do.
Connected today
- GitHub
- GitLab
- Sentry
- Datadog
- Slack
Repository monitoring
Grace never sleeps on your default branch.
On every push and every pull request, Grace reads the change and looks for regressions, fresh technical debt, and security holes, before any of it is merged. Each PR gets a comment with what the analysis found and, when it's warranted, a suggested fix.
- 01
Push / PR opened
The webhook fires
- 02
Analysis
Regressions, debt, security
- 03
PR comment
What was found, and why it matters
- 04
Suggested fix
When there's something to fix
Auto-remediation
Turn the alert into a pull request.
When an error surfaces in Sentry, Grace reads the stack trace, traces it back to the cause in your code, and opens a corrective pull request. You review the diff, you merge. That's the whole loop.
- 01
Error in Sentry
The alert reaches Grace
- 02
Root cause
Stack trace mapped to the code
- 03
Corrective PR
Tested, explained, reversible
- 04
You approve
Or you don't. It's your branch
What it looks like on the pull request.
The analysis lands where the review already happens. No new tab, no new login, and nothing merged on Grace's initiative.
The new /admin/export route reads every row for the account but never checks the caller's role. Two existing tests cover the happy path; neither covers an authenticated non-admin.
- Missing role check on a data-export route
- No regression on the 3 revenue paths
- Build, lint, and 61 tests pass
→ Grace can open a fix on a branch off this PR. Reply /grace fix to have it drafted.
Illustration of a Grace review comment. Findings and wording depend on your code.
What Grace connects to, and what it does there.
Connecting the repo is the only step that isn't optional. Everything else is there to shorten the distance between an alert and a fix.
GitHub
Webhook · Push & PR
Reads the change, flags regressions, and comments the analysis on the pull request
GitLab
Webhook · Push & MR
Same behaviour as GitHub, on merge requests
Sentry
Error alerts
Reads the stack trace, finds the root cause, opens a corrective PR
Datadog
Monitoring & alerts
Correlates a performance anomaly with the cause in the code
Slack
Notifications
Weekly repo health summary, and critical alerts as they land
| Integration | How it connects | What Grace does |
|---|---|---|
| GitHub | Webhook · Push & PR | Reads the change, flags regressions, and comments the analysis on the pull request |
| GitLab | Webhook · Push & MR | Same behaviour as GitHub, on merge requests |
| Sentry | Error alerts | Reads the stack trace, finds the root cause, opens a corrective PR |
| Datadog | Monitoring & alerts | Correlates a performance anomaly with the cause in the code |
| Slack | Notifications | Weekly repo health summary, and critical alerts as they land |
A webhook is read access, not a blank cheque.
Grace listens, analyses, and proposes. It opens branches and pull requests; it never merges and never pushes to your default branch. The repos in scope, the level of autonomy, and who gets notified are all yours to set, and a data-residency / EU hosting option is available.
Connecting the repo takes a minute.
The audit runs on it straight away, and you see what Grace sees before you wire anything else up.