Requirements

Everything to prepare before installing Klipsu Sentinel. Most organisations run one Sentinel node for evaluation and two or more nodes behind a load balancer in production.

What you need

• A server: Linux x86-64 or ARM64 (the binary is static; any distribution), or Windows Server 2019+ x86-64. 2 vCPU and 2 GB RAM handle about 2,000 devices.
• PostgreSQL 14 or newer (17 recommended): an empty database and a role that owns it. No extensions are needed. Plan about 200 MB of database storage per active person per year (encrypted sync history and images).
• DNS names and TLS certificates:
  • Endpoint (for example sentinel.example.com): used by devices; it must be reachable from where employees work (internet or VPN).
  • Console (for example sentinel-admin.example.com): for the security team; keep it on an internal network. It can share the endpoint's name and listener if you prefer.
• A place to keep two secrets safe: the key file (sentinel.key, created at initialisation) and the evidence passphrase (chosen at setup).

Network

Ports (defaults, configurable)

Listener	Default	Who connects
Endpoint (device API, enrollment page)	:8443	Klipsu apps, employees' browsers during enrollment
Admin (console)	:9443	security team
Outbound	as configured	PostgreSQL; SIEM, webhooks or Slack if you add integrations

Sentinel makes no other outbound connections: no telemetry, no license server, no update checks.

Next steps

• Install on Linux or Install on Windows