Manage your Incus deployment from the web.
Incus UI Application Shell
Incus UI is currently in its infancy and its foundation is still under construction 🏗️. The first release (v0.1) is scheduled for November 12th, which will cement this foundation. From there, robust primitive implementation will begin.
We follow a semi-monthly release cycle, shipping a release alongside each monthly Incus feature update, and an additional release in-between.
For a holistic detailed roadmap for each planned version, see our GitHub Milestones.
Below is a high-level summary of our progress supporting the foundational Incus primitives and their target releases. This list will be updated as more support is implemented over time.
-
Projects
- Listing & switching (v0.1).
-
Server/Cluster
- TLS Client Certificate Authentication (v0.1)
- OpenID Connect (v0.1)
- CLI Authentication Flows (v0.1)
-
Instances
-
Storage
-
Networks
-
Images
-
Profiles
Incus UI supports the latest Incus release in each actively maintained Incus channel, starting with Incus 7.
As the first version of Incus UI has not yet released, this is the only version available to install until 11/12/2026.
Edge builds are compiled as code is merged into the main branch. These grant you access to features before they appear in the upcoming release.
Download the incus-ui.tar.gz artifact from a successful run of the Build Edge workflow. GitHub Actions downloads artifacts as zip files, so unzip the download first to obtain incus-ui.tar.gz.
If you installed Incus using a Zabbly package, use /opt/incus/ui as follows:
mkdir -p /opt/incus/ui
tar -xzf incus-ui.tar.gz -C /opt/incus/ui
If you installed Incus through another route, set the INCUS_UI environment variable for incusd to your preferred path, and extract Incus UI there.
If you have already previously installed a UI to this path, you will need to remove it (e.g. rm -r /opt/incus/ui).
If you use systemd, use:
systemctl restart incus
Simply visit your Incus host in the browser, and Incus UI will be served.