Install

One command. It runs on your machine, and your code never leaves it.

Watch instead: The StellarView Unboxing, from 00:00. 50 seconds.

What you need

Docker, and nothing else. No account, no sign-up, no cloud to connect to.

You will want a GitHub token and a Claude key eventually — see Keys — but neither is needed to start it and look around.

Load the image

Your download link gives you one file. It is the image itself, not an installer, and it came from us rather than from a public registry. There is nothing to log in to and nothing that can change under you between now and the next time you run it.

$ docker load -i stellarview-<release>.tar.gz
Loaded image: stellarview:<release>

The link is yours and expires. If it has, ask for another. Grants are per person, so a new one takes a moment.

Run it

Put this in a docker-compose.yml in an empty directory:

services:
  stellarview:
    image: stellarview:<release>
    ports: ["127.0.0.1:3456:3456"]
    env_file: [./config/.env]
    volumes:
      - ./config:/app/config
      - ./galaxies:/app/galaxies
      - ./mission-artifacts:/app/mission-artifacts

Then:

$ mkdir -p config galaxies mission-artifacts && touch config/.env
$ docker compose up

Open http://localhost:3456.

From up to the first screen took four seconds on the machine this was written on, with the image already loaded. Loading the image is the slow part and you do it once.

What the three volumes are for

They are the reason this is worth doing rather than running a container and forgetting it.

config/	your keys, in a file you own. Deleting the container does not touch them
galaxies/	the repositories it has read, and their analysis
mission-artifacts/	what its runs produced

Everything StellarView learns lives in those three directories, on your disk. The image is disposable. Pull a new one and keep the state.

Worth knowing

The port is bound to localhost on purpose. 127.0.0.1:3456 rather than 3456 means only your machine can reach it.

There is no authentication in this beta. Anyone who can reach the port has the whole cockpit, including your tokens. Do not remove the 127.0.0.1 binding, do not forward the port, and do not run it on a shared machine. This is a trusted-user release and that is a real constraint, not boilerplate.

Your code is not uploaded. Repositories are cloned to galaxies/ and read there. What leaves your machine is what you would send anyway: API calls to GitHub and to Claude, with your own keys.

The download is around 1.3 GB, which unpacks to roughly 5.4 GB on disk. docker load takes a minute or two. After that the image is local and every start is seconds.

About a third of that is a browser and ffmpeg. They are there because this instance renders its own films and documents rather than fetching ours.

---

Next: Keys. Two required, seven optional.