Launch a pre-configured App in one click from the Deploy App page in my.cubepath.com. Each App runs on a Virtual Machine, with the region and plan pre-filled for you.
NoteYour account must be verified before you can deploy.
Deploy
- 1Choose an appPick an App from the carousel, or use the search box to find one by name.
- 2Configure settingsFill in any environment variables the App needs; values marked as auto-generated are created for you.
- 3Confirm region and planA nearby region is auto-selected by latency, and a recommended plan is preselected. Adjust either if you like.
- 4DeployReview the read-only root password, then click Deploy to launch the App.
- 5Get your access detailsAfter deploy, a window shows the access URL plus the credentials or secret key to sign in.
WarningAuto-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 the access URL appears on the VPS details page once the server is active. Manage it like any Virtual Machine: backups, firewall, metrics and resize all work exactly as normal.
NoteAn App declares a minimum RAM. If you pick a plan below it, the app may install but behave badly. The reinstall page warns you about this explicitly — believe it, and resize first.
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 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 and close everything else.
- Turn on backups. Applications accumulate data from the moment they start. Automatic daily 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:
- 1Open the app from your welcome emailSome apps email you an access link that already contains a token. Treat that link like a password — anyone holding it has full access.
- 2Create a key with the third-party providerSign up there, create an API key, and copy it.
- 3Paste it into the app's settingsThe 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 — it's the difference between a predictable bill and a surprising one.
WarningNever 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; the second gets charged to you.