Remote Desktops: noVNC
Remote desktops put a full Linux GUI behind a browser tab, which powers agentic computer-use workloads, secure browsing sessions, and disposable workstations. They are memory-hungry and used in short, interactive bursts, so each desktop runs in its own instance that scales to zero between sessions.
This guide explains how to create and deploy a noVNC app, allowing you to access remote desktops through a web interface inside a modern browser.
Note: Anthropic's Computer Use Demo inspired this example.
To run this example, follow these steps:
-
Install the unikraft CLI. You need a BuildKit builder. The easiest way to get one is via Docker. Alternatively, you can also directly set up and use BuildKit, see the quick start.
-
Clone the
examplesrepository andcdinto theexamples/novnc-browserdirectory:Code
Make sure to log into Unikraft Cloud and pick a metro close to you.
This guide uses fra (Frankfurt, 🇩🇪):
Code
When done, invoke the following command to deploy this app on Unikraft Cloud:
Code
The output shows the instance address and other details:
Code
In this case, the instance name is vnc-browser and the address is https://weathered-fog-y5jjmwfd.fra.unikraft.app.
The name was preset, but the address is different for each run.
Enter the provided address into your browser of choice to access the remote desktop interface.
This exposes an unauthenticated remote desktop interface to the public internet.
To require authentication, use websockify authentication plugins (--auth-plugin, --auth-source, --web-auth).
See auth_plugins.py for the available plugins.
You can list information about the instance by running:
Code
Code
When done, you can remove the instance:
Code
Learn more
Use the --help option for detailed information on using Unikraft Cloud:
Code
Or visit the CLI Reference.