# Frequently Asked Questions

Common questions about what Bugstack maintains and how you stay in control

What does Bugstack maintain?

Bugstack watches three things:

-   **Your running app**: a two-line SDK captures uncaught server-side errors.
-   **Your host**: failed deploys on connected hosts. Render is the host supported today.
-   **Your repository**: scans for known-vulnerable packages every four hours, secrets nightly, and outdated packages daily.

When your app crashes or a deploy fails, Bugstack finds the cause, writes the fix, and opens a pull request. It scans and reports dependency and security findings, and can open pull requests for them. Those pull requests are switched on per account.

Can Bugstack fix a bug a customer reported?

Yes. A report written in plain words, from Zendesk, Intercom, Freshdesk, a support inbox, a GitHub issue or the dashboard, goes to Bugstack’s Tester. It writes a test that fails for the reason the customer described, the fix has to make that test pass, and the customer hears back once the fix is live. [Customer bug reports](/customer-bug-reports)

What doesn't Bugstack watch?

Bugstack does not watch wrong answers returned as a success. It does not watch anything that does not throw, such as a job that quietly stops or a page that gets slower. It does not capture errors in your users' browsers. It does not see deploys on hosts that are not connected.

Is Bugstack finished?

No. Bugstack is under active construction. Crash fixes, failed-deploy fixes on Render, fixes for a failing CI run on your default branch, and repository scanning for vulnerable packages, secrets and outdated packages are live today. Performance regressions, failures that do not throw, browser errors, more hosts and repositories outside GitHub are not covered yet. That is the edge today.

Will Bugstack merge changes without asking me?

Only if you choose that. Each repository has one of three autonomy levels: Suggest, Review and Autopilot. New repositories start on Review, where Bugstack opens pull requests and you merge them. On Autopilot, a bug fix merges only with green CI and sandbox proof: 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.

How does Bugstack prove a fix works?

In an isolated sandbox. Bugstack copies your repository into a sandbox, installs your dependencies and cuts the network. The tester writes a test that reproduces the bug, and it has to fail on your current code for the bug’s own reason; a test that fails for anything else, a typo or a bad import, never counts. Then the fixer makes the change in the same sandbox: the test has to pass and every other test has to stay green. Only then does a pull request open, carrying the proof and the test. Before Autopilot merges it, Bugstack runs the proof again. The sandbox gets none of your secrets and is destroyed when the fix is done.

Do I need Sentry or Datadog to use Bugstack?

No. Bugstack captures crashes with its own SDK, so it works without a monitoring vendor. If you already have monitoring, keep it. Bugstack does not replace dashboards or tracing.

What languages and frameworks do you support?

We have SDKs for:

-   **JavaScript**: Express, Next.js
-   **Python**: Flask, FastAPI, Django
-   **Ruby**: Rails, Sinatra and Rack
-   **Go**: net/http, Gin, Echo and Fiber

Each SDK collects error details, request context, and environment info, then sends it to Bugstack for processing. The sandbox that proves each fix runs Python, JavaScript and TypeScript, and Go test suites. Ruby repositories, and test suites that need a database or other services, are not run in the sandbox yet; their fixes open for your review. Want another language? [Let us know](mailto:support@bugstack.ai).

Do you have access to my code?

Yes. Bugstack reads the connected repository to scan it and to write fixes. It accesses the repository through GitHub, with the permissions you grant. To prove a fix, it copies the repository into an isolated sandbox for the length of that fix, then destroys it. It keeps a map of your file paths, a package inventory, each finding with its location, and each change it proposes. It does not keep a copy of your codebase. Every change arrives as a pull request, so you can see what changed and why.

Can I review fixes before they're merged?

Yes. Every fix is delivered as a GitHub pull request. You set one of three autonomy levels for each repository: Suggest, Review or Autopilot. New repositories start on Review, where every pull request waits for you to merge it.

What if the AI fix is wrong?

Several things keep a wrong fix from doing damage. Your CI runs against every pull request. New repositories start on Review, so nothing merges until you merge it. On Autopilot, a bug fix merges only with green CI and sandbox proof: a test that failed before the fix and passes after, with the rest of the suite green. If a merged change turns out to be wrong, undo opens a revert pull request. Every decision is recorded on a tamper-evident audit log.

How long does it take to fix a bug?

A pull request typically arrives in minutes. How long CI takes depends on your test suite. On Review, the fix ships when you merge it.

Can I use this in production?

Yes. The SDK captures errors asynchronously and never blocks your API responses. Errors are rate-limited and deduplicated before Bugstack starts a fix. Fixes run through your own CI before anything is merged. You choose the autonomy level for each repository.

Does Bugstack support on-prem or self-hosted deployments?

Not at this time. Bugstack is a cloud-hosted service. If you have on-premise or self-hosted deployment requirements, [contact us](/contact) to discuss your needs.

What happens if Bugstack is down or experiencing an outage?

Your app is never affected. The SDK is non-blocking: it queues the error and returns immediately. If Bugstack's endpoint is unreachable, the JavaScript SDK retries up to 5 times with exponential backoff (1s, 2s, 4s, 8s, 16s), and the Python, Ruby and Go SDKs retry 3 times. After that, the error is dropped. The retry queue is in memory only, so if your process restarts during an outage, queued errors are lost. Your users never notice.

What does a fix cost?

It depends on the fix, so we do not quote a figure. Work draws on your credit as Bugstack does it, a small fix uses less than one that takes several attempts, and your billing page shows what each piece of work used. We [deduplicate](/features) errors by fingerprint within a 24-hour window, so repeats of an error already being fixed don't start a second fix.

How does pricing work?

There is one plan. Bugstack Pro is $100 a month and includes $100 of usage credit every month. A new workspace starts with a 14-day trial: $50 of credit, plus a first security audit on us, up to $50 more of credit. Repositories are unlimited. Work draws on credit, and you can add more from $10 whenever you need it. A card is required to start the trial, and nothing is charged until Pro starts. [See pricing](/pricing).

Can I cancel anytime?

Yes. Cancel from your dashboard settings. There are no cancellation fees, and if you cancel mid-cycle you keep access until your current period ends.

[See how Bugstack works →](/docs/how-it-works)

## See it work on your own code.

$100 a month

Includes $100 of usage credit every month. Start with a 14-day trial: $50 of credit and a first security audit on us. A card is required.

[Get started](https://dashboard.bugstack.ai/login) [Book 15 minutes with the founder](https://cal.com/mason-bachmann-1atgdq/15min)