Skip to content
Focient

Empty corridor at night, by Nino Souza on Pexels (Pexels License).

National security · 19:40

A case, from first look to last entry

Watching recordings until the detail turns up.

The case holds a timeline across cameras, annotations and a relationship map of what was seen together.

An example case detail panel for case 0142, Loading dock, after hours: its status, priority and the time it was opened, and three evidence items. The four links to the timeline, graph, reports and activity are inert. The data is fictional.

Screens on this page show fictional data.

Empty corridor at night, by Nino Souza on Pexels (Pexels License).

At 21:15

Who is on the case

Cases have owner, editor and viewer roles.

Only its members can see a case, and each time an administrator opens one without being a member, that access is audited.

The team panel of the example case, Loading dock, after hours: three members, each shown by a fictional handle and a role, owner, editor or viewer. The data is fictional.

Empty corridor at night, by Nino Souza on Pexels (Pexels License).

At 22:30

The snapshot, checked again

Snapshots are hashed as they are captured, and the hash can be checked again from any citation.

An example Ask answer with one citation under Sources: the snapshot of the side door at the loading dock, its camera and time, its headline and a Verified chip. The data is fictional.

Empty corridor at night, by Nino Souza on Pexels (Pexels License).

At 23:50

What changed, and when

Written up at the end of the shift, from memory.

A case's activity log lists changes to the case, its evidence, its members and its briefings, each with its time.

The activity log of the example case, Loading dock, after hours: six changes, newest first, each with its label and its time. They are a briefing generated, a member added, three evidence items linked and the case created. The data is fictional.

Access, audit and retention

Your organisation's audit log can be read by its administrators and its auditors.

The audit log of an example organisation: four administrative actions, newest first, each with how long ago it happened, what it was and who did it. They are a change of role, a change to the organisation's settings (its retention), an invitation and an earlier change of role. The data is fictional.
  • Data kept apart

    Your organisation's data is kept apart from every other organisation's, in the database itself.

  • Retention

    The retention period of your organisation is set by an administrator.

  • Hashed late

    An image that was hashed only after capture is labelled as such.

How data stays apart

From timeline to briefing

Briefings are drafted for an analyst to review and can be exported as Markdown.

A case's Timeline screen: the dock door opens and closes, and a white van stops at the gate, each with its time, camera and snapshot. The data is fictional.
The same case's Reports screen, with one briefing. The data is fictional.
  • One snapshot

    The case timeline shows the same snapshot of the exact frame the vision model judged.

  • Baselines

    Each camera has its own baseline by day of week and hour, and deviations are flagged once it has enough history.

  • Ranked matches

    Matches are ranked by how closely they fit your question, and none is shown as a percentage.

How reports are built

Questions reviewers ask

Can we check that a snapshot has not changed?

A "Verified" chip on a citation re-checks the hash.

Can an administrator open any case?

An administrator can break glass into a case. Every break-glass is audited.

Who sets the retention period?

An administrator sets the retention period.

Who answers our deployment questions?

In the first conversation, under NDA, we answer your questions about deployment, networks and data flow.

Talk to us about your casework

Tell us how your analysts open and review cases.

Request a demo

Briefings are held under NDA.