How it works
Connect. Answer. Act.
ForgeOrbis sits on top of the systems you already own. It connects their records into one shared vocabulary, answers in plain language with the record behind every claim, and carries an approved decision back into the system that owns it. Here is the whole path, entirely inside your perimeter.
The platform loop
Connect
Connectors read your systems in place: logs, incidents, tickets and owners today, with your other systems mapped during deployment. Their records become typed objects with links, so an incident knows its station, its ticket and its owner.
objects · links · one vocabulary
Answer
Ask in plain language. The Cognitive Kernel answers from the connected picture: an exact figure when it can count, a cited explanation when it must explain, and an honest refusal when the evidence is not there.
every claim cited to its record
Act
When the answer calls for a change, the Kernel proposes a typed action. Nothing runs until a person approves it. The Executor then writes it back to the system that owns it, through allow-listed connectors, and records it.
approved · governed · audited
Inside Log Intelligence
How a log question becomes a cited answer.
Logs are usually the first system connected, because they hold the ground truth of what happened. A month of them across thousands of folders, answered in a sentence.
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
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
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
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?”
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.
Read the full technical breakdown in two-engine routing.
Request a deployment
Put the connective layer inside your walls.
We scope which systems to connect first, size the hardware, and deploy ForgeOrbis with Orbis, our own fine-tuned model, in your environment. Your data never leaves your network.