KEEL SYSTEM
MONITORING ACTIVE
Assign route to Keel Agent: SHANGHAI → ROTTERDAM

The autonomous real-time supply chain disruption control agent.

An autonomous operations controller that keeps a production line running when suppliers fail — detecting disruption, challenging supplier claims against hard evidence, sourcing alternates, and escalating with a decision brief instead of an alert.

Go to App Watch the Simulation
The Thesis, In One Fact

Two companies. The same fire.
The same signal. A $2.34 billion difference.

Ericsson

Accepted the estimate. Philips said the Albuquerque plant would recover in about a week. Ericsson filed it, waited, and escalated three weeks later. Recovery actually took months.

Lost $2.34bn in its mobile phone division and exited handset manufacturing.

Nokia

Refused the estimate. Challenged the recovery figure, demanded specifics, escalated within days, put engineers on site and locked alternate capacity before the market knew.

Shipped through the quarter and took market share.

The difference was not information. Both had the same signal on the same day. The difference was whether anybody challenged a supplier's estimate against evidence, quantified the exposure, and escalated with a decision rather than an alert.

KEEL is the Nokia response, in software — applied to every part number, every day.

Part One · Research Context

What the research actually says.

We did not start from the brief. We started from the failure literature and the 2025–26 disruption record, and let the findings choose the problem worth solving.

Finding 1 · Where the time goes

Detection is solved. The 40 hours after are not.

8.7h
Time to detect
40.9h
Time to understand

The bottleneck is interpretation, not sensing. A buyer covering 200–400 part numbers cannot spend forty hours on one vague email.

Finding 2 · Alert Fatigue

Control towers failed at their actual job.

22%
Shippers call control towers effective

Visibility was built ahead of response capacity. Problems arrive faster than the organization can absorb them. It is a throughput problem, not a data problem.

Finding 3 · Adversarial Inputs

Three inputs a planner must treat as adversarial.

65%
Inaccuracy in ERP inventory records

Nothing checks ERP records, vague supplier emails, or invalid shipping labels. Verification exists only in the heads of experienced buyers.

Finding 4 · Mid-Market Gap

The mid-market runs on a workbook.

.XLSX
Is the actual system of record

No risk function, no planning suite, no integration budget. If the buyer's system is a spreadsheet, Keel reads/writes `.xlsx` as a first-class data source.

Read Research Literature
Live Demonstration

Watch Keel mitigate in real time

Click through the steps of an active supply chain disruption event. See how the agent perceives data discrepancy, ranks risks, challenges supplier claims, and executes costed allocations.

agent.keel.sh/simulate

01 · Perception Engine (Stock Reconciliation)

[Ingesting Workbook...]

• ERP stock register: 800 units

• Warehouse stock count: 390 units

• Reconciled consumption projection: 304 units

WARNING: ERP inventory figure is overstated.

Keel reconciles system records against physical realities, planning on the most pessimistic figure to prevent late line-down alerts.

02 · Risk Register & Prioritization

  • BATTERY CELL LFP-88 Stockout: 2.7 Days · Impact: LINE STOP
    🚨 CRITICAL RISK
  • COPPER CATHODE FOIL Stockout: 9.4 Days · Impact: None
    ✔ SECURE
  • SILICON WAFER H-1 Stockout: 14.2 Days · Impact: None
    ✔ SECURE

03 · Claim Verifier (Adversarial Checking)

SUPPLIER CLAIM CONTRADICTS TRACKING RECORD
SUPPLIER CLAIM
"The shipment has been dispatched and is on its way."
CARRIER AUDIT
Label generated, but no pickup has occurred.
ACTION: Refused supplier claim. Reliability score penalized. Sourcing alternate supply...

04 · Recovery Allocator & Cost of Delay

Option A: Split Allocation (Recommended)

Route 3,000 units via Air Cargo + 12,000 units via standard Ocean route.

Cost +$12,400
Coverage 0 Days Stop
Option B: Full Expedited Air Cargo

Route 15,000 units via priority air corridor (heavy freight surcharges apply).

Cost +$48,000
Coverage 0 Days Stop

05 · Escalation Brief & Append-Only Audit Trail

[ESCALATION] Cost exceeds authority threshold ($10k limit). Generating Decision Brief for Human approval.
15:42:01 Event [Detection] - Discrepancy logged for LFP-88.
15:42:03 Event [Reasoning] - Selected split alternative under cost of delay analysis.
15:42:05 Event [Action] - Drafted email to Shenzhen Supplier and booked Air space.
API Call dispatched to Maersk Shipping line (Vessel re-route instructions) ✔ SUCCESS
15:42:07 Allocating 5,000 units from SG-Buffer-04. Dispatching warehouse picking orders.
15:42:10 Resilience rating locked at 98.4%
Hash: 7b1c...19a8 MITIGATED
Part Three · Operations

Who uses Keel,
and how it runs the buyer's morning.

Keel takes a half-day of manual triage (reading vague emails, matching ERP cover, getting quotes) and completes it in minutes, showing its working at every step.

1. System Roles & Access

👤

Buyer / Planner

To know which parts threaten production and have the recovery already worked out.

Agent Console, Mail, ERP
🧾

The Approver

To decide in 60s, with costs, consequences, and alternatives in front of them.

Approval Inbox
🚚

The Supplier

To answer the buyer's query in their own words without downloading anything.

Supplier Portal Link
🔍

Auditor / Exec

To ask "why did we spend ₹1.5L?" and get a clear, verifiable savings counterfactual.

Audit Score, Prevented Screen
🛠

Ops Engineer

