Skip to main content

How to Launch a Velocity Application on Cloudways

Learn how to launch a Velocity application on Cloudways, choose a plan, import a GitHub repository, review build settings, and deploy your app.

Written by Syed Abuzar Mehdi

Velocity is a JavaScript runtime used to build fast and scalable web applications, APIs, and backend services.

With Cloudways, the server setup and deployment process is simplified, so you can focus on building and running your application instead of managing the hosting environment manually.

Note:

Cloudways Node.js is now called Cloudways Velocity. This is a product name change only. You can continue using Cloudways Velocity to launch, deploy, and manage your Node.js applications. References to Node.js in this article describe the application runtime and deployment process available through Cloudways Velocity.


How to Launch a Velocity Application on Cloudways

Cloudways Velocity lets you launch, deploy, and manage Velocity applications from the Cloudways Platform.

You can connect your GitHub account, import your application repository, choose your preferred plan, review the build settings, and deploy the app with a few simple steps.

Step #1 - Go to Velocity from the Cloudways Platform:

  • Log in your Cloudways Platform, and from the home screen, select Velocity from the left-side menu and click on Get Started.

  • You can also click Try Now from the Velocity card if it appears on your dashboard.

  • This will start the Velocity application launch process.

  • If you already have an app on Velocity, you can add another Velocity app as shown below.

  • The process will be same. Click on side bar menu first so the below mentioned screen appears.

Step #2 - Choose Your Velocity Plan:

On the Choose Your Plan screen, select the plan that fits your application needs.

Each plan shows the following details:

  • Monthly price — the cost of the selected plan.

  • vCPUs — the virtual CPU power assigned to your application.

  • RAM — the memory available for your application.

  • Disk Size — the storage space available for your files and application data.

  • Network — the maximum network speed supported by the plan.

You will also see included features such as:

  • Enterprise CDN — helps deliver content faster to visitors.

  • DDoS Protection — helps protect your application from large traffic-based attacks.

  • Malware Protection — helps scan and protect your application from malicious files or threats.

You will also need to Chose Disk Space.

After selecting your preferred plan, click Proceed.

Step #3 — Select a Git Provider

On the Select Repository screen, select the version-control provider where your application code is stored.

Cloudways Velocity currently provides the following options:

  • GitHub

  • GitLab

  • Bitbucket

A Git provider is a service that stores and manages your application’s code repositories.

Select your preferred provider. For example, to import a repository from GitHub, select GitHub, and then click Connect.

Step #4 — Sign In to Your GitHub Account

  • A GitHub sign-in window opens after you click Connect.

  • Enter your GitHub username or email address and password, and then click Sign in. You may also use another sign-in method supported by GitHub.

  • This step allows Cloudways Velocity to request permission to access the repositories you want to deploy.

Note:

If you select GitLab or Bitbucket, you will be redirected to the corresponding provider’s authentication page instead.

Step #5 — Authorize Cloudways Deploy

After signing in, GitHub asks you to install and authorize the Cloudways Deploy application.

Select one of the following repository-access options:

  • All repositories: Allows Cloudways Deploy to access all current and future repositories associated with the selected GitHub account.

  • Only select repositories: Allows you to choose specific repositories that Cloudways Deploy can access.

For greater control, select Only select repositories and grant access only to the repository you intend to deploy.

Review the requested permissions, and then click Install & Authorize.

After authorization, GitHub redirects you to the Cloudways Platform.

Step #6 — Select the Repository

After your Git provider is connected, return to the Select Repository screen.

  1. Confirm that the correct Git provider and connected account are selected.

  2. Select the required Workspace, if applicable.

  3. Locate the repository containing your Velocity application.

  4. Use the search option if you have several repositories.

  5. Select the repository you want to deploy.

  6. Click Continue.

A repository is the storage location that contains your application code, configuration files, and version history.

If the required repository does not appear, refresh the repository list and verify that Cloudways Deploy has permission to access it.

Step #4 - Review Build Settings:

On the Review build settings screen, review the application setup before deployment.

You will see the selected GitHub repository and the available deployment options.

Review or update the following settings:

  • Framework Preset
    Select the framework used by your application, such as React. A framework is a set of tools used to build your application.

  • Branch
    Select the Git branch you want to deploy. A branch is a version of your code inside your GitHub repository.

  • Node (Now Velocity) Version
    Select the Velocity version required by your application, such as Node 22 LTS. LTS means Long-Term Support, which is a stable version recommended for most users.

  • Root Directory
    Confirm the folder where your application code is located. If your application is in the main repository folder, the root directory may appear as /.

