Investigation intelligence for law enforcement.

Open a case from the initial report, work every lead with the whole file behind you, and hand the prosecutor a package that holds up.

The problem

The case is buried in its own evidence.

01

Too much to read

A serious case generates thousands of pages. No investigator can read all of it, let alone hold it in their head.

02

Scattered across sources

The evidence lives in different systems, formats and agencies, so the connection between two documents in two places never gets made.

03

The connection goes unseen

The link that breaks the case open, or the inconsistency a defense attorney will exploit, is usually already in the material. It just never surfaced.

One file at a time, against the whole case Top: a case as rows of pages held by different teams (lab, phones, video, financial), only a few read, with a link between a lab page and a financial page that never gets made. Bottom: the same case connected, as a web. Around an open outer ring sit the sources: call records, geofence, crypto, CCTV, plate reads, bank, interviews, body cam, tower dumps, DNA, latent prints and ballistics, with a gap for every other record in the file. Spokes run from each source to the people, phones, accounts, vehicles, places and items it names, and those are linked to each other. A blue thread runs from DNA on a casing to a person, their phone, a crypto wallet tied to it, the vehicle it paid for, and the scene. TODAY A case, read one file at a time. LAB PHONES VIDEO FINANCIAL READ NOT YET READ LINK NEVER MADE CASE The whole case, connected. + EVERY OTHER RECORD IN THE FILE CALL RECORDS GEOFENCE CRYPTO CCTV PLATE READ BANK INTERVIEW BODY CAM TOWER DUMP DNA LATENT PRINT BALLISTICS CASING PERSON PHONE WALLET VEHICLE SCENE
What CASE is

The whole case,
not just the part you can hold.

Anatomy of a case in CASE An isometric plate of one case in front of a blue circle. A dotted trail runs from a house to the scene, marked in blue; the scene is linked to a vehicle and to a document in the case file, stacked along the back of the plate. A ghosted branch leads to a person whose account rests on a source held aside. Callouts read: what happened, every source on one timeline; who's connected, people, phones, vehicles and places; what it supports, each claim tested against the file; and what if a source is set aside. A trace strip runs along the plate's edge. WHAT HAPPENED. Every source, on one timeline WHO'S CONNECTED. People, phones, vehicles, places WHAT IT SUPPORTS. Each claim tested against the file WHAT IF. A source is set aside TRACE Every entity, link and finding opens to the page it came from.
Anatomy of a case in CASE, compact An isometric plate of one case in front of a blue circle, with four numbered markers: 1 on the trail from a house to the scene, 2 at the scene, 3 at a document in the case file, and 4 at a person whose account rests on a source held aside. 1 2 3 4
  1. 1

    What happened.

    Every source, on one timeline.

  2. 2

    Who's connected.

    People, phones, vehicles, places.

  3. 3

    What it supports.

    Each claim tested against the file.

  4. 4

    What if.

    A source is set aside.

TraceEvery entity, link and finding opens to the page it came from.

The case, start to finish

From first lead to closing argument.

CASE isn't only where the evidence goes. It's where the case is run: opened from the initial report, worked lead by lead, and handed to the prosecutor in a package that stands up.

A newly assigned case: the initial report beside its suggested opening tasks
A newly assigned case: the initial report beside its suggested opening tasks
A newly assigned case: the initial report beside its suggested opening tasks

Use it on day one. Upload documents, phone returns, photos, video and spreadsheets as you go. When you're ready, CASE connects to your internal and third-party systems, so there's no waiting on an integration project to start.

Inspector

Ask the case.

Inspector is an AI assistant that works only from the material your team has approved. Ask a question in plain language and every answer cites the page it came from. Test a theory and it shows what the evidence supports, what conflicts with it, and what's missing.

Try asking
  • What contradicts the witness's timeline?
  • Which vehicles were seen near the scene?
  • Where was this phone between 9 pm and midnight?
InspectorApproved sources only

Who was in contact with 555-0142 on the night of the 14th?

Four numbers were in contact between 9:40 pm and 1:15 am. Two belong to known associates CDR 555-0142· p. 14. One is a prepaid line activated two days earlier Subscriber return· line 3.

