Services and ports

Kisuno runs as a Docker Compose stack. The chat application and the services it needs each run in a container of their own and talk to each other over an internal network.

What is reachable from the outside

The only thing published to the outside is a reverse proxy on the usual web ports, which terminates TLS and distributes everything else internally. All remaining services are reachable exclusively on the internal network and are not published on the host.

Which services a delivery covers in detail and how they are switched on is described in the operating documentation.

Plan network access

Besides the web ports, the instance needs an outbound path to the model provider. Decide before going live which destinations the server may reach on the outside, and allow access to the server itself only from your administration network.

Operating documentation

The list of the individual services with their tasks and dependencies, the network and deployment variants as well as the checks for operation are included with the delivery. Customers receive these documents together with their access.

How the stack is started, stopped and observed day to day is on the command reference page. The licenses of the building blocks involved are on the licenses and origin page.