NERVE is live across local, private and approved-cloud deployments. Book an evaluation
Commercial model
Licensed by scope. Agreed at evaluation.
NERVE is licensed to organisations with a mandate to hold and search the material they acquire. Scope follows your source families, your deployment profile and your governance surface, and all of it is written down before anything is signed.
Available now
Eligibility
Licensed to organisations with a mandate to use it.
NERVE holds material that is governed, attributable and often protectively marked. Licensing is restricted to organisations that already carry the authority to acquire and retain it.
01
Government
Departments and agencies that hold approved source material under national handling rules and need it searchable without losing the acquisition record.
02
Law enforcement
Forces and units handling device exports, disclosure obligations and material whose provenance has to survive scrutiny long after the search that found it.
03
Private intelligence
Consultancies and corporate teams that have to show a client exactly which source a finding came from, and keep that reference stable across reprocessing.
Licence options
Three options. One licence model.
The licence follows the deployment profile you choose. Scope, term, support hours and renewal are agreed in writing with your organisation before deployment. Nothing is bought through this website.
Local
Compact local
Licence
On request
Signed local components on hardware you own
Offline policy, with an air-gapped profile available
Local vectorisation only, no external endpoint
Your custody of identity, keys and backups
Signed, verifiable upgrade packages
Handling labels from OFFICIAL upwards
Private
Scale-out private
Licence
On request
The same components on infrastructure you operate
Offline or online policy, your choice
Processing and search tiers scale independently
Approved connectors and gateways only
Separate development, staging and live environments
Your custody of keys, certificates and secrets
Cloud
Approved cloud
Licence
On request
AIC-operated Microsoft Azure, UK South
Separate development, staging and production
Signed release manifests for every service role
Policy-controlled connectivity under a handling ceiling
Certificates, backups and upgrades run by AIC
Acceptance criteria agreed per environment
What is included
The product does not change with the profile.
Scope rows differ because the environment differs. The pipeline, the canonical model and the evidence contract are the same in all three.
Compact local
Scale-out private
Approved cloud
Scope
Hosting
Hardware you own
Infrastructure you operate
AIC-operated Azure, UK South
Connectivity policy
Offline or online
Offline or online
Online, policy-controlled
Vectorisation
Local only
Local or approved endpoint
Approved endpoint or local
Air-gapped profile
Available
On request
Not applicable
Pipeline
Byte-exact original retention
Included
Included
Included
Canonical common model
Included
Included
Included
Full-text, structured, time and geospatial indexes
Included
Included
Included
Policy-approved vector index
Optional
Optional
Optional
Search API and Explorer
Included
Included
Included
Assurance
Acquisition and transformation lineage
Included
Included
Included
Exact locator citations
Included
Included
Included
Per-item partial-job reporting
Included
Included
Included
Signed release manifests
Included
Included
Included
Deployment and access
Identity and permissions
Your directory
Your directory
Your directory
Handling labels, compartments and caveats
Included
Included
Included
Keys, certificates and backup custody
Yours
Yours
AIC, under agreement
Upgrades
You apply
You apply
Run by AIC
Licence scope, term, support hours and renewal are confirmed in a written quotation. Figures are not published here because they depend on the source families in use, the retained volume and the environment the profile runs in.
Agreement
Written down before anything is signed.
An evaluation runs NERVE against a representative slice of your own material. Five things come out of it, and they become the terms.
01
Acceptance criteria
What has to be true for the deployment to be accepted, expressed against your own sources rather than a generic checklist.
02
Measures
Which measures are recorded during evaluation, including hash recovery, canonical mapping coverage, citation resolution after reprocessing and source-to-search time on your hardware.
03
Environment and responsibilities
Which profile runs where, who holds keys, certificates and backups, and which operational duties sit with AIC and which sit with you.
04
Handling and data rules
Datasets, handling labels, compartments and caveats, and the authority model applied to search responses and the Search API.
05
Term, support and exit
Licence scope and term, support hours, renewal, and the decommissioning and data-return arrangements that apply at the end of it.
Boundaries
What is not on this page, and why.
No list price
A figure that ignores your source families, retained volume and environment would be wrong by the time you read it. Scope is quoted in writing instead.
No feature tiers
The product is the same in all three profiles. We do not withhold indexes, provenance or the Search API to create a higher tier.
No service-level figures
Availability and throughput depend on the hardware and network the profile runs on. Those are measured during evaluation in your environment, then committed to in the agreement.
Next step
Get a quotation that matches your holdings.
Tell us which source families matter, roughly what you hold and where it has to run. We will scope an evaluation around them and quote against the result.