To point it at own data workbooks and see whether the reasoning survives reality.

Workbook Connect, Lab

2. The Primary Journey Timeline

01 · Pick Disruption Scenario

Choose the plant's opening position, pick a seed to randomise parameters, and hit Start.

02 · Watch the Agent Work (Agent Console)

Watch Keel reconcile stock ("ERP says 800, warehouse says 390"), refuse speculative vague replies, challenge tracking records, and reject uncertified suppliers.

03 · Human-in-the-Loop Approvals

When cost exceeds ₹1,50,000, Keel blocks automatically and asks for signature. A rejection reopens the risk register, forcing it to find a cheaper alternative.

04 · ERP PO Generation & Sync

Keel writes POs, flags untrusted items, updates stock limits, and exports the resolved network mapping to `.xlsx` files.

05 · Recompute Counterfactual Savings

Compares what a buyer working from standard ERP data would have spent on panic freight vs. what the agent spent by acting early.

06 · Audit Trail Logging

Every single detection, tool call, logic decision, and reasoning contradiction is logged into an immutable append-only JSON file.

Explore User Journey & Screens
Part Two · Core Engine

Eight Core Modules.
Built because of a documented failure mode.

Every module exists to solve a specific way traditional planning loops break down.

01 · Stock Reconciliation

ERP vs Physical Reality

Takes the ERP figure, the warehouse count, and consumption projections to plan on the most pessimistic figure.

Without it: Replenishment fires days late; lines stop.
02 · Commitment Parser

No Hedging Tolerated

A supplier's reply counts only if it contains a specific date, quantity, and zero speculative hedging language.

Without it: Speculative responses are logged as "acknowledged."
03 · Claim Verifier

Adversarial Cross-Checking

Verifies any supplier dispatch claim against carrier records. Keeps alternate sourcing active on contradiction.

Without it: False label generation halts backups.
04 · Risk Register

State Memory & Assumption Expiry

Keeps a live working memory of all active risks. Every risk carries its assumptions, each with a strict expiry.

Without it: Stale mitigation plans expire unnoticed.
05 · Recovery Allocator

Split-Source Sourcing Optimization

Applies quality gates first, then searches single-source, split, and staged options across available suppliers.

Without it: Quotes sorted by unit price overlook certification.
06 · Cost of Delay

Freight Cost vs Line-Down Penalties

Prices expedite rates directly against the cost of delay, including moving low-priority runs for zero cost.

Without it: Expediting becomes an expensive reflex.
07 · Escalation Brief

Human Handover Format

Compiles cost, overages, impact if approved/rejected, alternative list with reasons, and a decide-by time.

Without it: Vague approval requests stall for days.
08 · Supplier Memory

Historical Reliability Index

Attaches historic hedges and contradictions directly to the supplier scorecard, feeding allocation mathematics.

Without it: Deceptive suppliers score same as honest ones.
System Architecture Docs Worked Walkthrough Guide
Visual Narrative

Full Circle.

Three acts, one mitigation cycle. Watch how a shipment navigates a global disruption event from warning to landing.

KEEL LOOP · PHASE I · PERCEIVE & RANK
HAZARD VECTOR
304 Units
Reconciled · Usable stock cover
ACTIVE
800 Units
ERP Claim · Overstated stock
DISCREPANCY
Excluded
PO-7712 · Vague supplier reply
BLOCKED
PERCEPTION JOURNAL · PHASE I
status · ERP overstatement detected
usable stock · 304 units
daily usage · 112 units / day
time to stockout · 2.7 days (risk)
EXPEDITED AIR PHILIPS FAB KEEL AGENT ALTERNATE FAB INCUMBENT TRANSIT ASSEMBLY LINES
"Keel re-reads inventory sheets and identifies components threatening line stoppage by severity."
01 / 03
Playbook Explorer

Disruption Resolver Flow

Select a supply chain hazard to walk through the autonomous agent mitigation cycle step-by-step.

"Querying cargo line routes..."
You operator node
supplier
supplier node
carrier record
tracking info
mitigation plan
recovery options
You ask.
The Layer Underneath

How the commands will move between carriers.

The agents that dispatch the commands are freight forwarders, carriers, port controls, and buffer hubs, each operating inside their own systems. Keel builds the secure protocol layer that lets them hand routing amendments over without exposing their internal data. The ingestion pipeline runs today. The autonomous execution is next.

BOOTING 3D AIS GLOBAL TELEMETRY ENGINE...
SIMULATE LIVE NETWORK HAZARDS (AGENT TRIGGER)
System status: Telemetry operational. Active agent routing normal.
Clarifications

Integrations, Operations & Trust

Frequently asked questions about Keel integrations, rules, and deployment policies.

Keel offers direct API connectors for SAP and Oracle, but is also uniquely designed to treat spreadsheets (.xlsx) as a first-class data source. For mid-market plants running without a planning suite, Keel reads, writes, and syncs directly with workbooks, automatically replanning the moment any cell changes.
Yes, Keel enforces a hard, code-level Authority Threshold from the very first commit. Below your specified dollar limit, the agent executes and commits options automatically. Above the limit, execution is locked in code until a manager reviews and signs off on the generated Decision Brief.
Keel uses a provider-agnostic model adapter. If your data cannot leave the building, Keel can connect directly to OpenAI, Azure AI, or a locally self-hosted model running on your own network, ensuring absolute data security and governance compliance.
Keel is priced per site against the avoided loss it prevents, not per seat. We offer structured pilot packages for a single plant to prove the coverage arithmetic, followed by tier-based site subscriptions scaled by part count numbers and supplier volume.