Straight answers.

krupiq is a deception platform for the enterprise. It builds a living twin of your network from Zeek JSON. The twin looks, answers and changes like the real thing, so an attacker spends their time inside it while you watch every move. Nothing real is exposed and nothing raw leaves your environment.

Static decoys get fingerprinted and ignored. The krupiq ghost network morphs in thirty-second epochs and adapts its entropy when it is probed, so it never looks the same twice and cannot be told apart from your infrastructure.

Hosts that answer, services that behave and data that looks real, none of it real. Every packet they send is recorded from the first one, and their effort is spent on a network that does not exist.

No. The container reads Zeek JSON locally and generates synthetic personas. Real records are never copied, never sent to the portal and never visible to us. The customer holds the keys, and a proof for every epoch shows the platform ran exactly as published.

As a container on Kubernetes, ECS or any Docker host, one per network segment. No agents, no kernel modules, no privileged containers, no host networking. Fifteen minutes from zero to a running ghost network is the normal case.

Because the platform has zero access to real data, the compliance position rests on architecture rather than policy. Auditors receive per-epoch proofs, complete engagement records and signed deployment evidence, exported as JSON or PDF.

One fixed annual fee. No per-seat, per-alert or per-gigabyte pricing, and no incident fees. Contact sales for a quote.

Yes, under NDA, for qualified prospects. Images are reproducible builds signed with sigstore, so what you review is what runs.