Skip to content

Self-hosted (Edge)Enterprise

The self-hosted Sluis appliance: Console, Workspace and gateway on your own Kubernetes or Docker, with a signed license and optional air-gapped use.

Enterprise only. Sluis Edge runs on a signed license file (a flat annual fee per installation, not billed by usage). Contact hello@sluis.ai to scope your installation and get your license file.

Sluis Edge is the full Sluis product on your own infrastructure: the gateway, the console and Sluis Workspace, with one tenant per installation. It runs the same images as the cloud.

Install

  • On Kubernetes, with the Helm chart.
  • On Docker Engine, with the Compose bundle (on Windows, Linux in WSL2).

What it runs

  • Postgres with pgvector, Valkey, S3-compatible storage and ClamAV.
  • Sign-in through your own OpenID Connect provider is optional. You can require it for the whole installation.
  • Local models are optional: files you import, never pulled at run time.
  • Air-gapped operation (SLUIS_AIRGAP) is supported. Your OpenID Connect provider must then resolve on a private address.

Where traffic goes

Prompts do not transit the Sluis cloud. External model providers still depend on your configuration, so use local models when traffic must stay inside your network.

Install with Helm or the Compose bundle and give it the signed license file license.json.

Renewing the license

  • The gateway re-reads a renewed license within a minute.
  • Replacing an existing license in the Compose bundle needs no restart.
  • A Helm upgrade with new license values rolls the gateway pods, and installing the first Compose license recreates the services.
# Kubernetes (Helm 3.12+): chart, profile and license file from your release bundle
helm install sluis deploy/helm/sluis -n sluis --create-namespace \
  -f deploy/helm/sluis/profiles/airgap-cpu.yaml \
  --set-file license.licenseJson=license.json --set-file license.signature=license.json.sig \
  --set owner.email=ada@corp.example --set owner.name=Ada

# Docker Engine (Compose bundle, air-gapped by default)
cd deploy/compose
./install.sh --version X.Y.Z --license license.json --owner-email ada@corp.example

Observability

For dedicated and self-hosted deployments the gateway exposes compliance-labelled Prometheus metrics:

  • Request counts, labelled by provider, jurisdiction, ownership, routing decision and status.
  • Token volume, cost and latency, labelled by provider.
  • Cache hits and circuit-breaker state.
Audit log: inspect sealed requests and their gate decisions.
Audit log: inspect sealed requests and their gate decisions.English interface · illustrative demo data. Open the image for full size.
  1. Set SLUIS_METRICS_ENABLED.
  2. Scrape /metrics on a private network. With SLUIS_METRICS_TOKEN set, the endpoint needs that bearer token. Without it, the endpoint is open to anyone who can reach it.
  3. Optional: export traces over OTLP with SLUIS_OTLP_ENDPOINT. Every trace carries the request id that correlates it one to one with its audit row.
# operational endpoint: enable with SLUIS_METRICS_ENABLED=true, set SLUIS_METRICS_TOKEN
# to require a bearer token, and keep it network-restricted (private network or mesh)
scrape_configs:
  - job_name: sluis-gateway
    metrics_path: /metrics
    static_configs:
      - targets: ["gateway.internal:8080"]