Ghost Architect™ Local · version 7.0.4

Download and install

Ghost Architect™ Local is delivered directly by us, not through a public package registry. You receive one tarball, you check it against the SHA-256 published here, and the installer does the rest. The evaluation trial starts inside the product; no card, no account.

1. Get the tarball

Request the download

Fill this in and EJ replies with the download link, or with access to the delivery repository on GitHub, usually the same day. The GitHub username is for that access. The model question is so the trial is set up for the hardware you have.

Already a customer with access to the delivery repository? gh release download v7.0.4 --repo EJWisner/ghost-local-delivery

Verify it before you unpack it

The file is about to become a global command on your machine. Check it first.

shasum -a 256 ghost-architect-local-7.0.4.tgz

On Windows PowerShell:

Get-FileHash -Algorithm SHA256 ghost-architect-local-7.0.4.tgz

Expected for 7.0.4:

12b6d385a7f4f9140c0378064a6c1235fed19f6729275e65759041d5a9e9d8fb

If the hash does not match, stop. Do not install it. Email [email protected] with what you got.

2. What you need

macOS 13 or later, Linux, or Windows 10 or later

The installer checks the OS floor and stops below it. Linux installs run as a service account with a data root the installer creates, and the Linux path is verified on a fresh machine for every release. Windows uses a PowerShell installer from an elevated prompt and registers Windows Services; it ships covered by tests but has not yet been run on a real Windows machine, and says so in its own header. Treat a Windows install as a first run and send us the console output.

Node.js 24 or later

The installer checks it and does not install it. Get it from nodejs.org or your version manager first.

A model server with a model pulled

Ollama, vLLM, LM Studio, Jan.ai or any OpenAI-compatible endpoint on your network. Our estate runs qwen3:14b on Ollama. The installer asks which and checks it answers.

A second machine, when you want the estate

Any of the three can be a spoke. Enrol it from Admin Console on the hub and it runs scans and reports them back; the model calls go to the hub's model server over your LAN.

3. Install

Everything happens inside the directory you unpack. Keep that directory; the global ghost command links into it rather than copying it.

tar -xzf ghost-architect-local-7.0.4.tgz
cd package
bash install/setup.sh              # macOS
sudo bash install/setup-linux.sh   # Linux
.\install\setup.ps1                 # Windows, elevated PowerShell

The installer changes four things on your machine, and INSTALL.md, in the directory you just unpacked, is the authoritative list of them. Re-running the installer is the supported upgrade path: your service account, data root and signing key are left alone.

4. First run and the trial

Run ghost. The evaluation trial starts on first use, registered against this install, and the product tells you the day it ends.
Point it at a codebase. Start with Recon: one planner call that sizes the codebase and tells you what a full scan would read, how many passes, and how long, with the basis of that estimate printed beside it.
Open the portal it prints (https://localhost:3443 by default): the Fleet page, the queue, LLM Status, the reports. Trust its certificate the way the page tells you to.
Enrol a second machine from Admin Console when you want the estate view. Every machine reports back to the hub.
To keep it, convert from inside the product during the trial. The first year is half price and the licence arrives by email, signed, and activates against this install.

Zero egress, if that is how you work

Activation is the one call home (the licence key and an install id, nothing from your code). After it, turn on zero-egress mode and the product refuses every outbound destination at the code level and prints the inventory that proves it. Details on the security page.