Plain explanations of how each Kuant service is built. Each one opens a diagram of the parts and how they connect, on the page of the service it belongs to.
How it fits together
Start with the architecture, then open the service you care about.
From raw telemetry to a gated fix
Signals from every device land in one open-source core. The AI layer turns them into one incident with a cause, and nothing changes device state without passing the gate.
A PostgreSQL cluster that survives a node failure
Applications connect to one address. Behind it, a primary and two replicas are supervised for automatic failover, and every change is archived for point-in-time recovery.
Cloud economics on hardware you own
Workloads run on an open compute platform, sit on software-defined storage, and are protected by integrated backup and a DR site.
A secure network, from the internet edge to the user
Traffic is inspected at the perimeter, segmented inside, and every device config is backed up so each change is attributable.
One identity for every tool, server and device
People are created once in the directory. Single sign-on and MFA carry that identity everywhere, and removing it removes access everywhere.
Mail your business controls, delivered to the inbox
Mail is filtered before it reaches the platform, stored on servers you control, and sent with the records that keep it out of spam folders.
Leave a licence without losing a single check
The new stack is built beside the old one and both run in parallel until the results match. Only then is the old one switched off.
From a commit to production, as reviewable code
Infrastructure and applications live in Git. A pipeline builds and tests them, and the cluster keeps itself in the state Git describes.
Test it, audit it, then watch it around the clock
One engagement covers the three things usually bought separately: offensive testing, compliance audit and 24×7 detection.
One toolchain, wired together
One identity signs people in to every tool, and one path carries an alert all the way to a ticket.
Where the collectors sit
Agents and agentless checks feed a collector close to the devices. Collectors feed the central stack, where the pipeline decides under policy.
Talk to an engineer about your environment
Tell us what you run today and what you need it to do. We reply with a plan, not a brochure.
Get in Touch