Back to all templates
Cloud Commander logo

Cloud Commander

Development256MB+ RAM

Cloud Commander — orthodox web file manager with a built-in terminal and editor for managing remote files from the browser

developmentdevtoolscloudcommanderopen-sourceself-hosteddocker

Deploy Cloud Commander in 3 Steps

1

Connect Your VPS

Add your server credentials to Server Compass

2

Select Cloud Commander

Choose from our template library

3

Deploy & Configure

Fill in settings and click Deploy

No Docker knowledge required
Step-by-step deployment guide

Deploy Cloud Commander on a VPS with Server Compass

Use the Cloud Commander template in Server Compass to deploy a self-hosted browser file manager on your VPS, then verify the web UI.

About 10 minutesBrowser verified
1
Step 1

Open the server Apps tab

Select the tutorial-vps VPS, open the Apps tab, and start a new app deployment. Keep sensitive server details hidden before capturing or sharing screenshots.

Server Compass Apps tab before creating a Cloud Commander app
2
Step 2

Choose an app template

Click New App and choose the template deployment path so Server Compass can load the built-in catalog.

Choosing to deploy an app from a Server Compass template
3
Step 3

Search for Cloud Commander

Use the template picker search to find Cloud Commander in the Server Compass template catalog.

Searching for Cloud Commander in the Server Compass template picker
4
Step 4

Select the Cloud Commander template

Choose the Cloud Commander template. Server Compass fills the cloudcmd service, generated login password, files volume, root config volume, and public web port.

Cloud Commander template selected in Server Compass
5
Step 5

Review the Cloud Commander settings

Confirm the app name and compose service. In this run, the app was named cloudcommander-demo and used host port 4189.

Reviewing Cloud Commander project settings and compose service
6
Step 6

Deploy Cloud Commander

Review the generated compose settings, confirm the Cloud Commander web port is available, and click Deploy.

Reviewing Cloud Commander web port before deployment
7
Step 7

Watch the deployment progress

Keep the deployment modal open while Server Compass uploads the compose file, pulls the Cloud Commander image, starts the container, and verifies the stack.

Server Compass deploying the Cloud Commander template on the VPS
8
Step 8

Confirm Cloud Commander is running

After deployment finishes, return to the Apps tab and confirm the Cloud Commander app is marked Running with its application URL available.

Cloud Commander template running in the Server Compass Apps tab
9
Step 9

Open Cloud Commander in the browser

Open the application URL in a browser. The Cloud Commander login or two-panel file manager confirms the web UI is reachable.

The deployed Cloud Commander web UI loaded in a browser

After Cloud Commander Opens

  • Place Cloud Commander behind HTTPS before exposing browser file management.
  • Change the default admin password on first login.
  • Keep CLOUDCMD_ROOT constrained to /files and avoid mounting sensitive host paths into the container.
  • Back up the Cloud Commander files and root config volumes because they store managed files and service state.
  • Keep the Cloud Commander image updated for dependency and security fixes.

Verified Result

The Cloud Commander web interface loaded successfully from the deployed container.

Cloud Commander deployment questions

What does the Cloud Commander template deploy?

It deploys the Cloud Commander browser file manager with persistent files and root config volumes.

Which port did the tutorial use?

The tutorial used host port 4189, which maps to the Cloud Commander web UI on the same generated internal port.

Does Cloud Commander need setup after deployment?

Yes. Create the first admin account, configure the public URL, then add bot integrations and provider keys.

Should this become a blog post?

No. The deployment guide should live on the Cloud Commander template detail page and be linked from the reusable template deployment docs page.

After Deployment

After deploying Cloud Commander with Server Compass, complete these steps to finish setup

1

Visit http://YOUR_SERVER_IP:{{PORT}} and log in with CLOUDCMD_USERNAME / CLOUDCMD_PASSWORD

2

Upload or create files inside /files using the two-panel UI

3

Open the integrated terminal (Ctrl+~ or the bottom panel) to run shell commands inside the container

4

(Optional) Mount an additional host directory into /files in the compose file if you need to manage real server files instead of a private volume

Need help? Check out our documentation for detailed guides.

Cloud Commander FAQ

Common questions about self-hosting Cloud Commander

How do I deploy Cloud Commander with Server Compass?

Simply download Server Compass, connect to your VPS, and select Cloud Commander from the templates list. Fill in the required configuration and click Deploy. The entire process takes under 3 minutes.

What are the system requirements for Cloud Commander?

Cloud Commander requires a minimum of 256MB RAM. We recommend a VPS with at least 1024MB RAM for optimal performance. Any modern Linux server with Docker support will work.

Can I migrate my existing Cloud Commander data?

Yes! Server Compass provides volume mapping that allows you to import existing data. You can also use standard Cloud Commander backup and restore procedures.

How do I update Cloud Commander to the latest version?

Server Compass makes updates easy. Simply click the Update button in your deployment dashboard, and the latest Cloud Commander image will be pulled and deployed with zero downtime.

Is Cloud Commander free to self-host?

Cloud Commander is open-source software. You only pay for your VPS hosting (typically $5-20/month) and optionally Server Compass ($29 one-time). No subscription fees or per-seat pricing.

Ready to Self-Host Cloud Commander?

Download Server Compass and deploy Cloud Commander to your VPS in under 3 minutes. No Docker expertise required.

Download Server Compass