Routine workload savings
When extraction and classification stay on controlled lanes
Approve public, sovereign, and on-prem lanes by policy. Keep routine extraction cheap, keep sensitive material inside the boundary, and log every routed decision back to the case.
Routing posture
Public, sovereign, and on-prem options in one control surface
9
When extraction and classification stay on controlled lanes
82-97%
Prompts, outputs, reviewers, and model versions logged
100%
Operators keep working if one provider or region becomes unavailable
Multi-lane
Approved model lanes
Analysts stay in the same case workflow while policy decides whether a task can use an external provider or must stay private.
Linked case context
Summaries and extracted findings stay attached to the investigation graph so analysts can review, merge, reject, or promote them inside the live case workflow.
Use approved external providers for complex reasoning, multimodal review, and long-context synthesis when the workload is cleared to leave your controlled environment.
Approved provider
Capabilities
Best For
Photo, video, and long-form document analysis cleared for external handling
Compliance
Approved provider
Capabilities
Best For
Cross-file reasoning, entity extraction, and analyst drafting outside controlled data lanes
Compliance
Approved provider
Capabilities
Best For
GovCloud-aligned deployments, partner environments, and approved multi-model routing
Compliance
Approved provider
Capabilities
Best For
Long briefings, case review, and cautious drafting where operators need strong review discipline
Compliance
Approved provider
Capabilities
Best For
Open-source and social-media context where current public signals matter more than controlled records
Compliance
Routine workload savings
When extraction and classification stay on controlled lanes
Approved model lanes
Public, sovereign, and on-prem options in one control surface
Trace coverage
Prompts, outputs, reviewers, and model versions logged
Fallback posture
Operators keep working if one provider or region becomes unavailable
Routing Control
The routing layer evaluates sensitivity, complexity, and required review before choosing a model lane.
Input Prompt
Extract names, locations, and organizations from this arrest report.
Routing Control
Routing Review
Sensitivity
LowComplexity
LowDecision
PrivateRoutine structured extraction stays in the cheapest controlled lane so volume work does not spill to premium providers.
Selected Model
Llama 3.1 8B
Cost
$0.00002
Cost Control
Compare a premium public-only posture with routed workloads that keep routine casework on cheaper controlled lanes.
100,000 prompts/month
Task Weighting
Adjust the workload weights. The calculator normalizes them to 100% of monthly volume automatically.
Current weight total: 100
Monthly Cost Comparison
Public-only routing
$289.00
With policy-based routing
$158.60
Monthly savings
$130.40
(45%)
Annualized savings
$1,564.80
Operating Advantages
The point is not model novelty. It is keeping provider choice, cost control, and evidentiary discipline inside one repeatable case workflow.
6+
fallback paths
Provider terms and approved-use rules change. A routed architecture preserves continuity when one provider becomes unavailable or restricted.
9
approved lanes
Extraction, long-context review, and multimodal analysis do not belong on one default model. Route the job instead of forcing a compromise.
0%
single-vendor dependence
Avoid provider lock-in and keep procurement leverage by proving that operators can work across more than one approved lane.
Continuous
lane refresh
Add, replace, or retire providers without retraining operators on a new interface or breaking the evidence trail.
Governance Posture
Each routed operation preserves who initiated it, why it was sent to that lane, which model answered, and how the result moved into casework.
Governance Posture
Prompts, outputs, reviewer actions, and routing reasons stay tied to the investigation record instead of disappearing into a chat transcript.
Governance Posture
Prompts, outputs, reviewer actions, and routing reasons stay tied to the investigation record instead of disappearing into a chat transcript.
Controls for criminal justice information and controlled investigative work
Deployment lanes aligned to federal hosting and continuous monitoring expectations
Traceability needed for disclosure, challenge, and court review
Governance Posture
Each routed operation preserves who initiated it, why it was sent to that lane, which model answered, and how the result moved into casework.
{
"operation_id": "op_7f8a9b2c",
"timestamp": "2024-12-08T14:32:17.842Z",
"user_id": "det_martinez",
"organization": "metro_pd",
"model": "llama-3.1-8b-instruct",
"tier": "private",
"task_type": "entity_extraction",
"input_tokens": 847,
"output_tokens": 156,
"cost_usd": 0.00002,
"sensitivity_classification": "CJI",
"routing_reason": "CJIS data - private tier required",
"prompt_hash": "sha256:e3b0c442...",
"response_hash": "sha256:5d41402a...",
"latency_ms": 183
}Walk through sensitivity rules, provider choices, and review controls on your own workload instead of watching a generic AI demo.