> For the complete documentation index, see [llms.txt](https://docs.bugsplat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugsplat.com/about/introduction.md).

# Why BugSplat?

Here's a list of the top reasons our users choose BugSplat. If you agree, consider signing up [here](https://app.bugsplat.com/v2/sign-up).

1. BugSplat provides our users with world-class crash reporting on [cross-platform](/integrations/desktop.md), [desktop](/integrations/desktop.md), [web](/integrations/web.md), [gaming](/integrations/game-development.md), and [mobile](/integrations/mobile.md) platforms.
2. Integrating BugSplat with your application is a well documented process, you can learn more about it [here](/getting-started/getting-started.md). Our team provides responsive, friendly support along the way, making getting up and running a straightforward process.
3. BugSplat has years of experience (15+ years to be more precise) providing crash reporting in a wide variety of applications: from hustling, individual developers to Fortune 500s with millions of users.
4. We prioritize and build the features our users care about. With a no-nonsense, fast, easy-to-navigate UI and as well as powerful search features, we go above and beyond to build the features you ask for.
   1. Note: we take product feedback seriously. Our team reviews any feedback we receive via our [Feedback](/education/how-tos/sending-feedback.md) tool. We respond to all submitted feedback directly.
5. On average, users stay with BugSplat for 5+ years after first integrating their app with our crash reporting service.
6. There is nothing complicated with our fair and straightforward pricing: no big, scary, complex tables that leave you wondering what you're actually getting with a plan. By making our pricing simple, we've found a lot of ways to pass along savings to our users.
7. BugSplat is a [bootstrapped company](/about/who-is-bugsplat.md) that answers only to our users.
8. Every new account signing up for BugSplat helps us [plant more trees](/about/who-is-bugsplat/charitable-giving.md#one-tree-planted) to fight deforestation and the climate crisis through our partner, One Tree Planted.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bugsplat.com/about/introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.