Q-Ready by Knowlcom

The local AI for cybersecurity.

An on-device, offline AI security analyst. Its flagship capability is post-quantum readiness: it finds the cryptography quantum computers will break, explains the risk and builds a coordinated migration plan, without your data leaving your network.

Ask Q-Ready answering from a scan, with cited findings and its read-only principles alongside.

How it works

A deterministic engine, with a grounded AI on top.

  1. 01 · Discover

    Find every algorithm

    Code, configuration, keys, certificates, binaries, network endpoints and cloud key stores, inventoried by a deterministic engine.

  2. 02 · Assess

    Score the quantum risk

    A Q-Readiness score, a Mosca timeline against your deadline profile and a crypto-agility index.

  3. 03 · Ask

    A grounded AI analyst

    Ask in plain language. Every answer cites your scan or the local knowledge base and passes a grounding check.

  4. 04 · Plan

    A plan you sign off

    Coupled systems grouped, five gated waves and a sign-off record for your change advisory board. Your teams execute.

Why post-quantum first

Data recorded today can be decrypted later.

Harvest-now, decrypt-later makes long-lived data exposed already. Every post-quantum roadmap starts with knowing where vulnerable cryptography lives.

Read-only by design

It audits and plans. It never executes.

Q-Ready does not patch code, rewrite configuration or rotate keys. Changing one layer alone can break every peer, client or partner that still depends on the current keys.

  • Ask for a change and you get migration guidance: what would need to change, what it is coupled to, which wave it belongs to and whether that wave is safe to start.
  • No diffs, patches or pull requests. The AI’s actions only navigate, to a plan item, the scan picker or network discovery.
  • Plan sign-off records a decision. It triggers nothing; your teams execute through change management.

How the AI works

Ask Q-Ready declining a request to apply fixes and delete old keys, and explaining that changes belong in a coordinated migration plan.
A change request, answered with a plan instead of a patch.

Migration planner

Change what must change together, in the right order.

A single-layer change can break every system that still depends on the current keys. The planner turns the inventory into a coordinated plan your change advisory board can sign off.

  1. 01

    Dependency graph

    Couplings through protocols, trust anchors, signature chains, libraries and key stores, with blast radius and must-change-together groups.

  2. 02

    Five gated waves

    Foundations; stop harvest-now, decrypt-later; signatures and PKI; remaining public-key use; symmetric and hygiene. Each has prerequisites, interoperability checks, coexistence, rollback and validation gates.

  3. 03

    Readiness you can trust

    A wave reads not safe to start until every prerequisite is met or attested. Gates the scan can verify cannot be attested.

  4. 04

    Signed-off plans

    Sign-off records the reviewer, decision and waves covered, bound to a SHA-384 digest of the plan. Export as Markdown, CSV or JSON.

Migration plan readiness view: no wave is safe to start yet, with the prerequisites each wave is waiting on.
Readiness: what each wave is waiting on.
Migration plan dependencies: TLS key exchange and signature chains that must change together, with sequencing for each.
Dependencies: what must change together, and in which order.
Migration plan board with work items across the five waves.
Board: every work item, by wave.
Plan sign-off dialog: decision, waves covered and attested prerequisites, recorded as a decision only.
Sign-off: a recorded decision. Execution stays with your change management.
Mosca timeline for each algorithm against a deadline profile, with the crypto-agility index and where the exposure is.
Mosca timeline, crypto-agility index and exposure for one project.

Quantum risk

Know which data is already late.

The Mosca timeline compares migration time and data shelf life with the window for a cryptographically relevant quantum computer. A crypto-agility index shows how hard each swap will be.

Ten deadline profiles set the horizon:

  • IN-CII-2029
  • IN-OTHER-2033
  • US-CNSA2
  • US-NIST-IR8547
  • US-OMB-HVA
  • EU-2030
  • UK-NCSC-2035
  • AU-ASD-2030
  • CA-CCCS-2035
  • JP-NCO-2035

On-device AI

An analyst that never leaves the machine.

