# Managed server

The platform provisions, sets up, and operates a managed server itself and bills it through your subscription, so you do not need an account with a cloud provider.

> Source: https://www.application-platform.com/en/docs/managed-server/

With a managed server, the platform takes over provisioning. The server runs on our infrastructure, we set it up and operate it, and the costs appear as a separate item on your bill. You need neither a server of your own nor an account with Hetzner or Hostinger. This option fits when you do not want to look after the server or manage an additional provider.

## Creating the server

1. Open **Servers** in the sidebar, click **Add server**, and choose **Managed server**.
2. Set a **name** and a **server ID**. The server ID is a slug, a short identifier without spaces or special characters.
3. Choose the **tier** that matches your needs. S, M, and XL are available.
4. Confirm the **billing consent**. The managed server is billed as an additional monthly item via Stripe on top of your subscription; the terms are on the [pricing page]({{< relref "/pricing" >}}).
5. Confirm. The platform sets up the server and sends you the **root password** by email.

The server is then available when creating or editing projects. Deployments run through the pipeline as with all other server types, as described under [Git workflow and deployment]({{< relref "git-workflow" >}}).

## Switching or combining later

The server types can be mixed, because the assignment happens per project. You can start with a managed server and later move individual projects to your own [cloud servers]({{< relref "cloud-servers" >}}) or to a [server of your own]({{< relref "own-server" >}}) by selecting a different server when editing the project.

