Workspace Proxies

Workspace Proxies

Workspace Proxies

Workspace proxies are in an experimental state and the behavior is subject to change. Use GitHub issues to leave feedback. This experiment must be specifically enabled with the --experiments="moons" option on both coderd and the workspace proxy.

Workspace proxies provide low-latency experiences for geo-distributed teams.

Coder's networking does a best effort to make direct connections to a workspace. In situations where this is not possible, such as connections via the web terminal and web IDEs, workspace proxies are able to reduce the amount of distance the network traffic needs to travel.

A workspace proxy is a relay connection a developer can choose to use when connecting with their workspace over SSH, a workspace app, port forwarding, etc. Dashboard connections and API calls (e.g. the workspaces list) are not served over workspace proxies.


Deploy a workspace proxy

Each workspace proxy should be a unique instance. At no point should 2 workspace proxy instances share the same authentication token. They only require port 443 to be open and are expected to have network connectivity to the coderd dashboard. Workspace proxies do not make any database connections.

Workspace proxies can be used in the browser by navigating to the user Account -> Workspace Proxy


  • The Coder CLI must be installed and authenticated as a user with the Owner role.

Step 1: Create the proxy

Create the workspace proxy and make sure to save the returned authentication token for said proxy. This is the token the workspace proxy will use to authenticate back to primary coderd.

$ coder wsproxy create --name=newyork --display-name="USA East" --icon="/emojis/2194.png"
Workspace Proxy "newyork" created successfully. Save this token, it will not be shown again.
Token: 2fb6500b-bb47-4783-a0db-dedde895b865:05271b4ef9432bac14c02b3c56b5a2d7f05453718a1f85ba7e772c0a096c7175

To verify it was created.

$ coder wsproxy ls
NAME         URL                    STATUS STATUS
newyork                             unregistered

Step 2: Deploy the proxy

Deploying the workspace proxy will also register the proxy with coderd and make the workspace proxy usable. If the proxy deployment is successful, coder wsproxy ls will show an ok status code:

$ coder wsproxy ls
NAME              URL                           STATUS STATUS
brazil-saopaulo   https://brazil.example.com  ok
europe-frankfurt  https://europe.example.com  ok
sydney            https://sydney.example.com  ok

Other Status codes:

  • unregistered : The workspace proxy was created, and not yet deployed
  • unreachable : The workspace proxy was registered, but is not responding. Likely the proxy went offline.
  • unhealthy : The workspace proxy is reachable, but has some issue that is preventing the proxy from being used. coder wsproxy ls should show the error message.
  • ok : The workspace proxy is healthy and working properly!


Workspace proxy configuration overlaps with a subset of the coderd configuration. To see the full list of configuration options: coder wsproxy server --help

# Proxy specific configuration. These are REQUIRED
# Example: https://coderd.example.com

# Runtime variables for "coder start".
# Example: https://east.coderd.example.com
# Example: *.east.coderd.example.com


# Additional configuration options are available.

Running on a VM

# Set configuration options via environment variables, a config file, or cmd flags
coder wsproxy server

Selecting a proxy

Users can navigate to their account settings to select a workspace proxy. Workspace proxy preferences are cached by the web browser. If a proxy goes offline, the session will fall back to the primary proxy. This could take up to 60 seconds.

Workspace proxy picker

See an opportunity to improve our docs? Make an edit.