Genestack Console Powered by P.Industries

Install

A dedicated server. One command. Open the Console.

Install it on its own Linux server. That server never joins the cluster. We recommend it be L2 with the machines it installs, so it can start them from the network. Run the command on that server, then open http://127.0.0.1:8080/ui there. That page is the Console. From a laptop, forward the port with ssh -L 8080:127.0.0.1:8080. If the server cannot be L2 with a site, install the console agent there. You still run the job from the Console. Optional later: link at my.genestack.dev for Apple apps and support. That account page does not run the Console.

The Console

curl -fsSL https://get.genestack.dev/console.sh | bash

Then http://127.0.0.1:8080/ui on that server. PowerShell: irm https://get.genestack.dev/console.ps1 | iex. After you sign in, your first cluster is the setup: a cluster you already have, Talos from an ISO, or Ubuntu that is already installed. A management port is optional.

Run the same command again to move an install to the latest binary. It leaves the config, the database, and /opt/genestack as they are. To install one published build: curl -fsSL https://get.genestack.dev/console.sh | bash -s -- --version 2026.10.04.3. A later run with no version follows latest again.

A production deploy host runs that published binary. Clone the repository when you are changing the console and testing that change. A checkout can run on a deploy host. The install we support in production is the binary.

The virtual machine disk and the installer CD are on Releases, next to the program file.

The API

The webpage on the deployer is a client of /api/v1. You can call the same API yourself. A linked account does not replace the Console on that server. API docs.

The stack is what that cloud looks like. Talos is the preferred boot onto the metal. Kubespray adopts machines that already have an OS. Connect comes after.

Source

The code, the build, and what changed.

Genestack Console is open source. The repository is PIndustries/genestack-console, Apache-2.0. A tagged release is the build a production deploy host runs. That workflow makes the Linux binary, and the install command downloads it. Clone the repository when you are changing the console and testing that change. A checkout can run on a deploy host. The install we support in production is the binary. Commits on main after a tag are in the source. They ship in the next release.

Loading the repository…