Exposure model
Structures suppliers, sites, routes, systems, materials, and customer commitments as an operating network.
Caracal is an operational risk intelligence software platform. It models potential disruptions against company-specific suppliers, sites, routes, systems, and customer commitments. It then monitors risk signals continuously and recommends mitigation strategies when exposure changes.
Product architecture
Map potential disruptions before they occur. Monitor emerging risks continuously. Act with exposure-linked mitigation strategies.
Structures suppliers, sites, routes, systems, materials, and customer commitments as an operating network.
Collects and groups relevant external signals from approved public, commercial, and client sources.
Separates confirmed relationships from inferred ones, then scores timing, proximity, criticality, and confidence.
Produces exposure briefs, mitigation strategies, verification tasks, alerts, and integration events for the correct owner.
Inputs
Outputs
Integrations
Start
CSV, spreadsheet, and JSON intake for a focused pilot.
Connect
Scoped connectors for ERP, TMS, procurement, supplier-risk, continuity, ticketing, and BI systems.
Deliver
Email, webhook, JSON export, dashboard, and client-defined operating handoffs.
User workflows
Question: Which suppliers, lanes, and orders are exposed?
Decision: Verify stock, reroute, buffer, or escalate.
Question: Which direct or tier-2 relationship needs validation?
Decision: Contact the supplier, qualify an alternative, or revise terms.
Question: Which site, line, or customer promise can be affected?
Decision: Resequence work, activate continuity actions, or notify leaders.
Question: What is confirmed, inferred, or still uncertain?
Decision: Request evidence, start formal review, or maintain monitoring.
Evidence controls
A decision brief is not complete when it shows only a score. It must show where the evidence came from, how current it is, what is confirmed, and what could change the assessment.
Direct link to the official notice, dataset, or approved source record.
Publication time and the most recent time Caracal checked the source.
Primary official, primary operational, established secondary, or unverified signal.
Confirmed, inferred, or unknown. The output does not present an inference as a fact.
The version time for the exposure graph, rules, and scoring configuration used in the result.
Operating facts that the analysis uses but has not independently verified.
The evidence that would raise or lower confidence in the event, relationship, timing, or impact.
Evidence record example
Deployment options
Fast validation with a limited dataset and an agreed hosting region.
Required boundary: Data scope, retention, subprocessors, and access are documented before intake.
For clients that need dedicated cloud boundaries and client-specific controls.
Required boundary: Identity, networking, encryption, logging, backups, and support access are designed with the client.
For high-sensitivity workloads that must stay inside the client environment.
Required boundary: The client and Caracal agree update, support, monitoring, and recovery responsibilities.
Interactive platform workflow
The public demo uses modeled data. A pilot replaces it with the agreed client footprint, source policy, decision thresholds, and security boundary.
World map
Step 3
Run an event to load the impact score.
No event has been run yet.
Select a network and disruption to show the scenario impact.
Representative modeled USD range
Generate the brief to load a modeled cost range.
This is not a customer result, forecast, or price quote.
Company-specific demo
Send your email and we will follow up to schedule a company-specific walkthrough or focused pilot scope.