Install

Gateshift installs from its repository on GitHub, which holds the Community Edition. There is no download on this site and no registration.

Requirements

The installer checks all of this before it changes anything.

Local machine

git clone https://github.com/gateshift/gateshift.git
cd gateshift
./install.sh

The web UI then listens on http://127.0.0.1:8080.

Remote server

git clone https://github.com/gateshift/gateshift.git
cd gateshift
./install.sh --bind 0.0.0.0

On a server the bind address has to be given explicitly. The web UI then listens on http://<server-address>:8080.

The web UI binds to loopback by default and has no authentication of its own. Making it reachable from the network is an explicit option and belongs behind a reverse proxy or on a trusted management network. The web container mounts the host's Docker socket, which is root-equivalent access to the host. Run the stack on a host you would trust with firewall credentials anyway.

Configuration

The installer generates strong random credentials into .env (never overwriting an existing one) and starts the stack. .env.example documents every setting if you prefer to set up .env yourself.

Air-gapped installs

Gateshift needs no internet access to run: no telemetry, no phone-home, no licence callbacks, no cloud uploads, no LLM calls. The exception is the image build, which downloads the Tailwind CLI from GitHub, so build the images where there is egress, or provide a proxy. Every installer option is documented in the repository.

Before the first migration

What Gateshift does not do is written down: read KNOWN_LIMITATIONS.md in the repository before the first migration. The overview lists what verification means before a cutover, the legal page carries the warranty disclaimer.