Skip to content
SolidwayLLM gateway
English中文

Deployment

Deployment

One binary and one configuration file. The gateway runs wherever your workloads already run.

  • Docker

    A distroless image with the binary and nothing else.

    docker run -p 8080:8080 \
  -v ./solidway.toml:/etc/solidway.toml \
  solidway/gateway

  • Kubernetes

    Deployment plus Service manifests, with readiness and liveness probes wired to the health endpoint.

    kubectl apply -f \
  deploy/kubernetes/

  • Bare metal

    A statically linked binary for x86-64 and arm64, with no runtime dependency.

    ./solidway --config ./solidway.toml

Operational notes

0
ConfigurationOne TOML file, hot-reloaded on change
1
SecretsEnvironment variables, files, or your existing secret store
2
NetworkOutbound HTTPS to providers; no inbound control plane
3
TelemetryOff by default; opt in per exporter

Next step

Talk to us about your architecture

Tell us how your traffic is shaped today. We will walk through where a forward path fits, what the failure policy should look like, and how the gateway would be deployed in your environment.

Request a conversationRead the architecture notes

No pricing on this page. Every deployment is scoped individually.

  • A review of your current provider and key layout
  • A failure policy matched to your error classes
  • A deployment shape for your network