code-server vs OpenVSCode Server: Which to Host?

Quick Verdict

Both run VS Code in your browser. The meaningful difference: code-server (by Coder) has been around longer, has more server-side configuration options, and uses the Open VSX extension marketplace. OpenVSCode Server (by Gitpod) is closer to upstream VS Code and uses the official Microsoft marketplace, giving you better extension compatibility. If a specific extension only exists on the official marketplace, go with OpenVSCode Server. Otherwise, either works well.

Overview

code-server is maintained by Coder and has been the go-to self-hosted VS Code since 2019. It patches VS Code to run as a server, adds built-in authentication (password-based), and provides additional configuration for server-side features like proxy domains and app ports.

OpenVSCode Server is maintained by Gitpod and takes a thinner approach — it’s closer to unmodified VS Code with server capabilities added. It uses token-based authentication and makes fewer modifications to the upstream codebase, which means VS Code updates land faster.

Feature Comparison

Feature	code-server	OpenVSCode Server
Maintained by	Coder	Gitpod
First release	2019	2021
Extension marketplace	Open VSX (open-source)	Microsoft Marketplace (official)
Authentication	Password (built-in)	Connection token
Docker image	codercom/code-server:4.99.3	gitpod/openvscode-server:1.109.5
Default port	8080	3000
Config file	~/.config/code-server/config.yaml	Command-line flags only
Proxy domain support	Yes (built-in)	No (use reverse proxy)
App port forwarding	Yes (built-in)	Yes (VS Code native)
Telemetry	Disabled by default	Disabled by default
License	MIT	MIT
Container size	~500 MB	~500 MB
RAM (idle)	300–500 MB	300–500 MB
VS Code version lag	1–4 weeks behind upstream	1–2 weeks behind upstream

Extension Marketplace

This is the most important practical difference.

code-server uses Open VSX, an open-source extension registry. Most popular extensions are available, but some Microsoft-published extensions (Python, C++, Remote SSH, GitHub Copilot) are missing or outdated because Microsoft restricts them to the official marketplace.

OpenVSCode Server connects to the official Microsoft VS Code marketplace. Every extension available in desktop VS Code is available here, including Microsoft-published ones.

Bottom line: If you need GitHub Copilot, the official Python extension, or Remote Development Pack, use OpenVSCode Server. For everything else, both marketplaces cover you.

Authentication

code-server uses password authentication configured in ~/.config/code-server/config.yaml. Set a password, and the login page prompts for it. Simple. Supports --auth none to disable.

OpenVSCode Server uses a connection token. You pass it as a URL parameter (?tkn=TOKEN) on first access. The browser stores it. Set CONNECTION_TOKEN=none to disable.

Both should sit behind a reverse proxy with HTTPS for production use. For additional security, put them behind Authelia or Authentik.

Configuration

code-server offers a YAML config file (config.yaml) with options for bind address, port, auth method, cert paths, proxy domain, and more. This makes it easier to configure without modifying Docker Compose.

OpenVSCode Server is configured entirely via command-line flags. Less flexible for complex setups, but simpler for basic deployments.

Performance

Identical. Both run the same VS Code backend. RAM usage (300–500 MB idle, 1–2 GB under load), CPU usage, and responsiveness are effectively the same. Performance differences come from your server hardware and network latency, not from the tool choice.

Use Cases

Choose code-server If…

• You want server-side configuration via a YAML file
• You prefer password-based authentication over token-based
• You don’t need Microsoft-exclusive extensions
• You want built-in proxy domain support for port forwarding
• You’re already using Coder for team development environments

Choose OpenVSCode Server If…

• You need full Microsoft marketplace access (Copilot, Python, C++ extensions)
• You want the closest experience to desktop VS Code
• You prefer minimal modifications to the upstream codebase
• You want faster upstream VS Code version updates

Final Verdict

For most self-hosters, OpenVSCode Server is the better default in 2026. The official marketplace access eliminates the “is my extension available?” question entirely. code-server’s advantages (config file, password auth, proxy domains) are nice-to-haves that reverse proxy configuration can replicate.

If you’re already running code-server and it works, there’s no compelling reason to switch. Both are actively maintained, MIT-licensed, and functionally equivalent for day-to-day development work.

Related

• How to Self-Host code-server
• How to Self-Host OpenVSCode Server
• Best Self-Hosted Development Tools
• Best Self-Hosted Git Hosting
• Docker Compose Basics