> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bugspray.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Choose how to run Bugspray

> Start locally, then select an operator-owned deployment path.

| Mode | Runtime and storage | When to choose it |
| - | - | - |
| Local workstation | Node, SQLite, filesystem artifacts/profiles | First use, authoring and trusted local QA |
| Self-hosted Node | Node behind your HTTPS proxy, private persistent data | An operator-managed server with explicit authentication and backups |
| Cloudflare tenant | Worker, D1, private R2, Queue, Container runner and Access | An operator building a hosted tenant architecture with a separate broker |

[Local startup](https://docs.bugspray.io/quickstart.md) creates no cloud resources. A hosted tenant, provider connection or paid runner is not required for ordinary local use. No maintained release series or support SLA is currently announced; identify deployments by exact source/image digests.

## Local and hosted capabilities differ

The local stdio bridge supports visible-browser sign-in. Hosted deployments expose Settings-generated OAuth, tenant-bound service tokens and authenticated browser discovery when configured. Do not assume every tool available on one deployment is available on another. Discover the live MCP schemas and inspect Settings.

Local repros run processes on your host; hosted repros run Containers. Both execute trusted code and require deliberate enablement. Review [findings and replay](https://docs.bugspray.io/guides/findings-and-replay.md) before accepting script submissions.

## Pick your operating guide

> [card] [Self-host Node](https://docs.bugspray.io/self-hosting/node.md)
>
> Configure production origin, credentials, persistent storage and a proxy.

> [card] [Cloudflare architecture](https://docs.bugspray.io/self-hosting/cloudflare.md)
>
> Understand private manifests, tenant boundaries and reviewed release tooling.

> [card] [Upgrade and recover](https://docs.bugspray.io/self-hosting/upgrades.md)
>
> Preserve data, artifacts and keys; rehearse recovery before rollout.

> [card] [Configuration](https://docs.bugspray.io/reference/configuration.md)
>
> Use the actual runtime variables and distinguish clients from servers.

## Current container limitation

The root Dockerfile installs before copying required vendored dependency archives. The Compose path needs that packaging correction and actual image validation before use. A Worker bundle check does not prove the Container runner builds or works. This docs change does not alter packaging or claim container readiness.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.