Questions and answers

The questions that come up, answered as they are asked.

These are the real objections, in the words they arrive in. Where the answer is not the one you were hoping for, it is written that way on purpose.

What the software is

What does VERA actually do?

VERA is forensic analysis software for seized devices. It takes a raw Full File System extraction, builds the structure, and the examiner validates it. The examiner then asks the seal in plain language. Meaning-based search covers the text and what a picture shows. The assistant answers, and every statement is a click that opens the source row. It runs offline, on the workstation or on a server the service hosts.

It begins where acquisition ends. It does not extract devices and it does not replace the tool that does.

We already have Cellebrite or AXIOM. Why would we add this?

Most VERA users do have one, and they keep it. VERA works from the raw extraction rather than from their output, so it covers what your existing tool did not decode, including application versions that changed since its last release.

The two run alongside each other. Nothing is migrated and nothing is retired.

Does it need our acquisition suite to be installed, or licensed?

No. VERA reads the extraction directly. There is no upstream licence, no dongle and no companion installation, which also means you can read a seal that arrived from a service using a tool you do not own.

Which operating systems and devices does it cover?

VERA works on the raw extraction rather than on a device, so the question of which handset it supports does not really apply to it. Whatever your acquisition tool produced, from whatever operating system, is what VERA reads.

Coverage of the applications inside that extraction is the interesting question, and that is answered on the automatic coverage page.

Is it a cloud service?

