Q-Ready · Enterprise and fleet

One inventory across the whole estate.

A self-hosted Console for a fleet of headless agents, with role-based access, single sign-on, separation of duties and a tamper-evident audit log.

Q-Ready Console fleet overview: hosts, Q-Readiness, assets at risk, a cited fleet summary and results by site.

Console and fleet agents

See every host. Drill into any one.

Fleet overview, hosts with signature provenance, inventory, risk, plan and compliance, and Ask Q-Ready across the fleet.

Headless agents on servers, workstations, pipelines and air-gapped sites send hybrid-signed results to a self-hosted Console, which exports to SIEM, ticketing and a REST API.ServersWorkstationsCI pipelinesAir-gapped siteConsoleself-hostedSIEMTicketingREST APIagents · console · hybrid-signed result bundles
Console host list with Q-Readiness, findings and last-seen time for each enrolled agent.
Every enrolled host, with its Q-Readiness and findings.

Agents

Results you can verify, from every site.

  • One-time enrolment

    Agents enrol with one-time tokens; the Console pins each agent’s hybrid public key.

  • Hybrid-signed results

    Results are signed with Ed25519 and ML-DSA-65. Replayed or tampered bundles are rejected.

  • Air-gapped import

    Agents push over HTTPS, or export a file for air-gapped import.

  • Desktop enrolment

    The desktop app can enrol with a Console and push signed results after consent for each push.

Access

Built for separation of duties.

Five roles in the Console:

  • Viewer
  • Analyst
  • Approver
  • Auditor
  • Admin
  • Single sign-on

    OIDC, with ID tokens verified against a local key set.

  • Second-person decisions

    Plan sign-offs, risk exceptions and policy changes are decided by a second person. Decisions are records; nothing is executed.

  • Tamper-evident audit log

    A SHA-256 hash chain with a verify endpoint, and signed evidence export.

Integrations

Findings where your teams already work.

Q-Ready integrations
AreaSupported
SIEMsyslog, Splunk HEC
WebhooksHMAC-signed webhooks
TicketingJira, ServiceNow
Threat intelligenceSTIX 2.1
CI/CDGating through the command line
AutomationREST API, described in OpenAPI

Integration support does not imply endorsement by, or partnership with, the vendors named.

Policy as code

Decide the algorithms. Gate every build.

Define allowed and forbidden algorithms once. The policy gate checks them in CI and across the fleet, so new code cannot reintroduce what migration removed.

CI stepexample
$ qready scan . --quick --fail-on high
# exit code 3 if a high or critical finding is present

$ qready policy check result.json
# exit code 3 when a blocking rule fires

Deployment

Your infrastructure, your boundary.

Agents, the command line and the Console run 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.

Managed providers. The MSSP Console runs many client estates from one multi-tenant deployment.

Next step

Request a Q-Ready briefing.

Plan a fleet roll-out with a Knowlcom team.