QgenticQgentic
Qgentic / editions / air-gapped
Qgentic air-gapped · isolated networks

Compliance software for networks with no internet.

For defence, government and financial entities whose data cannot leave. Qgentic runs as a standalone executable on your own infrastructure, with no external connections, no telemetry and no accounts anywhere else, and it generates verifiable regulatory evidence entirely inside your network.

Who it is for

Defence contractors

For contracts that demand isolation: compliance data is processed entirely inside your secure enclave.

Public sector

No third party processes the data, so data-handling classifications stay inside your own controls.

Financial institutions

The data stays on your premises and there are no sub-processors, which keeps data residency simple and the vendor risk assessment short.

Vendor risk assessment becomes the verification of a local artefact, using published hashes, an SBOM and your own network monitoring, where it would otherwise be an audit of someone's cloud.

How the isolation works

Network access is blocked in code, with no setting that turns it back on, and your own team can verify the isolation.

Egress

An active egress guard

In air-gapped mode an internal egress guard blocks every outbound request except your configured internal data feeds. Each denied request is logged to an audit chain, and the allowlist is logged at start-up so security can check it.

$env:QGENTIC_AIRGAPPED = "1" # offline engine + egress guard armed
Licensing

Licences verified locally

Software entitlement is an Ed25519-signed licence file verified against a compiled public key. No activation servers, no heartbeat checks.

No external APIs

Deterministic execution

Processing takes deterministic paths and calls no external API. The validation logic, including identifier checks and cross-template rules, runs entirely on your infrastructure, with no network in the loop.

Audit trail

Evidence you verify yourself

Every operation is recorded in a SHA-256 hash chain: a tamper-evident log auditors can verify themselves, with no external service and no access from us.

Every release comes with a published SHA-256 checksum, so you verify the binary yourself before it goes in.

Get-FileHash .\qgentic.exe # matches the published SHA-256

Every module, offline

The air-gapped edition runs every standard module. Adding a regime is a licence-file update, with no new software to deploy.

EU DORA (Register of Information)

Validates ICT arrangements against the official templates, with ISO 17442 LEI checksums, and hashes every export. See the DORA platform.

UK operational resilience

Tracks business services, impact tolerances and third-party dependencies, and computes every tolerance breach. See the OpRes platform.

EU AI Act & UK AI governance

Keeps the AI system register, computes risk classifications and manages Annex IV and Annex VIII documentation. See the AI Act platform.

HMRC Making Tax Digital (MTD)

Prepares and validates VAT and Income Tax returns offline. The final HMRC submission is made from an internet-connected system, once the prepared return is moved there. See the MTD platform.

From evaluation to running

  1. EvaluationTest the executable on your own infrastructure with synthetic data, with no accounts and nothing else to install.
  2. Configuration workshopYour data sources and formats are mapped, and the way security will verify the build is agreed.
  3. Transfer and verificationYou receive the binary and its SHA-256 checksum, transfer it in and verify it.
  4. LicenceAn Ed25519-signed licence file authorises use, with no external network dependency.
  5. First runA first internal run checks data intake, the processing rules, the exports and the network isolation controls.
  6. RunningRuns are scheduled with your internal tools, and each update arrives as a full replacement binary with updated signatures.

How every edition ships and updates (signed artefacts, pinned digests and the pre-answered IT change request) is set out on the deployment and updates page.

What crosses the air gap, and what never does Two things cross into your isolated network, once and by hand: the signed binary, whose SHA-256 you verify yourself, and an Ed25519-signed licence file checked offline against a public key embedded in the binary. Everything else runs inside: the engine that reads, validates and assembles the filing; the dashboard on localhost with your own people and roles; and the approval gate where a named person signs every run onto the audit chain. There is no DNS, no egress, no telemetry, no account and no phone home, which a packet capture taken during a run will confirm. Two things cross back out, also by hand: the filing package in the regulator's own file names, and the evidence bundle of audit chains and the run report, re-verifiable offline with no Qgentic service running. § IN, ONCE § YOUR ISOLATED NETWORK § OUT, BY HAND The binary qgentic.exe SHA-256 published yours to verify The licence *.qgentic file Ed25519 signature checked offline EVERYTHING BELOW RUNS ON YOUR OWN MACHINES The engine reads · validates assembles the filing byte-for-byte the rules the SaaS runs The dashboard on localhost your people, your roles no account with us, none to lose The gate a named person approves every run recorded on the chain, inside your walls NO DNS · NO EGRESS · NO TELEMETRY · NO ACCOUNT · NO PHONE HOME Point a packet capture at it during a run: that is the test we ask network teams to make. Filing package the regulator's own file names manifest.json Evidence bundle audit chains run report verify it offline A licence check is arithmetic on a signed date: the public key ships inside the binary and the private key stays with us.
The interesting question about an air-gapped product is what crosses the line. Two things go in, once, and both are things you can verify yourself; two things come back out, carried by hand. Everything between them (the rules, the dashboard, the approval, the audit chains) runs on your own machines, and the evidence bundle re-verifies with no Qgentic service running at all.

A named person approves every export

Control

Approval is always a person's

The data is compiled and validated automatically, and every final export waits for a person to authorise it. The approval is cryptographically bound to that user and recorded in the audit trail. Automatic approval is not supported, by design.

What it costs

The air-gapped edition is licensed flat, annually, by agreed capacity tier, since an isolated network has nothing to meter. Sealed Site is the entry rung: one pack, one site and bounded capacity, at a number a department can sign off without the board.

Sealed Site, any pack

£24K / €28K /year, entry tier

One pack, one site, up to 250 arrangements, third parties or governed systems. Same sealed binary, same offline entitlement key, same update cadence as every tier above it.

Qgentic OpRes, air-gapped

from £95K /year, capacity tier

UK operational resilience on an isolated network.

Qgentic AI Act, air-gapped

from £95K / €105K /year, capacity tier

The EU AI Act and UK AI governance modules, isolated.

Qgentic DORA, air-gapped

from £110K / €120K /year, capacity tier

The full Register of Information, run entirely inside your network.

Every edition's price is on the pricing page. Security teams can test the isolated executable before anything is bought: ask for an evaluation build.

Frequently asked questions

What makes it air-gapped?

It is built to refuse every outbound connection, and it has no telemetry and no external activation service. The isolation is part of the application's architecture.

How is licensing managed offline?

Locally: an Ed25519-signed licence file is checked against a public key compiled into the binary.

Are AI-assisted features available?

Cloud-based document parsing is switched off. Validation, compliance logic and the deterministic calculations run entirely on your infrastructure.

How are submissions handled?

It prepares and validates. The finished reports are moved to a connected system for the final submission.

How can security teams audit the software?

Through the published SHA-256 hashes, the egress-guard allowlist, the local cryptographic audit logs and the SBOM.

How is usage metered?

Licences are fixed annual capacity tiers, so nothing is metered. Internal usage logs can be exported for an audit on request.

What are the business continuity safeguards?

Nothing in the software or its verification depends on an external service, and source code escrow is available on request.

Air-gapped guides