> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/elements-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/elements-docs/hosting/elements-hosting-reactor-panel/packages/hosting-packages.md).

# Hosting Packages

View your Elements Hosting packages for all of your hosted websites

<figure><img src="https://410055788-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1wrnfhRFfBQTaZF2M5d8%2Fuploads%2FI5FShwyNyJOtzM1h9yyt%2F01-hosting-packages.webp?alt=media&amp;token=a715c261-2d11-4b85-a994-b379c0d03861" alt=""><figcaption></figcaption></figure>

Your hosting package defines the resources and features available to your website(s) on Elements Hosting. It determines things like how much storage, bandwidth, and other resources your site has access to. If you host multiple websites or have different needs, you can be subscribed to more than one hosting package at the same time.

Elements Hosting supports common package types, including shared and dedicated hosting. This makes it easy to match the right resources to each website while keeping everything organized and easy to manage in one place.


---

# 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.realmacsoftware.com/elements-docs/hosting/elements-hosting-reactor-panel/packages/hosting-packages.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.