> 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/administration/billing/free-plans-from-bugsplat/standard-free-plan.md).

# Free Plan Overview

BugSplat wants to help all hackers, those getting started, and do-it-yourselfers to have access to world-class crash reporting. Because of that, we provide a Free Plan that covers 3 users, one user group, up to 15,000 monthly errors and crashes and a suite of key features to help your project succeed.

#### How long does the free plan last?

The Free plan is free forever. Consider upgrading to a paid plan if you need more users, crashes, storage space, or additional features.

#### Are there other free plans?

Yup! If you're an [indie game dev](/administration/billing/free-plans-from-bugsplat/free-accounts-for-indie-game-development.md), [working in education](/administration/billing/free-plans-from-bugsplat/bugsplat-free-accounts-for-students-and-teachers.md), supporting a not-for-profit [open source project](/administration/billing/free-plans-from-bugsplat/bugsplat-free-accounts-for-not-for-profit-open-source-projects.md), or working on a [good cause](/administration/billing/free-plans-from-bugsplat/good-causes.md), we've got some free plans for you to check out.

### How to get started

To get started with the Standard Free Plan, follow the below steps:

1. Sign up for an account [here](https://app.bugsplat.com/v2/sign-up).
2. Follow the [Getting Started](/getting-started/getting-started.md) docs to set up your account.
3. Use BugSplat normally and stay within the plan's guidelines (3 users, 1 User Group, and less than 15,000 monthly errors and crashes). Will have the chance to select the Free plan at the end of the [Free Trial](/administration/billing/free-trial.md).


---

# 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/administration/billing/free-plans-from-bugsplat/standard-free-plan.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.