Company
危険 — it means danger.
Kiken is the Japanese word stenciled on hazard signs. We chose it because that's the job: not preventing every bad thing — seeing danger early enough that you can act.
How we work
Three principles we won't trade.
Claims are checked against code.
Every capability statement in our materials is verified against the shipped product before it's published. If something is roadmap, we label it roadmap. Security buyers have been burned enough.
Detection, done exceptionally well.
We don't chase the whole acronym soup. Kiken does discovery and early warning — and integrates cleanly with the prevention and rights-management layers you already operate.
Privacy is a design input.
Clipboard checks report match summaries, not contents. Evidence capture is off by default and opt-in per device. Screenshots live in private storage behind short-lived links.
How it's built
Systems software, not shelfware.
The agent and server are written in Rust and run as native OS services on macOS, Linux, and Windows — the kind of software you forget is there until it tells you something you need to know.
Agents self-update with checksum verification and rollback, hot-reload configuration without restarts, and talk to your self-hosted server over a real-time channel. The dashboard gives your team fleet control, alerts, and reporting in one place.
We build with design partners, in production, against real fleets. If that sounds like your team, we'd like to meet you.
Work with people who tell you what doesn't work.
The fastest way to find out if Kiken fits is to ask us the hard questions first.