> ## Documentation Index
> Fetch the complete documentation index at: https://help.onetsolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploy an application

> Choose an application in the catalogue and put it online on your VPS

Once the platform is installed, deploying an application takes a few minutes and no command line.

<Info>
  **Prerequisites**

  * The One Click Apps platform installed and in the **Ready** state
  * Enough free RAM on the instance
</Info>

## Choose an application

<Steps>
  <Step title="Open the catalogue">
    In your instance, go to **One Click Apps** then select **Deploy an application**.
  </Step>

  <Step title="Find the application">
    Filter by category or search by name. Featured applications are shown first.
  </Step>

  <Step title="Open the deployment form">
    Select **Deploy** on the application card.
  </Step>
</Steps>

## Fill in the form

| Field         | What it does                                                                                                                                     |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| Name          | The unique identifier of the application on this instance. Lowercase letters, digits and hyphens. A name is suggested from the application name. |
| Parameters    | The settings the application exposes, such as a site title or an administrator address. Defaults are prefilled.                                  |
| Custom domain | Optional. Your own domain name, applied at deployment. See [Custom domain](/one-click-apps/custom-domain).                                       |

Select **Deploy** to start. The task runs in the background: you can leave the page and follow it from the instance tasks.

## After deployment

The application appears in the One Click Apps list with a **Running** status. Open it to reach:

* The generated HTTPS address, ready to use
* The credentials generated at deployment, in the **Overview** tab
* The logs, environment variables, domains, backups and history tabs

<Warning>
  The credentials shown in the console are generated once, at deployment. Store them in a password manager: changing them inside the application does not update the console.
</Warning>

## If a deployment fails

A failed deployment keeps its card in the list with a **Failed** status and a link to the task and its logs. Read the task logs first: a deployment usually fails because the image could not be pulled or because the application did not become healthy in time.

Select **Retry** on the card to start over. The previous attempt is removed from the platform before the new one starts.