Skip to main content
Development

Self-host code-server on a VPS

VS Code in the browser, on your own server.

Run a full VS Code instance on a VPS and code from any browser, tablet or thin client, with your files staying on the server.

Start freeSee VPS plans

Why self-host code-server?

code-server gives you a consistent development environment anywhere, and keeps source code off borrowed machines.

How to install code-server

  1. 1

    Provision a VPS

    Pick a Debian/Ubuntu template and get root SSH in about a minute.

  2. 2

    Install the runtime

    Install Node.js binary or Docker.

  3. 3

    Deploy the application

    Net what you need from the project’s official source and run it.

  4. 4

    Put it behind TLS

    Reverse-proxy with Nginx and issue a Let’s Encrypt certificate.

  5. 5

    Add it to your backups

    Include the data directory and database in your backup routine before you rely on it.

Practical tips

  • Give code-server its own database user with rights only on its own schema.
  • Reverse-proxy code-server and terminate TLS at the proxy so certificates are managed in one place.
  • Take a VPS snapshot before major upgrades so you can roll back cleanly.
  • Keep code-server patched — most self-hosting incidents are unpatched software.

Frequently asked questions

How much RAM does code-server need?
Plan on 2–4 GB for typical use; add headroom if you expect many concurrent users.
What stack does code-server run on?
Node.js binary or Docker.
Can I run other things on the same VPS?
Yes — size the plan so code-server plus your other workloads fit in RAM with room to spare.

Looking for something else? Popular alternatives include Eclipse Che, Gitpod (hosted), OpenVSCode Server — browse all app guides.

About code-server

code-server is open-source software released under the MIT licence. HostingSwift does not maintain, sell or support code-server itself — you install and run it on your own VPS. These are the official links to the project:

Read the project's own documentation before deploying. We credit upstream projects because we genuinely run and recommend them — see our full open-source directory.