> 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/getting-started/create-a-new-database-in-bugsplat.md).
# Creating a Database
In BugSplat, a database is the top-level container for crashes and can be considered a standalone workspace for your application. Generally, a database holds all crashes and errors from a single application or logical group of applications, such as a client and server. To learn more about the hierarchy of BugSplat information, please view this [document](/guides/using-the-app.md#navigating-with-breadcrumbs).
To start using BugSplat, you'll need to create a database. You can create a database through one of two methods: via the [Onboarding Tool](https://app.bugsplat.com/v2/welcome) or the [Databases page](https://app.bugsplat.com/v2/database/general).
### Create a Database via the Onboarding Tool 🧑🏫
For new BugSplat users, creating a new database can be accomplished via the Onboarding Tool. After creating a new account, users will be prompted to create a database. You can return to it any time by navigating to the [Onboarding Tool](https://app.bugsplat.com/v2/welcome).
Create a Database via the Onboarding Tool
### Create a Database via the Database Page ⚙️
Alternatively, a database can be created on the [Databases](https://app.bugsplat.com/v2/database/general) page. At the top of the page, enter your new database's name under the **New Database** section and click **Create**. The Database's page is helpful when setting up multiple databases under an account.
Create a Database via the Databases Page
### Naming your Database 🪪
Pick something descriptive and easy to remember when choosing a database name. Please note that spaces, periods, and symbols other than `-` are prohibited. Some examples of database names are: `DeliciousDonutsApp` or `Super-Strong-Coffee-App`.
---
# 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/getting-started/create-a-new-database-in-bugsplat.md?ask=&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.