Grounded in your own evidence, and never the one that makes the change.

  • Local by default

    The built-in Core backend answers on the device with no model download. Optional local models run in-process or on a loopback server; there are no cloud AI calls.

  • Signed model bundles

    Optional model weights load only from a bundle signed by a key you trust. None ship with the app, and nothing downloads automatically.

  • Cited and checked

    Every sentence cites engine evidence or the local knowledge base. A draft that fails the grounding check falls back to the extractive answer.

  • Deterministic first

    Findings come only from the rule engine and collectors. The AI cannot create, delete or alter a finding.

  • Injection-aware

    Instruction-like text inside scanned files, certificates or banners is withheld and never followed.

  • Offline by design

    Works air-gapped. The knowledge base is embedded and the advisory feed is offline.

How the AI works

Modules

One inventory, from source code to key vaults.

Choose a group to see what it covers.

  • 01

    Ask Q-Ready

    A local AI security analyst with cited, grounding-checked answers, for newcomers and experts alike.

  • 02

    Migration guidance

    Change requests are answered with what would need to change, what it is coupled to and which wave it belongs to. No patches.

  • 03

    Migration planner

    Dependency graph, must-change-together groups, five gated waves and a signed-off plan.

One deterministic engine underneath.

Measured on a single 8-vCPU test host: 120,000 files in 2.12 s with a warm cache, and 49.1 s on a cold first run. Times differ on other hardware.

Outputs

Evidence in the formats your tools read.

  • CycloneDX 1.6 CBOM
  • SARIF 2.1.0
  • Reports (HTML, PDF, CSV, JSON)
  • Migration plans (Markdown, CSV, JSON)
  • Plan sign-off records
  • Compliance evidence packs
  • Hybrid-signed result bundles
  • SIEM and ticketing events

The Cryptography Bill of Materials is validated against the official CycloneDX 1.6 schema. SARIF feeds code-scanning dashboards; hybrid-signed bundles carry results to the Console.

Evidence mapping

qready-cbom.cdx.jsonexcerpt from a sample report
{
  "bomFormat": "CycloneDX", "specVersion": "1.6",
  "components": [{
    "name": "3DES (3des-cbc)",
    "cryptoProperties": { "assetType": "algorithm",
      "algorithmProperties": { "primitive": "block-cipher",
        "nistQuantumSecurityLevel": 0 } },
    "evidence": { "occurrences": [{
      "location": "config/sshd_config", "line": 5 }] },
    "properties": [
      { "name": "knowlcom:qready:severity", "value": "high" },
      { "name": "knowlcom:qready:recommendation",
        "value": "AES-256-GCM" } ]
  }]
}

Interface

Plain language at the keyboard.

One-click checks, plain-language reports and a guided migration plan. Available in 20 interface languages, including right-to-left Arabic and Urdu, designed to WCAG 2.2 AA, in dark and light themes.

Q-Ready home screen with a one-click check of the computer.
Start with one check.
Network discovery: an allow-list of TLS and SSH endpoints and the key exchange each one negotiated, including hybrid X25519MLKEM768.
Hybrid key exchange, detected per endpoint.
Cloud key-store connectors that read key metadata only, with secrets kept in the operating system keychain.
Cloud key stores, read as metadata only.

Deployment

From one laptop to a sovereign fleet.

Desktop, agent, command line and Console, on infrastructure you control.

  • Standalone desktop

    macOS, Windows and Linux (deb, rpm, AppImage).

  • On-premises and sovereign

    Headless agents, the command line and the Console on servers you control.

  • Air-gapped

    Agents export signed results for air-gapped import; signed bundles carry rule packs and updates in.

  • CI/CD

    The command line gates builds on findings and on policy.

  • Enterprise fleet

    Headless agents push hybrid-signed results to a self-hosted Console.

  • MSSP

    One multi-tenant Console for many client estates.

Enterprise and fleet

Privacy

Your evidence stays yours.

  • No telemetry.
  • Source code, file contents and private keys never leave the device.
  • Every network feature is opt-in, and secrets stay in the OS keychain.

Privacy and security

From plan to migration

Q-Ready plans. Your teams execute.

Knowlcom teams can take a signed-off plan through each wave.

  1. 01

    Inventory

    The cryptographic inventory and CBOM.

    Service Post-quantum audit

  2. 02

    Plan

    Couplings, waves and readiness gates from the planner.

    Service Advisory

  3. 03

    Migrate

    Each wave through your change management, with Knowlcom PQ products where they fit.

    Service PQC migration

  4. 04

    Keep current

    The policy gate keeps the estate on approved algorithms.

    Module Policy-as-code gate

Next step

Request a Q-Ready briefing.

See it on your own systems with a Knowlcom team.