--- title: "Deploy an App" description: "Launch a pre-configured app on a VM in one click, capture its one-time credentials, and know what setup some apps still need afterwards." category: "Deployment" language: en source: https://cubepath.com/docs/products/deployment/deploy-an-app updated: 2026-11-17 --- # Deploy an App Launch a pre-configured **App** in one click from the **1-Click Apps** page in [my.cubepath.com](https://my.cubepath.com). Each App runs on a Virtual Machine, with the region and plan pre-filled for you. > Note: Your account must be [verified](/docs/products/overview/account-setup) before you can deploy. ## Deploy ```steps ### Choose an app Pick an App from the carousel, or use the search box to find one by name. ![One-click app catalog with search](https://cdn.cubepath.com/img/docs/products/dabc3f30-2a63-4218-a0f4-a27129f663fa.png) ### Confirm region and plan A nearby **location** is selected for you by latency; to pick a different one, use **Advanced Mode**. A recommended **plan** is preselected, and you can choose another. ### Configure settings Fill in any **environment variables** the App asks for in the **Configuration** section. Auto-generated values are created for you, so they don't appear there. ### Deploy Copy the auto-generated **root password** (it's for SSH access as root and can't be edited), then click **Deploy** to launch the App. ### Get your access details After deploy, a window shows the **credentials** or **secret key** to sign in. The **access URL** appears on the VPS details page once the server is active. ``` > Warning: Auto-generated passwords and secret keys are shown **only once**, right after deploy. Copy them into a password manager before closing the window. Some cannot be recovered afterwards, only reset from inside the application. The App runs on a VM, so you manage it like any [Virtual Machine](/docs/products/deployment/deploy-a-virtual-machine): [backups](/docs/products/deployment/vps-backups), [firewall](/docs/products/deployment/vps-firewall), [metrics](/docs/products/deployment/vps-metrics) and [resize](/docs/products/deployment/vps-resize) all work exactly as normal. > Note: An App declares a **minimum RAM**, and plans below it can't be selected when you deploy. If you later [reinstall](/docs/products/deployment/vps-reinstall) an existing VPS with an App and its plan is below that minimum, the reinstall page warns you: resize first, or the App may install but behave badly. ## After deploy A few things are worth doing on the first day, because a one-click deploy skips them by design: - **Point a domain at it.** Add an A record in [DNS records](/docs/products/deployment/dns-records) for the machine's IP rather than sharing a raw address. - **Lock down the ports.** The App only needs its own ports plus SSH. Attach a [firewall group](/docs/products/deployment/firewall-groups) and close everything else. - **Turn on backups.** Applications accumulate data from the moment they start. [Automatic daily backups](/docs/products/deployment/vps-backups) cost 20% of the plan. ## Apps that need their own credentials Some Apps are a front end for a service you pay for separately (an AI assistant that talks to a model provider, for example). Those arrive with the server ready but not yet connected, and the pattern is always the same: ```steps ### Open the app from your welcome email Some apps email you an access link that already contains a **token**. Treat that link like a password: anyone holding it has full access. ### Create a key with the third-party provider Sign up there, create an API key, and copy it. ### Paste it into the app's settings The key lives in the application, not in CubePath. ``` That split matters for cost: **the server is what you pay CubePath for; the third-party usage is billed to you directly by that provider**. Set a spending limit in the provider's console on day one, and prefer their cheaper tier for routine work. That's the difference between a predictable bill and a surprising one. > Warning: Never share the access token from a welcome-email link, and never share a third-party API key. The first grants full access to your app; anything done with the second is charged to you.