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

Compliance for
Isolated Environments.

For defence, government and financial entities whose data cannot leave. Qgentic runs as a standalone executable on your infrastructure — no external connections, no telemetry, no accounts elsewhere. Verifiable regulatory evidence, generated entirely inside your network.

Contact Sales View Demo

Features identical functionality to the cloud edition, strictly restricted to local networks.

Target Organisations

Supported Sectors

Defence Contractors

Supports strict contractual isolation requirements. Compliance data processing remains entirely within secure enclaves.

Public Sector

Meets strict data-handling classifications by eliminating third-party data processing dependencies.

Financial Institutions

Ensures compliance with stringent data residency regulations. The localised architecture eliminates third-party sub-processors, simplifying vendor risk assessments.

Evaluating the air-gapped system shifts vendor risk assessment from auditing cloud infrastructure to verifying a local artifact via published hashes, SBOMs, and internal network monitoring.

System Architecture

Security and Isolation Controls

The air-gapped edition prevents network access via hardcoded mechanisms rather than configurable settings — isolation your own team can verify.

1 · Blocked Egress

Active Egress Guard

When initialised in air-gapped mode, an internal egress guard blocks all outbound requests except configured internal data feeds. Denied requests are logged to an audit chain. The allowlist is logged on startup for security validation.

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

Local Verification

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

3 · Zero API Dependencies

Deterministic Execution

The system forces deterministic processing paths, bypassing external APIs. Core validation logic—including identifier checks and cross-template rules—runs entirely on your infrastructure, with no network in the loop.

4 · Independent Audit Trails

Local Cryptographic Verification

Operations are recorded in a SHA-256 hash chain. This provides tamper-evident logs that auditors can verify independently without external services or vendor access.

Releases include published SHA-256 checksums to support independent binary verification during internal deployment.

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

Available Regulatory Packages

The air-gapped version supports all standard compliance modules. An additional regulatory regime arrives as a licence-file update — no new software deployment.

EU DORA (Register of Information)

Validates ICT arrangements against official templates, supporting ISO 17442 LEI checksums. Exports are cryptographically hashed. DORA →

UK Operational Resilience

Tracks business services, impact tolerances, and third-party dependencies. Automates tolerance breach calculations. OpRes →

EU AI Act & UK AI Governance

Maintains AI system registers, computes risk classifications, and manages Annex IV and Annex VIII documentation. AI Act →

HMRC Making Tax Digital (MTD)

Prepares and validates VAT and Income Tax returns offline. Note: Final HMRC submission requires moving the prepared return to an internet-connected system. MTD →

Deployment Process

Implementation Phases

  1. Initial EvaluationThe executable can be tested on local infrastructure using synthetic data, requiring no external accounts or installations.
  2. Configuration WorkshopSystem metadata sources and formats are mapped, and security verification protocols are defined.
  3. Transfer & VerificationThe application binary and SHA-256 signatures are provided for internal transfer and validation.
  4. Licence ProvisioningAn Ed25519-signed licence file is delivered, authorising use without external network dependencies.
  5. Initial ExecutionThe system is run internally to validate local data ingestion, processing rules, export functions, and network isolation controls.
  6. Standard OperationsSystem runs are integrated with internal scheduling tools. Application updates are delivered as full binary replacements with updated signatures.

How every edition ships and updates — signed artifacts, pinned digests, and the pre-answered IT change request — is documented on the deployment & 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 console 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 console 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 console, the approval, the audit chains — runs on your own machines, and the evidence bundle re-verifies with no Qgentic service running at all.

Network teams are encouraged to monitor the system to independently verify complete network isolation during operation.

Approval Controls

Mandatory Authorisation Requirements

Security Control

Mandatory Human Approval

The system compiles and validates data automatically but requires explicit human authorisation for all final exports. Approvals are cryptographically bound to the user and recorded in the audit trail. Automatic approval is unsupported by design.

This control ties every compliance output to a named, recorded approval.

Pricing Structure

Fixed Capacity Tiers

The air-gapped edition licenses flat, annually, by agreed capacity tier — an isolated network has nothing to meter.

Qgentic OpRes (Air-Gapped)

from £95K /year

Isolated UK operational resilience solution.

Qgentic AI Act (Air-Gapped)

from £95K / €105K /year

Secure EU/UK AI governance modules.

Qgentic DORA (Air-Gapped)

from £110K / €120K /year

End-to-end Register of Information, managed entirely internally.

Further details are available on the pricing page.

FAQ

Frequently Asked Questions

What defines the air-gapped deployment?

The system is hard-coded to refuse all outbound connections and omits telemetry or external activation services. Network isolation is enforced via application architecture.

How is licensing managed offline?

License entitlement is verified locally via an Ed25519-signed file against a compiled public key.

Are AI-assisted features available?

Cloud-based unstructured document parsing is disabled. Validation, compliance logic, and deterministic calculations run entirely on your infrastructure.

How are submissions handled?

The air-gapped system acts as a preparation and validation layer. Prepared reports must be transferred to a connected system for final external submission.

How can security teams audit the software?

Verification is supported via published SHA-256 hashes, egress-guard allowlists, local cryptographic audit logs, and SBOM documentation.

How is usage metered?

Licenses are bound to fixed annual capacity tiers. Internal usage logs can be exported for auditing if requested.

What are the business continuity safeguards?

Software functionality and local verification do not depend on external services. Source code escrow is available upon request.

Demonstration Binary Available. Security architectures can evaluate the isolated executable directly. Contact sales to request a sample.