One gateway in front of every LLM provider. Pick the desktop Application, the headless-capable CLI, a container image, or a hosted deployment — every build ships from the same signed release.
Could not load this source’s release details. The links below open its releases page; you can also choose another source.
One-line install
Installs the CLI for this computer and walks you through the database, administrator account and proxy. For the desktop Application, download it below.
Linux · macOS · Termux
curl -fsSL https://gproxy.leenhawk.com/install.sh | sh
Windows PowerShell
irm https://gproxy.leenhawk.com/install.ps1 | iex
Skip the questions
Add -y and any options to install without prompts. Run the script with --help to see them all.
GNU builds suit most distributions. musl builds offer Alpine APKs (apk-tools 3; import the signing key first). The CLI is static; the Application needs Alpine edge GTK/WebKitGTK.
Open GPROXY. A short wizard asks for the port and data folder, an administrator name and password, and an optional configuration to import. Keep the address and API key it shows at the end.
CLI
If you used the one-line installer, start GPROXY with the command it printed. Otherwise run the command below. Then open the console in your browser and sign in. A new instance prints its administrator password and API key once, so save them.
gproxy serve --data-dir ./data
http://127.0.0.1:8787/console/
Containers
Images on Docker Hub (gproxy2/gproxy), GitHub, GitLab and CNB registries for amd64, arm64 and riscv64. Stable versions use vX.Y.Z tags; beta is staging and development snapshots are nightly.
docker run -d --name gproxy -p 127.0.0.1:8787:8787 -v gproxy-data:/app/data gproxy2/gproxy:latest
Every release attaches a SHA256SUMS file and a signed manifest.json. The CLI and Application verify the same Ed25519 signature before self-updating; signing keys live only in the release pipeline.