Architecture

What runs on your machines, how the decoy moves, what the proofs show, and why your data stays where it is.

Updated

krupiq runs on your own machines, as an app or as a service. It presents the decoy there and watches it. Emersa runs nothing in your environment and receives nothing of yours.

On each machine

Each edition runs on the machine it is installed on: as an app with a window, or, with Micro, as a service under its own account on Windows, Linux or macOS. It sends nothing out of your network.

The decoy moves in epochs

The values that shape the decoy’s appearance move in epochs of 300 seconds, along a bounded walk drawn for each deployment: each epoch moves a value by at most a few percent of its range. The walk is fixed in advance by a key. The appearance never reacts to a probe, because a decoy that reacts to probing tells the prober it has been seen.

Proofs

Each epoch carries one VRF proof: evidence that the epoch’s values were derived correctly from the deployment’s key and a public input. The deployment keeps the secret key; you and your auditors check the record offline with the public key and the krupiq-verify tool (see Integrations).

The proof is about the decoy, not about your data. It shows that the values were derived as published; it does not show who chose the key, or vouch for anything a compromised machine wrote.

Data flow

  • Real traffic: sessions are counted, never recorded. No bytes are kept.
  • The description of your network that shapes the decoy stays on the machine.
  • Out to Emersa: nothing of yours. A licensed deployment renews its licence with krupiq.com, carrying counts and hashes, never content.

Planned, not yet available

Decided, and not built yet:

  • Enrolled agents. Micro gains an enrolled mode: each machine keeps one outbound, mutually authenticated connection to your own Chimera server and opens no port for that control channel.
  • Chimera as a cluster. Several nodes, one active and the others on standby; a standby is promoted only by a signature from your Operator Keys. One licence covers the cluster.
  • An offline evidence copy of the record, kept apart from the running system.

This page will say when each of these ships.