Skip to content

Applications

Deploy and operate verified Node.js, Next.js, and Python applications.

1Overview

Applications manages process-backed hosting workloads. Each application is tied to one registered domain, an account-owned application root, a runtime, an entry point, and a managed service.

Applications in the administrator panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.
Administrator Applications page showing managed applications and deploy, start, stop, restart, dependency, and log controls.

Applications in the administrator panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.

2Before you begin

Administrator actions can affect multiple customer accounts and server services.

Keep the project source, dependency file, environment values, and a rollback revision available before deployment.

3Step-by-step workflow

Select Applications, create or open an app, choose the existing domain and runtime, set the validated start configuration, install dependencies, build when needed, then deploy. Use status and logs to confirm the health check.

  1. Open Applications and identify the account and registered domain that should serve the project.
  2. Choose Create application and select the application type supported by the panel.
  3. Set an application root inside the owning account and supply the project source in that folder.
  4. Enter the start file or command and any build command that the project actually needs.
  5. Add required environment values privately; use the port supplied by the managed application runtime.
  6. Run Dependencies, then Build when needed, and review each result before deploying.
  7. Select Deploy or Start and check the application status and Logs.
  8. Open the public URL and use Stop, Restart, or a previous deployment only after checking the impact on that website.

4Practical example

Example: a Node.js project with package.json needs its dependencies installed before a start command can work. A plain HTML website normally belongs in a website document root and does not need a background Node.js process.

5Verify the result

Validate the outcome from the affected account or an independent client connection, not only from the administrator screen.

  1. Confirm the managed process shows Running or Healthy.
  2. Request the application URL and inspect the latest application log for startup errors.

6Common problems and what to check

The application exits immediately: check its entry point, dependencies, environment values, and startup log.

A process is running but the site is unreachable: confirm the domain routing and the port the application is listening on.

Permission denied: verify the project belongs to the hosting account and is inside an allowed application directory.

7Security, impact, and rollback

One managed application owns its domain routing. Stop, restart, or delete it only after checking the live site, build output, environment values, and rollback path.

Related guides

App Installers and panel modulesManage Softaculous connectivity and install trusted BigCloudy panel modules.WebsitesFind each hosted domain, its owner, document root, status, and website-level tools.See all guides in Administrator panel

Still need a hand?

Get help with your plan, website, or hosting through your client area.

Open client area