QryptexAI CAMP · On-prem

Discover, inventory, and govern every cryptographic asset.

CAMP continuously maps the cryptography running across your enterprise — certificates, keys, protocols, libraries and their FIPS posture — builds the network topology, and guides post-quantum migration of your most vulnerable assets. It runs entirely on-prem.

How it works
Boundary-scopedNever past your gateway
FIPS posturePer library & endpoint
Link-level topologySNMP LLDP / CDP / ARP
On-prem onlyNothing leaves your network

An ongoing crypto-asset management platform

Discovery finds it, the inventory governs it, compliance scores it, and alerts keep you ahead — a living picture of your cryptographic posture, not a one-off scan.

Discovery

Boundary-scoped network discovery

Scan your network — never past the org gateway — to find hosts, services, and their TLS posture, then enrich with credentialed connectors (SSH, SNMP, Prometheus).

Inventory

Canonical crypto-asset inventory

Every asset, certificate, key, protocol, cipher, algorithm and library in one encrypted, RBAC'd store — with owner assignment and a credential sign-off workflow.

Sites

Probes at every site

Enrol a probe at each site to scan networks the central server cannot reach, and add a passive sensor that records the cryptography actually in use in traffic, beside what each service offers.

Topology

Inferred link-level topology

Build the enterprise network graph from SNMP LLDP/CDP + ARP. Interactive diagram or list, with unmanaged peers surfaced as external nodes.

Compliance

Color-coded cryptographic posture

Flag weak algorithms, deprecated TLS, non-FIPS and end-of-life crypto libraries, and risky open-port exposure — scored red-to-green by severity.

PQC migration

Evidence-based PQC migration

Compare what vendors claim — including the CBOMs they publish — against what each endpoint actually negotiates, separate a configuration change from a replacement, and track drift as the estate moves.

CBOM

A CycloneDX CBOM of your network

Export the inventory as a CycloneDX 1.6 cryptographic bill of materials, with a PDF report: what is running and negotiated on your network, in the form OMB M-26-15 asks agencies to keep.

Alerts

Email alerts for what changes

Weak cryptography, certificates nearing expiry, drift in what an endpoint negotiates, licence and scan events — each emailed to the recipients you choose.

On-prem

Node-locked on-prem install

Docker Compose or Kubernetes, bundling its own Keycloak and PostgreSQL. Node-locked licensing; nothing leaves your environment.

The workflow

Scan → inventory → sign-off → enrich → govern

A boundary-safe scan finds hosts and their TLS posture. Assets that need deeper inspection are flagged; the owner provides credentials in their own portal (encrypted, never shared). CAMP then enriches with hardware, applications, crypto libraries and FIPS status — and scores compliance red-to-green.

1

Discover

Boundary-scoped network scan finds hosts, services and TLS posture — never past the org gateway.

2

Own & sign off

Flagged assets get an owner; the owner provides credentials in their own login, sealed at rest.

3

Enrich

SSH / SNMP / Prometheus connectors add make/model, apps, crypto libraries and FIPS status.

4

Govern

Color-coded compliance, link-level topology, and email alerts for expiry and weak crypto.

Self-host on your own infrastructure

CAMP runs entirely on your infrastructure. Request access and we email you a read-only registry login, the install instructions and a node-locked licence — bring the stack up, then activate it in the portal.

The images are private, so the install begins with a registry sign-in. Your credentials and the commands arrive with your licence.

Minimum requirements (self-hosted, single VM)

MinimumRecommended
vCPU48
RAM8 GB16 GB
Disk40 GB SSD100 GB SSD
OSLinux x86_64 with Docker Engine 24+—
Networkoutbound 443 to our image registry (install and upgrade only)—
The product

What you actually get

Screens from a running installation, scanning a three-site estate of 149 assets.

The estate as one picture
Assets cluster by site, so proximity means location. The dashed link is a WAN adjacency between two offices — drawn because one router reported the other, never because two sites exist.
Every asset, and where it is
The site column is what keeps two offices on the same private range apart. Each MAC carries how it was learned: ARP is certain, a router's cache is second-hand.
What is weak, and how badly
Findings graded by severity across the estate, from deprecated TLS to keys below every current baseline.
Posture at a glance
Assets, findings, worst posture and open alerts — the answer to 'how bad is it' before anyone opens a table.