How it works

One question. One cited answer.

A month of logs across thousands of folders, answered in a sentence, with the exact file, line, and match score behind every claim. Here is the whole path, entirely inside your perimeter.

01

Ingest & structure

Point Orbis at your log folder path. It parses date and process branches, extracts a stable template per line, deduplicates, and builds a private index in place, inside your network.

4.1M events · 1,042 templates · 71% dedup

02

Ask in plain language

Type the question an auditor would ask. A router classifies it: counting questions go to the exact engine, explanatory questions to the grounded engine.

router: STRUCTURED · SEMANTIC

03

Get cited, scored answers

Every answer carries its evidence: file, line, timestamp, and a match score, so anyone can verify it. Nothing is generated without a citation.

match 0.94 · confidence high

The path of a question

Parse line → template
Index in place
Route: exact vs grounded
Retrieve / query
Verify citations
Stream cited answer

Two-engine routing

Exact when it can be exact. Grounded when it must explain.

The router sends counting questions to a precise counting engine and explanatory questions to a grounded, cited engine.

Tier 0 · exact

exact · verifiable

“how many labels did STATION_A1 print on 2026-07-10?”

count · labelsstation STATION_A12026-07-10
labels_printedrows
3,4121

Counted directly from the logs Orbis indexed. Exact and repeatable, never generated.

Tier 1 · grounded

cited evidence

“why did LabelRun stop printing around 14:20 on 2026-07-09?”

The printservice service lost its print queue connection at 14:22, retried three times, and recovered when the watchdog restarted it at 14:24.

…/STATION_A1/print.log:882140.94

Read the full technical breakdown in two-engine routing.

Request a deployment

Put an auditor-grade answer engine inside your walls.

We scope your log tree, size the hardware, and deploy Orbis in your environment. Nothing leaves your network, including this conversation.