Integrations
GitHub is the one connection bugstack needs. The rest are optional. Each one widens what bugstack can watch or where it can reach you.
GitHub (required)
bugstack reads your code from GitHub and delivers every change as a pull request. Once a repository is connected:
- Repository scanning starts: vulnerable packages every four hours, secrets nightly, outdated packages daily
- When your app crashes or a deploy fails, bugstack reads the files involved and works out the cause
- A fix is written on a new branch, with a pull request that describes the problem and the change
- What happens next depends on the autonomy level you set for that repository
You set the autonomy level per repository from the dashboard. Choose between Suggest, Review and Autopilot. New repositories start on Review.
For dependency and security findings, bugstack scans and reports. It can open upgrade pull requests for npm packages too, which is switched on per account.
Hosts and services
These connectors are optional and available today:
Render
Failed deploys. When a deploy fails on Render, bugstack starts work on the cause.
Uptime checks
bugstack checks that your app is up.
Neon
Flags Postgres compute that never suspends.
Render is the only host supported for failed deploys today. Deploys on hosts that are not connected are not seen.
Your CI
There is nothing to install for CI. When bugstack opens a pull request, your existing checks run against it as they would for any other pull request. And when CI fails on your default branch, bugstack starts work on the cause. This works with:
GitHub Actions
Pull requests trigger your existing workflows.
CircleCI
bugstack pull requests trigger your CircleCI runs through GitHub.
Any CI Provider
Jenkins, Travis CI, Buildkite, and more. If it reports status checks on GitHub pull requests, it works.
bugstack reads the check status of each pull request. Every fix bugstack opens is already proven in its sandbox: a test that reproduces the bug fails on your current code and passes with the fix, with the rest of your suite green. Your CI runs on the pull request as a second check. On Autopilot, a merge needs green CI and that proof, checked again at merge; without it the pull request waits for you.
Alerts where you work
bugstack sends notifications through these channels:
Notifications by email.
Slack
Connected with an incoming webhook.
Microsoft Teams
Notifications in Microsoft Teams.
PagerDuty
Notifications through PagerDuty.
In-app
Shown in the bugstack dashboard.
Planned
These connectors are planned. None of them is available today:
- Code hosts (planned): GitLab, Bitbucket, Azure DevOps
- Infrastructure (planned): Terraform Cloud, Kubernetes, AWS
Your telemetry. bugstack is built to take problems from whatever telemetry 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. Tell us what you use.
Framework Support
bugstack SDKs have built-in support for these frameworks: