Self-hosted (Edge)Enterprise

The self-hosted data plane: install, sync, live reads, and observability.

Sluis Edge is the self-hosted data plane: one binary embedding the same router, providers, and gate, with local state and an outbound-only control tunnel to the cloud console. Keys, policy, and BYOK credentials sync down; usage and audit are read live from the box and never stored in the cloud.

Install on any systemd host with the one-liner below; configuration lives in /etc/sluis-edge/env and survives re-runs and reboots.

# one-liner install on a systemd host — values from the Console's Gateways view
curl -fsSL https://get.sluis.ai/edge/install.sh | sudo bash -s -- \
  --control-url wss://api.sluis.ai/edge/connect \
  --install-token sluis_edge_install_…

systemctl status sluis-edge     # service health
journalctl -u sluis-edge -f     # live logs

Observability

For dedicated and self-hosted deployments the gateway exposes compliance-labelled Prometheus metrics: requests, tokens, cost, and latency broken down by provider, jurisdiction, and routing decision, plus cache hits and circuit-breaker state.

Enable with SLUIS_METRICS_ENABLED and scrape /metrics on a private network. Traces export over OTLP (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 and
# keep it network-restricted (private network / mesh); never bind it public
scrape_configs:
  - job_name: sluis-gateway
    metrics_path: /metrics
    static_configs:
      - targets: ["gateway.internal:8080"]