How It Works
Keeping software running takes constant work: crashes, failed deploys, vulnerable packages, leaked secrets, packages that fall out of date. Bugstack takes that upkeep on in three steps:
- Watch. Your app reports crashes through a two-line SDK. Your host reports failed deploys. Bugstack reads your repository on a schedule for vulnerable packages, secrets and outdated packages.
- Fix. Specialist agents work each problem. One diagnoses and patches, one reproduces the failure in an isolated sandbox, and others handle security, dependencies and infrastructure. The fixes are written by Anthropic’s Claude and stay small enough to review.
- Prove. Every change is a pull request, and your CI runs on it. Before you see a bug fix, Bugstack proves it in an isolated sandbox: a test that reproduces the bug fails on your current code, then passes with the fix while the rest of your suite stays green. You choose how much Bugstack does without asking. Every action is logged, and undo opens a revert pull request.
See the full breakdown of how Bugstack works →
See Bugstack vs Dependabot and Renovate →
What Bugstack maintains
Bugstack watches three places: your running app, your host, and your repository.
- Crashes. Uncaught server-side errors, captured by the SDK.
- Failed deploys. On hosts you have connected. Render is the host supported today.
- Vulnerable packages. Checked every four hours.
- Leaked secrets. Checked every night.
- Outdated packages. Checked every day.
Bugstack scans and reports on packages and secrets, and it can open pull requests for those findings. That part is switched on per account.
What Bugstack does not watch
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 does not throw. A job that quietly stops. A page that gets slower.
- Errors in your users’ browsers. The SDK captures server-side errors.
- Deploys on hosts that are not connected. Render is the only host Bugstack hears from today.
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.
Getting Started
Setup takes a few minutes:
- Connect GitHub. Sign in with GitHub, start the 14-day trial with a card, and pick the repositories you want maintained.
- Install the SDK. Add the Bugstack SDK to your application (available for JavaScript, Python, Ruby, and Go).
- Deploy. Push your updated code to production. Bugstack starts catching crashes once the SDK is live.
- Connect your host. Optional. Connect Render so Bugstack hears about failed deploys.
Frequently Asked Questions
Do I need Sentry or Datadog to use Bugstack?
No. You do not need a monitoring vendor. Bugstack captures crashes through its own SDK, hears about failed deploys from your host, and reads your repository directly. If you already have a monitoring tool, keep it. Bugstack does not replace dashboards, tracing or performance monitoring.
Is it safe to let Bugstack push code to my repository?
Every change Bugstack makes 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, so you do the merging. On Autopilot, a bug fix merges only when CI is green and the sandbox has proven it: a test that failed before the fix and passes after, with the rest of the 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 decision is logged, and undo opens a revert pull request.
What languages and frameworks does Bugstack support?
Bugstack has SDKs for JavaScript/TypeScript (Express, Next.js), Python (Flask, FastAPI, Django), Ruby (Rails, Sinatra, Rack), and Go (net/http, Gin, Echo, Fiber).