The fourth number has no subscriber on file yet.

3 supported1 missing
Built for the team

Everyone who works the case,
in one place.

Investigators

Start from the initial report, approve the opening tasks, work leads in threads, and ask Inspector for answers that cite the file.

Analysts

Bring in documents and returns, check what was extracted, and work tower dumps, call records and pattern of life across every number.

Reviewers

Often the case agent, an analyst or a supervisor. Approve or deny each document with a note; only approved material feeds search, entities, the timeline and Inspector.

Supervisors

See every investigator's open and overdue work across cases, set roles and permissions, and keep the department's document templates.

Across the department

Every case you can see, and what needs you now.

  • Command center

    Your caseload at a glance, with a brief grounded in the case files and the work waiting on you.

  • Search all cases

    Find a name, phone or plate in any case in the department. Need-to-know still applies.

  • Team workload

    See where cases are stuck: open, overdue and blocked tasks for each investigator, so work can be rebalanced.

  • Templates

    Turn a warrant your court accepted into a template, then generate the next one from a case.

Trust

Every claim traces back to the evidence.

CASE doesn't generate conclusions. It structures, connects and surfaces what's already in the case material, and keeps the case clean while it does.

  • Reviewed

    A reviewer approves or denies each document before it counts, and the decision and its note are kept.

  • Source-linked

    Every entity, relationship, timeline event and finding cites the document or record it came from.

  • Need-to-know

    People reach a case because they're assigned to it, and each role can do only what an administrator allows.

  • Append-only

    Every change and review decision on a case is recorded in an audit trail that can't be edited.

  • Provenance kept

    Third-party records stay labelled. Every value shows whether it came from the case, an outside source, or both.

  • Verifiable

    Return packages carry their chain of custody and a SHA-256 manifest the prosecutor can check.

Under the hood

Infrastructure, not a chatbot.

Investigators see the case. Underneath it, CASE runs on Halō's engine: layers that turn raw material into source-linked output, with chain of custody, source linking and audit running through every one.

The CASE stack, in depth An isometric stack of three plates. At the bottom, sources: tiles for case files, phone returns, CCTV, lab results, messages, interviews and other material. In the middle, the engine: a dot grid where documents are read, reviewed and entities resolved. On top, the case: people, phones, vehicles, places and documents connected on one blue-edged plate, whose front edges carry the investigation framework and the custody controls. Above float four cards for the timeline, Inspector, entities and reports, each linked down to the case. A blue rule underneath reads chain of custody, source linking and audit across every layer. FRAMEWORK CUSTODY TIMELINE INSPECTOR ENTITIES REPORTS 04 INTERFACES AND OUTPUT Timeline, Inspector, entities, reports 03 THE CASE Who, what, where and when 02 ENGINE Read, reviewed and resolved 01 SOURCES Everything the case brings in CHAIN OF CUSTODY · SOURCE LINKING · AUDIT ACROSS EVERY LAYER
The CASE stack, compact An isometric stack of three plates with floating interface cards above, numbered 1 to 4 from the bottom: sources, the engine, the case in blue, and interfaces and output. FRAMEWORK CUSTODY TIMELINE INSPECTOR ENTITIES REPORTS 4 3 2 1
  1. 1

    Sources

    Everything the case brings in.

  2. 2

    Engine

    Read, reviewed and resolved.

  3. 3

    The case

    Who, what, where and when.

  4. 4

    Interfaces and output

    Timeline, Inspector, entities, reports.

Across every layerChain of custody, source linking and audit.

Built for the job

Not a blank canvas.
A tool that knows how a case works.

CASE starts from how a case actually works. It takes in the whole case, connects what's inside it, and reaches to known outside sources to widen the picture. The same structure holds across case types and grows to new ones without starting over.

Proof

Built with investigators, on real cases.

CASE is being built with the detectives and analysts who use it, on active cases in their precinct. What they need decides what gets built, from inside the work rather than from a team pitching to law enforcement.

That work has drawn attention from town, state and federal partners.

Evidence items and lab results, with match statistics

See CASE on a case like yours.

We'll walk your team through CASE on material that looks like your caseload, from the initial report to the package you hand the prosecutor.