Alongside your tools

Nothing has to be replaced.

Most VERA users hold a licence for a major acquisition suite, and they keep using it. VERA is not a competitor to the tool that extracts the device. It is what happens to the extraction afterwards.

  • No upstream licence required
  • Reads extractions from tools you do not own
  • Runs entirely on your own hardware

The division of labour

Two jobs, and they are genuinely different jobs.

Acquisition and analysis are separate problems that happen to have been sold together. Extracting a locked device is difficult, specialised engineering, and the companies that do it well are good at it. Making sense of the result is a different problem, and it is the one that has scaled badly as extractions have grown.

Your acquisition suite

Handles the physical and logical acquisition, deals with locks and encryption, and produces the raw file tree. That work stays exactly where it is, with the tool your examiners already know.

Unchanged

VERA

Takes that raw file tree and builds structure for everything in it, including the applications and versions no tool decoded, then makes the result searchable and questionable offline.

Offline

What changes

The gaps stop being permanent.

  • Unsupported applications

    An application your acquisition suite has not implemented is no longer invisible. VERA generates the mapping and your examiner validates it, in the time the case allows rather than in the time a release cycle allows.

  • Versions that moved

    A supported application whose storage layout changed after the last release is the same problem as an unsupported one, and it is far more common. It is handled the same way.

  • Extractions from tools you do not own

    A seal that arrives from another force, another country or a partner service can be read without acquiring a licence for whatever produced it.

Honest boundaries

What VERA does not do.

The fastest way to waste your time would be to leave you to discover this in a demonstration.

VERA does not

  • Extract a device. It has no acquisition capability of any kind.
  • Bypass a lock, a passcode or device encryption.
  • Replace your acquisition suite, your case management system or your laboratory information system.
  • Intercept live communications or collect anything from a network.

VERA does

  • Read the extraction your acquisition tool produced, whatever produced it.
  • Build structure for sources no tool has implemented, with human validation.
  • Make an entire seal searchable by keyword and by meaning.
  • Answer questions with the exact source record attached.

The questions that follow

What a technical evaluator asks next.

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

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.

Cellebrite already has an AI assistant.

They do, and it is cloud-hosted. If your service can place seized-device data in a third-party cloud, that is a real option worth considering on its merits.

If it cannot, VERA runs on your infrastructure and nothing leaves it. That is usually where the conversation lands.

Does VERA need our acquisition suite to be installed?

No. VERA reads the extraction directly and requires no upstream licence, no dongle and no companion installation.

Can we use it on extractions we received from another service?

Yes. That is one of the more common reasons a laboratory tries it. A seal that arrives from a partner service can be read without acquiring a licence for whatever tool produced it.

Do our examiners have to learn a second tool?

They learn a workspace rather than a syntax. The parts that matter, a conversation view, a gallery, a map and a search bar, look like what they already are.

The one genuinely new concept is the validation step on a generated mapping, and that is a review task rather than a construction task.

See it running on a real extraction

Thirty minutes, on fictitious data, with time for your questions. If VERA does not fit what your service needs, that is a useful answer too.

Every request is reviewed before access is granted.