Skip to content
SolidwayLLM gateway

These pages describe the intended behaviour of the gateway. The open-source release and the enterprise edition are being split out; details will be updated when the first release ships.

Installation

Run Solidway from a container, a Kubernetes manifest, or a single binary.

Solidway ships as one statically linked binary for x86-64 and arm64. There is no runtime to install on the host.

Docker

docker run -d --name solidway \
  -p 8080:8080 -p 8081:8081 \
  -v ./solidway.toml:/etc/solidway/solidway.toml:ro \
  -v solidway-state:/var/lib/solidway \
  solidway/gateway

The image is distroless: it contains the binary and nothing else. Because there is no shell, docker exec will not give you a prompt — use the logs and the health endpoint.

Kubernetes

kubectl apply -f deploy/kubernetes/

The manifests include a Deployment, a Service, a ConfigMap for the bootstrap file, and a PersistentVolumeClaim for console state. See Kubernetes.

Binary

tar xzf solidway-x86_64-unknown-linux-musl.tar.gz
./solidway --config /etc/solidway/solidway.toml

Requirements

Network Outbound HTTPS to your providers. No external control plane is contacted.
Configuration One small TOML file: listen address, public domain, state directory
State A writable directory. Console-managed configuration lives there.
Console A second port, bound to a private interface

Next