Deployment
Installing krupiq on your machines, the licence, and what is planned for larger deployments.
Updated
krupiq installs on the machines you want to protect. The install guide for each system, with its paths, service account and settings, ships with each release; this page describes the shape of a deployment.
Installing
- As an app: each edition runs with a window, or from the command line.
- As a service: Micro installs as a service on Windows, Linux or macOS and runs under its own account.
- It sends nothing of yours out of your network.
Licence
A licensed deployment renews its licence with krupiq.com. A renewal carries counts and hashes, never content. See Proofs and compliance for what leaves your network and what does not.
Planned, not yet available
Decided, and not built yet:
- Enrolling machines to your own Chimera server. Each enrolled machine keeps one outbound, mutually authenticated connection to Chimera and opens no port for that control channel.
- Chimera as a cluster: one active node and standbys, a standby promoted only by a signature from your Operator Keys, and one licence for the cluster.
See Architecture for the whole plan. This page will say when each ships.