> For the complete documentation index, see [llms.txt](https://bothosting-net.gitbook.io/bot-hosting.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bothosting-net.gitbook.io/bot-hosting.net/guides/the-new-panel.md).

# The new Panel

Learn what changed in the new panel and how to move your server.

The new panel replaces the legacy experience with a single workspace.

{% hint style="warning" %}
The legacy and new panels are separate. They do not share servers, subscriptions, or files.
{% endhint %}

### What's new

The new panel includes:

* Credits replace the legacy coin system for site payments and renewals.
* One account and workspace manage projects, deployments, and databases.
* A custom Developer API and OAuth support external applications. Users can authorize apps to manage their deployments and account, or create their own application.
* Templates let users publish deployable configurations for other platform members. Members can install a template on their server with minimal setup.
* More deployment types are available, including databases, services, static sites, and PHP deployments.
* Backups remain on the platform after a server is deleted.
* Environment variables, ports, packages, and connection details are easier to manage.
* Card and crypto payments are available on the website. PayPal payments are no longer available.

### Free and premium capacity

Free and premium servers now use repartitioned node capacity. Each node reserves a defined amount of space for free servers. Another portion is reserved for premium servers.

Each user can create one free server. Free-server capacity has been reduced because of inflation.

We kept prices unchanged for four years. Every free server now costs us money to provide. This separation helps us keep the service sustainable.

### Move to the new panel

{% hint style="info" %}
There is no migration portal currently. Move your files manually to a new server.
{% endhint %}

The legacy panel will shut down soon. We cannot maintain it anymore.

There is no estimated shutdown date yet. Updates will be posted here and on Discord.

If you have an active legacy subscription or server, wait for its subscription to expire. Deleting it does not provide a refund. Legacy servers cannot transfer directly to the new panel.

1. Download and archive your legacy server files. Keep a copy in Git or cloud storage.
2. [Create an account](/bot-hosting.net/guides/create-an-account.md) in the new panel.
3. [Create a server](/bot-hosting.net/guides/create-a-server.md), upload your files, and [set it up](/bot-hosting.net/guides/set-up-a-server.md).

### Legacy coin conversion

Only coins purchased in the legacy panel can be converted to credits in the new panel. Coins earned or received through other legacy methods are not eligible.

Manual coin-to-credit conversion requests are unavailable. Eligible coins will convert automatically when we move the panel.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://bothosting-net.gitbook.io/bot-hosting.net/guides/the-new-panel.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.