Note:

Cloudways does not automatically fetch or select the framework preset from your repository. You need to manually choose the correct framework preset, such as React, based on how your Velocity application is built. Selecting the correct framework helps Cloudways apply the right build and output settings during deployment.

Step #5 - Review Build and Output Settings:

  • In the Build and output settings section, Cloudways shows the default build settings based on your selected framework.

  • These settings define how your application will be built before it goes live.

  • Click Change if you need to update the build command or output folder based on your application requirements.

  • For many users, the default settings will work if the framework and repository are correctly detected.

Step #6 - Add Environment Variables, If Needed:

  • In the Environment variables section, click Add if your application needs environment variables.

  • Environment variables are values your application uses without storing them directly in the code. For example, these can include API keys, database details, or app configuration values.

  • If your application does not need any environment variables, you can leave this section unchanged.

Step #7 - Add Environment Variables from the Modal:

After clicking Add, the Set environment variables modal appears. Use this modal to add the values your application needs during the build process.

In this modal, you can:

  • Enter the Key and Value for the environment variable. The Key is the variable name, and the Value is the information your application will use.

  • Turn on the Sensitive toggle if the value is private, such as an API key, password, secret token, or database password. When a variable is marked as sensitive, its value is hidden after saving and cannot be viewed again. You can still remove the variable later if needed.

  • Click Add more to add multiple environment variables from the same modal.

  • Click Import .env if you already have an .env file. An .env file is a simple file that stores environment variables for your application.

  • Use Remove to delete an environment variable row from the modal.

  • Click Save after adding the required variables.

Important:

Sensitive values are hidden after saving. Make sure you enter the correct value before saving because you will not be able to view it again later.

Step #8 - Add a Custom Domain, If Needed:

  • In the Temporary domain section, Cloudways provides a temporary domain for your Velocity application.

  • You can use this temporary domain to access and test your application after deployment.

  • Click Add Custom Domain if you want to connect your own domain, such as example.com.

  • After you add the custom domain, Cloudways will ask you to point your domain to the Cloudways Cloudflare zone. This is done by updating your domain’s DNS records.

  • DNS records are settings that tell the internet where your domain should open from. You may need to add one of the following records:

    • A record — points your domain to an IP address.

    • CNAME record — points your domain to another domain name.

  • Follow the DNS instructions shown on the Cloudways Platform and update the records from your domain registrar or DNS provider.

  • You can also skip this step during deployment and add a custom domain later from the application overview page.

Note:

Your custom domain will not start working immediately after adding it to Cloudways. You must also update the required DNS records, such as the A record or CNAME record, so the domain points to the correct Cloudways Cloudflare zone.

Step #9 - Select Server Location:

  • In the Location section, choose the server location where your Velocity application will be hosted.

  • Choose a location close to most of your website visitors. This can help reduce loading time and improve the user experience.

  • For example, if most of your visitors are in the United States, you may choose a US-based location such as New York.

Deploy the Velocity Application

  • After reviewing all settings, click Deploy Now.

  • Cloudways will start setting up your Velocity server and building your application.


Step #10 - Wait for Deployment to Complete:

On the deployment screen, you can view the deployment progress.

Cloudways will show the selected deployment settings if you click the dropdown, such as:

  • Velocity version

  • Root directory

  • Build and output settings

  • GitHub author

  • Branch

  • Framework

  • Commit ID

The deployment process may take a few minutes.

You will see progress stages such as:

  • Setting up your Velocity Server

  • Building your application

Keep the tab open while Cloudways completes the setup. Once the process is complete, your Velocity application will be ready to use.

Your Velocity application is now deployed on Cloudways. You can use the temporary domain to test your application or connect a custom domain when you are ready to make it live.

Velocity Applications Page

After your Velocity app is launched, you can view it from the Velocity Web App page.

From this page, you can:

  • View all your Velocity applications in one place.

  • Check the application name, plan, server location, and creation date.

  • Use Sort by to arrange applications by date created.

  • Click Add Velocity App to launch another Velocity application.

  • Click the three-dot menu next to an application to manage it.

The three-dot menu gives you the following options:

  • Stop — temporarily stop the selected Velocity application.

  • Restart — restart the application if you need to refresh its services.

  • Delete — permanently remove the application from your Cloudways account.

Note:

Only delete an application if you are sure you no longer need it, as this action may remove the app and its related data.


That’s it! We hope this article was useful.

Did this answer your question?