What is an AI SRE?
When something breaks, a site reliability engineer gets paged, reads the logs, finds the cause, and fixes it. Between incidents they patch what is vulnerable, update what is stale, and keep deploys healthy. An AI SRE is an AI agent that takes on that work without being asked.
The category is new, and the products in it differ. Most of them, such as Resolve AI, Traversal, Cleric and Datadog’s Bits AI SRE, connect to your logs, metrics and traces, investigate an alert, and give the on-call engineer a likely root cause. Some go on to suggest a fix.
They are built for investigation across large systems, and they are good at it. Bugstack works on a different part of the job: the code change, and the upkeep between incidents.
What it does in a week
Investigating alerts is a small part of what an SRE does in a week. Bugstack does the rest of it too.
- It responds to crashes. It finds the cause in your code, writes the fix, and proves it in an isolated sandbox before you see it.
- It rescues failed deploys. On hosts you have connected. Render is the host supported today.
- It watches for vulnerable packages. Checked every four hours.
- It watches for leaked secrets. Checked every night.
- It keeps packages up to date. Checked every day.
- It leaves a record. Every action is written to a tamper-evident audit log, and every pull request says what happened and why.
Bugstack reports what its scans find, and it can open pull requests for those findings. That part is switched on per account. See how it compares with Dependabot and Renovate.
Telemetry agnostic
Bugstack is built to take problems from whatever you already run.
Its own SDK is the quickest way to start. To use Sentry, Datadog or your own source instead, we connect it with you. You do not have to change monitoring tools, and you do not need one at all.
How Bugstack compares
| An investigation-first AI SRE | Bugstack | |
|---|---|---|
| Takes problems from | Alerts, logs, metrics and traces | Its own SDK, Sentry, Datadog or your own source, plus your host and your repository |
| What you get | A root-cause report, sometimes with a suggested fix | The fix, as a pull request |
| Proof | Varies by product | Every bug fix proven in an isolated sandbox: a test that fails before the fix and passes after, with your suite green. Your own CI runs too |
| When nothing is on fire | Starts from an alert | Scans for vulnerable packages, leaked secrets and outdated packages |
| Scope | Incidents | Crashes, failed deploys, and the upkeep between them |
| Built for | Companies with an SRE team | Teams without one |
The left column describes the category in general. Individual products differ, so check each vendor’s documentation.
What happens when production breaks
One problem, start to finish:
- It hears it. A crash arrives from the Bugstack SDK, or from the telemetry you already run. Repeated crashes become one problem.
- It assigns it. A coordinator reads the problem and picks the specialists the job needs.
- It reproduces it. In an isolated sandbox, the tester writes a test that fails on your current code, for the bug’s own reason, before any fix exists.
- It fixes it. The fixer finds the cause in your repository and writes the smallest change that solves it.
- It proves it. In the same sandbox, the test has to pass with the fix and every other test has to stay green. A fix that doesn’t pass never becomes a pull request. Your own CI runs as well.
- You decide how it lands. The pull request waits for your review, or, on Autopilot, merges itself once it is proven.
See how Bugstack works in full →
You decide how much it does alone
Every change is a pull request, and your CI runs on it. You pick one of three levels for each repository: Suggest, Review or Autopilot. New repositories start on Review, where you do the merging.
You choose what waits for a person at every level. By default that is changes to sign-in and security code, infrastructure changes and rollbacks. Bugstack never rotates a secret itself. Undo opens a revert pull request.
Read how Bugstack handles your code and data →
What Bugstack does not do yet
Bugstack does not watch:
- Wrong answers returned as a success. If the code runs and returns the wrong result, Bugstack does not see it.
- Anything that fails without throwing an error. A job that quietly stops.
- Slowdowns and performance regressions.
- Errors in your users’ browsers. It works on server-side errors.
- Deploys on hosts that are not connected. Render is the only host today.
Bugstack does not replace dashboards, tracing or performance monitoring. Keep those, and let Bugstack act on what they report. See how Bugstack compares with error monitoring.
How well it works
On 25 September 2026 we ran Bugstack against 158 defects planted in real code: our own. All seven problem classes reached the right action at least 80% of the time; for a crash, the right action is opening a fix, which it did on 85% of passes. We then tuned the fixer and tested it on an exam of planted bugs sealed before tuning: on 8 October 2026, 43 of 44 proposed fixes held (98%).
It is not always right. That is why review is the default. See the numbers →
Frequently Asked Questions
What is an AI SRE?
An AI SRE is an AI agent that does the work of a site reliability engineer without being asked. A site reliability engineer keeps software running: they respond when it breaks, fix the cause, and do the upkeep that stops it breaking again. AI SRE products differ in which part of that job they take on. Bugstack takes on the fix and the upkeep.
Is Bugstack an AI SRE?
Yes. Bugstack does the work an SRE does for a software team: it responds to crashes and failed deploys, fixes the cause, and keeps packages and secrets in order. Two things define it. It delivers the fix as a pull request, and it takes problems from whatever telemetry you already run.
Does Bugstack work with my monitoring tool?
Yes. Bugstack is telemetry agnostic: it is built to take problems from whatever you already run. Its own SDK is the quickest way to start. To use Sentry, Datadog or your own source instead, we connect it with you. It also works with no monitoring vendor at all.
Do I need an SRE team to use Bugstack?
No. Bugstack is built for teams without one, where the person who gets paged is the person who wrote the code. Book a demo and we set it up with you.
Is it safe to let an AI SRE change production code?
With Bugstack, every change is a pull request and your CI runs on it. You pick one of three levels for each repository, and new repositories start on Review, where you do the merging. Before Autopilot merges a bug fix, Bugstack proves it in an isolated sandbox: a test must fail before the fix and pass after, with the rest of your suite green. You choose what waits for a person at every level. By default that is changes to sign-in and security code, infrastructure changes and rollbacks; Bugstack never rotates a secret itself. Every action is logged, and undo opens a revert pull request.