The deployment we describe on this site runs on your infrastructure: models on the workstation or on a server your service hosts. No telemetry. When a workstation has a network, VERA confirms its licence key with us (the key's id, the workstation code and the version, never case data); without a network it works as usual.

A placement at VERA Forensics exists for organisations that decide not to run the models themselves. It is off by default, sends the text of an AI request, never the case files, and is paid from the account balance.

Coverage and mappings

So our examiners have to build these mappings themselves?

No. Known applications are mapped automatically on import. Anything unknown is mapped by the software itself, and the examiner reviews the result.

The visual editor exists so that your examiners keep full control and can correct anything, rather than because they are expected to do the work.

What happens when an application updates and the storage layout changes?

That is treated the same way as an application nobody has seen before, and it is far more common. VERA generates a new mapping for the changed structure and the examiner validates it. You are not waiting for someone else to notice the change and ship a fix.

Does our case data go into your library?

No. The library holds parsing definitions, which describe how to read a given application's data structure. It never holds evidence.

It is self-hosted on your infrastructure, and you decide who it is shared with, including nobody.

What if the generated mapping is wrong?

You see it before it is applied. What reaches the examiner is a preview over the real records rather than a specification to read, so a mapping that has misunderstood the source is usually obvious immediately.

The examiner corrects it in the visual editor or discards it. Nothing enters the case until a human accepts it.

Verification, AI and the courtroom

How do we know the AI is not inventing things?

You do not have to take its word for it. Every statement links to the exact file, table and row behind it, and one click puts you on the source.

The assistant proposes and your examiner decides. Nothing enters a report unverified.

Does VERA decide who is a suspect?

No. A signal says that a written trace looks like suspicious behavior, with a domain and a level, and shows the words behind it. It is a lead for the examiner, not a finding, and no signal enters a report on its own.

The optional AI review says whether the passage really looks suspicious, whether the words are ordinary, or whether it cannot tell, and its ruling is labelled as AI-generated. The examiner can set any signal aside, and the assistant says what it could not see.

How signals work
What about coded language in other languages, or a word used innocently?

The lexicon covers around fifty languages and recognises plurals, accents, stretched letters, disguised spellings and emojis. A common word such as “plug” or “snow” counts only beside a price, a quantity or another word of the same domain, and the AI review reads it in context before the level is kept.

It will still miss some suspicious behavior, and flag some innocent messages. That is why a flag is a lead, and why each one opens the message it comes from.

Is this admissible in court?

Admissibility rests on the examiner's verification of source data rather than on the tool. VERA is built so that verifying takes one click instead of an afternoon.

It does not replace the examiner's judgement. It makes exercising that judgement practical at scale.

What does the audit trail actually contain?

Every action the assistant takes and every result it receives is written to a log held inside your deployment. Records carry their provenance from ingestion through to display, and recovered records carry their recovery status, so a carved row is never presented as a live one.

Can the defence challenge a finding that came from the assistant?

They can challenge any finding, and they should be able to. What VERA provides is the material to answer with: the original record, its path, and the fact that an examiner verified it before it entered the report.

A finding that could not be traced back to a source record is not one we would want in a report either.

Security and sovereignty

We would need a security review.

We would expect one. The architecture makes it simpler than most: no telemetry, no vendor remote access, and no case data leaving your perimeter unless you choose hosted AI or translation. Apart from the licence check, which runs when the workstation has a network, VERA connects to outside services only when its VERA Internet connection is on (off by default). It then reaches the model downloads you start and the basemap, which is OpenStreetMap unless you choose the local map pack only. The one exception is the public library catalogue, which is read even with the connection off and carries no case data.

The questions that normally arrive in a review are answered in advance on the sovereignty page. We will answer whatever questionnaire you use, and anything not covered gets added to that page.

Can you access our deployment?

No. There is no remote support tunnel and no maintenance access: we cannot read, change or reach your cases. The one thing we can do is withdraw a licence key, and a workstation with a network then stops at its next licence check. That is also why deployment documentation matters: the system has to run without us because we cannot reach into it.

Which AI models does it use?

The models run on your own hardware and can be replaced by you. Naming the specific models publicly would be a level of detail no vendor in this category publishes, and it would date badly, because the point of the design is that a model can be swapped without touching the client.

In a technical evaluation under a confidentiality frame this is a reasonable question and it gets a straight answer.

Does it phone home for licensing?

Yes, when the workstation has a network, and only for the licence: VERA sends the key's id, the workstation code and its version, and learns whether the key is still valid. Never case data. A key is activated for one workstation, online or, without a network, with a code entered in your account. A workstation that never has a network runs on its key until the key's date.

The company, procurement and continuity

You are a small team.

Yes. That is why the deployment is fully documented, why the software runs without us, and why we are having this conversation with you rather than building a sales organisation.

If continuity is a concern, source escrow can go into the contract, along with a perpetual licence on the deployed version.

What happens if you disappear?

A fair question, and the honest answer has two halves. Contractually, source escrow and a perpetual licence on the deployed version are both available. Practically, a deployment that requires no internet connection and no vendor access does not stop working because the vendor did.

We cannot procure from a company this small.

Below the direct-award threshold there is no formal procedure required, which is exactly why we would propose a pilot at that scale rather than a large contract.

If your service has a supplier-size requirement that a pilot does not solve, tell us early. That is a real constraint and we would rather know it before either of us spends time.

Send us your pricing.

We can. It depends on the shape of the deployment, so it is a short conversation rather than a page on this site.

The structure is published: an annual licence per seat. An independent expert orders a seat online once approved; a service with several seats works under a contract, with pilot arrangements available. What we would suggest first is a pilot small enough that procurement is not the difficult part.

What support and training come with it?

Deployment support during installation, written documentation for the deployment, and a training session for the examiners who will use it. Support afterwards is direct with us, by email, without a ticketing layer in between.

We will not describe a twenty-four-hour support desk that does not exist. If your service requires one contractually, that is a real conversation to have before anything else.

How often does VERA change?

A new version usually ships every few days. Each one that changes something for the examiner is written up in plain language on the What's new page, with internal work left out.

Customers download the latest version from their account. A version already installed on an offline workstation keeps working as it is.

See what's new
What is coming next?

The roadmap lists what we are building, what comes next and what we are still studying, without dates. Everything on it is in development and described that way, on this site and in a demonstration.

The order moves with what services ask for. If your laboratory needs something that is not there, say so.

See the roadmap
Can we speak to an existing user?

That depends on what the deploying institution is willing to have said publicly, and we will not put words in their mouth on this website. Ask during the demonstration and we will tell you exactly where that stands at the time.

Something not answered here?

If your question is missing, write to us. The answer usually ends up on this page afterwards, which is a good reason to ask.

Write to VERA Forensics

See it running on a real extraction

A service asks for a demonstration, usually thirty minutes on fictitious data. An independent expert asks for access: a person reviews the request, then the yearly licence is ordered from the account.

Request access

Every request is reviewed before access is granted.