Q-Ready · On-device AI

An AI security analyst that runs where your data lives.

Ask in plain language. Ask Q-Ready answers from your own scan, cites every source and explains what would need to change. It never makes the change.

Ask Q-Ready giving migration guidance for one finding: what would need to change, what it is coupled to and why its wave is not yet safe to start.

Grounded answers

Every answer traces back to evidence.

The detection engine decides what is found; the analyst explains it.

Your scan results and a local knowledge base feed read-only tools on your device; answers cite their sources, and change requests return migration guidance. Your scan results Local knowledge base Read-only toolson your device Answer, with sources Migration guidance deterministic engine = source of truth · grounding check · no cloud AI calls
  • The local knowledge base covers NIST FIPS 203, 204 and 205, SP 800-208, IR 8547, CNSA 2.0, CERT-In CBOM guidance, the EU and UK roadmaps and an offline advisory feed.
  • Inline citations open the exact excerpt; a grounding indicator shows how well each answer is supported.
  • The grounding check tests attribution, not truth. Recommendations remain for your teams to validate.

What it can do

Read-only tools. Navigation-only actions.

Questions are routed to tools over the real scan. None of them writes a file, runs a command or opens a connection.

  1. 01

    Summarise and query

    Results, inventory and finding explanations over your real scan.

  2. 02

    Assess risk

    Mosca timeline, exposure and crypto-agility for any asset or host.

  3. 03

    Explain the plan

    Which wave an item belongs to, what blocks it and what it must change with.

  4. 04

    Find evidence

    Which evidence supports a control, across the 19 evidence packs.

  5. 05

    Suggest next steps

    Open a plan item, the scan picker or network discovery. Each action only navigates.

Ask Q-Ready declining a request to apply fixes and delete old keys, and explaining that changes belong in a coordinated migration plan.
Asked to apply all fixes, Q-Ready explains why changes belong in the plan.

Read-only by design

Change requests get guidance, not patches.

Q-Ready audits and plans. It never changes code, configuration, keys or systems. Ask it to patch a configuration, open a pull request or apply every fix, and it explains what would need to change, what that change is coupled to and which wave it belongs to.

  • No patch, diff or pull-request generation, and no configuration rewrites.
  • No tool can write a file, start a process, open a network connection or call a vendor API.
  • These properties are enforced in code and covered by automated tests, not only by prompting.

Prompt-injection defence

Scanned content is data, never instructions.

File names, code comments, certificate subjects, SSH banners and package metadata can all carry text that reads like an instruction.

  • Withheld, not followed

    Instruction-like text in tool output is withheld, and the answer says when this happened.

  • Fenced evidence

    Evidence is passed in fenced source blocks that are treated as data.

  • Refused up front

    Requests to reveal secrets, send results elsewhere or bypass policy are refused before any tool runs.

Backends

Choose how answers are written.

Facts always come from the deterministic engine, whichever backend writes the answer.

  • Core, built in

    The default. Deterministic and extractive: it quotes engine evidence and knowledge passages, with no model download.

  • Local model

    GGUF weights run in-process, loaded only from a bundle signed by a key you trust. No weights ship with the app or download automatically.

  • Local server

    llama-server or Ollama on a loopback address only. Remote addresses are refused.

Offline

Air-gapped, and still current.

The knowledge base is embedded in the app and the advisory feed is offline. Rule packs, policies and models arrive as signed bundles.

Deterministic first. Findings, scores and policy results come from the detection engine. The analyst explains them; it cannot create, delete or alter a finding.

Next step

Request a Q-Ready briefing.

See the analyst work on your own evidence.